[r2075+]Unable to allocate 217698 bytes

Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies

BBCode is OFF
Smilies are ON

Topic review
   

Expand view Topic review: [r2075+]Unable to allocate 217698 bytes

Re: [r2075+]Unable to allocate 217698 bytes

by Graf Zahl » Fri Feb 19, 2010 12:10 pm

See here:

http://forum.drdteam.org/viewtopic.php?p=43669#p43669


I consider any further investigation of a project that wastes so much memory for bad organization pointless.

Re: [r2075+]Unable to allocate 217698 bytes

by Major Cooke » Wed Feb 17, 2010 7:10 pm

Yeah, except that I actually got a blue screen for the first time on 2071 while playing in game... I'm beginning to think that it indeed may be my system after all. I'll try it again to see if I get either bluescreen or the allocation failure message, again... It's the first time on 2071 that it's ever happened too, been using it for quite a while.

I didn't catch the file name of what was causing it to stop up, sadly.

*sigh* Whether a reformat would help or not, I'm considering sometime soon. I still have a bunch of junk on my hard drive, related to homework, other games, etc... And it's easy to back everything up on my external HD and wipe it out.

Oh, and would it be of any help for me to say I'm running windows 7 professional?

Edit: Okay, I put up the GZdoom version here, if this interests you at all Randy. I should tell you now that what I experience in the GZdoom software renderer I get the same with Zdoom (I used gzdoom 696 with 2071 as those two were compatible, or so I think) except for that blue screen... I don't really know what to say there, but I only experienced it in regular Zdoom.exe, not GZdoom with software renderer. But anyway, I tweaked some of the display cvars and reduced the usage of things like decals to nothing, and a few other things in the zdoom-name.ini file and it seemed to have helped a bit. I still get that occasional crash though.

Re: [r2075+]Unable to allocate 217698 bytes

by randi » Wed Feb 17, 2010 7:03 pm

And can you confirm that 2071 still works properly? That by just switching between 2071 and 2072 without rebooting or doing anything else, you can make the problem go away and come back?

Re: [r2075+]Unable to allocate 217698 bytes

by Major Cooke » Wed Feb 17, 2010 6:50 pm

Okay. I downloaded them and tried them, they behave the same way. I used Aeons of Death and Hell Revealed II map 32, still the same problem.

Re: [r2075+]Unable to allocate 217698 bytes

by randi » Wed Feb 17, 2010 4:48 pm

I thought this was implied, but I guess not: I uploaded those three revisions so you could try them and see how they behave. If you can pinpoint the specific revision that starts giving you trouble, that might be helpful. Now please download them.

Re: [r2075+]Unable to allocate 217698 bytes

by Gez » Mon Feb 15, 2010 2:28 pm

Major Cooke wrote:I'm also using Aeons of Death.
See, that's the kind of things you've got to say in the first post.

Re: [r2075+]Unable to allocate 217698 bytes

by Project Shadowcat » Mon Feb 15, 2010 2:01 pm

Major Cooke wrote:Aeons of Death
This has been the cause of a lot of memory-based issues regarding ZDoom, because no other WAD even comes close to having that many resources.

Re: [r2075+]Unable to allocate 217698 bytes

by Major Cooke » Mon Feb 15, 2010 1:54 pm

Hmm... I've been looking into this some more, and I realized that having sv_unlimited_pickup 1 on and gaining more ammo makes Zdoom take up more memory... I don't know why that is, but if this could be looked into, maybe this can help. I'm also using Aeons of Death.

Re: [r2075+]Unable to allocate 217698 bytes

by randi » Fri Feb 12, 2010 8:57 pm

Major Cooke wrote:I... haven't tried 2072-2074
Here, I have collected them for you.
Attachments
lostrevisions.7z
Oh, how ironic, that 7-zip has compressed three versions of the executable smaller than zip can compress one.
(1.65 MiB) Downloaded 55 times

Re: [r2075+]Unable to allocate 217698 bytes

by Graf Zahl » Thu Feb 11, 2010 4:41 pm

Sorry, can't help you with your computer acting up. The latest version works fine for me and does not produce any memory leaks either.


Regardless, the fact that memory allocation fails is normally pointing towards a problem with your system. Don't forget that all currently running processes can allocate 4GB of memory altogether so if you got some memory waster running in the background that alone may cause your problems.

Also, some more information would be appreciated, like a startup log for example or a screenshot of your task manager. I have absolutely no idea what you are all running so right now I blame your system for the problems.

Re: [r2075+]Unable to allocate 217698 bytes

by Major Cooke » Thu Feb 11, 2010 4:02 pm

Deathlike2 wrote:You don't have a big enough page file... or you have memory going bad or something. I suggest that you test your memory with Memtest86+ and/or check your memory timings/voltages. Having improper memory settings will cause stuff to be unstable.

I've tried your last map example (which is just a skip-map) and nothing happened here.
I've already ran diagnostics, my RAM is fine. I have 4 gigabytes of RAM. This didn't happen before I updated, but eh... Who knows. The map was supposed to be called "Hell's Vendetta", and it was a typo, should have been 23 I think...

EDIT: I think I found something... I went to install the default of Zdoom 2.4.1 over my r2151 build, it says the fmod.dll I have now is smaller than the one inside the official repack... I wonder why that is.

Actually, GZdoom 1.4.3 is using a different version of fmod.dll than Zdoom 2.4.1, I think. I hope Graf looks back at this message soon.

Re: [r2075+]Unable to allocate 217698 bytes

by Deathlike2 » Thu Feb 11, 2010 11:54 am

I've noticed this in GZDoom, but I'm not sure ZDoom does it. There's like a small cache used for building the nodes for the specific WAD (certain WADs do this IIRC).

I noticed that within the changelog, the only major changes between the reported version and the last working version is the node building.

Is it possible that the failure to rebuild nodes between versions is the culprit?

This bug looks vaguely similar to this: http://forum.drdteam.org/viewtopic.php?f=24&t=4747

The map in that thread also builds nodes as well.. so it might be affected somehow. This is just pure speculation on my end.

Re: [r2075+]Unable to allocate 217698 bytes

by Deathlike2 » Thu Feb 11, 2010 9:50 am

You don't have a big enough page file... or you have memory going bad or something. I suggest that you test your memory with Memtest86+ and/or check your memory timings/voltages. Having improper memory settings will cause stuff to be unstable.

I've tried your last map example (which is just a skip-map) and nothing happened here.

Re: [r2075+]Unable to allocate 217698 bytes

by Major Cooke » Thu Feb 11, 2010 9:04 am

Okay. I just got it again, and I'm using Zdoom r2151 and GZdoom 740, playing on Dues Vult II.

"Failed to allocate 1228800 bytes from process heap", it crashed on map 28.

Re: [r2075+]Unable to allocate 217698 bytes

by Major Cooke » Wed Feb 10, 2010 7:45 pm

I... haven't tried 2072-2074. Here's what I have tried so far:

2075
2108(2113)
2114
2118
2151

The only difference that I'm seeing is that it's crashing for me in both Zdoom and GZdoom (i tried both, just to make sure) and I get that error after a while of gameplay on larger maps.

Top