[r2075+]Unable to allocate 217698 bytes

[Major Cooke]

One thing I notice is that after playing a few maps of Invasion UAC, the game tends to slog a little, and then I notice something EXTREMELY weird... Sprite sorting gets shot out the back door and places random sprites for random actors, the console screen changes to all sorts of ripped up sprite placements, and then the game will crash with the "Unable to allocate 217698 bytes" error.

The only build I can use that won't give this error is Zdoom r2071 and GZdoom 696, anything above that will continue to give me the error after a bit of gameplay.

[Spleen]

Are you using high quality resize scaling in OpenGL mode? You could be running out of page file space, since it can take up a lot, depending on whether your graphics card uses your computer's RAM or its own.

You could check by opening your Task Manager (Ctrl+Alt+Del) and looking at your RAM usage throughout the game. The exact procedure for doing this depends on your Operating System.

If that's the problem and you are using HQ scaling, try turning it off.


If you are running out of page file sapace without HQ scaling, I suggest closing programs besides ZDoom [edit: oops, what was I thinking, sorry] whilst playing it.

[Major Cooke]

I'm not using Skulltag. Skulltag uses it's own engine... What are you talking about? I said Zdoom and GZdoom.

And no, hi-res scaling is off. I have 4 gigs of memory, and I did close all my windows.

I reverted back to Zdoom 2071, and GZdoom 696(697), and I haven't encountered the error once since. I've tried different revisions above this too, and I'm honestly afraid to try any more. It tears the sprites up the hizzy.

[randi]

You've tried 2075 and 2071. How do the three revisions in between fare?

[Major Cooke]

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.

[Major Cooke]

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.

[Deathlike2]

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.

[Deathlike2]

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.

[Major Cooke]

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.

[Graf Zahl]

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.

[randi]

I... haven't tried 2072-2074

Here, I have collected them for you.

[Major Cooke]

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.

[Project Shadowcat]

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.

[Gez]

I'm also using Aeons of Death.

See, that's the kind of things you've got to say in the first post.

[randi]

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.