zdoom stays in memory

SargeBaldy · Post by **SargeBaldy** » Sat Nov 01, 2003 4:52 am

i've been having trouble with zdoom not closing properly in some of the latest betas of 2.0. when i'm testing a map doom builder will crash when i try to test because a copy of zdoom is already open hidden, and it's getting annoying. i guess i really don't have any more information than that about it.

Post by **randi** » Sat Nov 01, 2003 2:13 pm

It's never done this for me, although this keeps cropping up as a bug report from time to time. Until it happens to me, don't expect it to change.

Hirogen2 · Post by **Hirogen2** » Sat Nov 01, 2003 2:32 pm

Ugh. This same happens for my Paint Shop Pro, which for some reason crashes when ZDoom quits-and-changes back from fullscreen to windowed mode.

Anonymous · Post by **Anonymous** » Sun Nov 02, 2003 2:59 am

i used Deepsea and zdoom (not any of the 5x beta's) and deepsea couldnt run zdoom. it just sat there FOREVER. i ended up forcequitting, and from then on, simply using the START->RUN command to test my levels. (which was only a little annoying cause i had to close my level each time to allow zdoom to open it)

randomlag · Post by **randomlag** » Sun Nov 02, 2003 10:39 am

I've run all previous ZDOOM's (1.23 ... 52) and ZDOOM runs successfully with DeePsea using XP.

So the problem is not with ZDOOM or DeePsea, but something else, for example the OS.

Are you guys running XP or some version of Win98? How much memory? Vid card/driver? Version of DeePsea (could be something I forgot about).

Btw, killing a task/program in Win9x/ME is just about guaranteed to cause you problems later on because Win9X has real crappy object cleanup. It doesn't cleanup the GDI objects and some other handles - which is a big problem because you only have 64kb available.

Anonymous · Post by **Anonymous** » Sun Nov 02, 2003 10:13 pm

well, im running Xp, with around 200mgs of ram. (196 to be exact i think) and a 400mhz processor on a 266mhz motherboard overclocked to 300mhz. (so in otherwords 300mhz) running 2 videocards, one is Matrox G200 and second is Appian Graphics jeronimo Pro, both using WinXp certified drivers that came with Xp. deepsea is 11.82a shareware.

i go to Test level, and nothing is checked. the only fields with text inputted are EXE NAME: E:\DOOM2\ZDOOM.EXE and START IN:E:\DOOM2\

when i click OK, ZDOOM starts up, asks me for my IWAD. then creates a maximized window (to enter fullscreen) then... it freezes. i press Cnl+Alt+Del and both Zdoom AND Deepsea say 'not responding' so, i forcequit zdoom.

the little window pops up 'you decided to forcequit Zdoom' and i click 'show details' and heres all the info a little user like me could find that it wanted to send to microsoft. (plus the 2 files appcompat and Zdoom.some-weird-file-extension)

szAppName : ZDOOM.EXE szAppVer : 2.0.47.0 szModName : hungapp
szModVer : 0.0.0.0 offset : 00000000

randomlag · Post by **randomlag** » Mon Nov 03, 2003 12:04 pm

Since ZDOOM asks you for the IWAD, enter this on the Test Options line (this is the default, unless you forgot to mention this line?)

Test Options: -iwad e:\doom2\doom2.wad (change as required)

Should work since you said you can run it manually.

I'm assuming you have enough swap file space (you need at least 512mb free on the swap drive).

SargeBaldy · Post by **SargeBaldy** » Mon Nov 03, 2003 12:07 pm

i'm running XP on an athxp 1700 with 512M of RAM and a radeon 7500.

SyntherAugustus · Post by **SyntherAugustus** » Tue Nov 04, 2003 4:15 pm

Im also getting the same problem every time zdoom crashes on me.

Mr. Tee · Post by **Mr. Tee** » Tue Apr 27, 2004 10:59 am

Sorry for bumping an old post, but I had the same problem a while back.

It's been resolved ever since I added more RAM to my machine (from 128 to 384 MB). I don't know why, but since this and 63, ZDoom hasn't done its "staying in memory" thing again.

It may also have to do with an XP Pro update from MS.