Crashing after a time in-game.
Winterous
Join Date: 2005-07-29 Member: 57092Members, Reinforced - Shadow
You've heard it a bunch before, the game crashes after a while in-game with no apparent cause.
I fully removed the game from my computer then re-installed it, and it kept happening.
I fully removed the game from my computer then re-installed it, and it kept happening.
This discussion has been closed.
Comments
After switching to Kharaa I found that some images weren't loading correctly, I'd open the buy menu and images / transparent "effect" type things were squares of colour rather than what they were supposed to be. Then I entered the commander position and large pieces of the HUD were doing the same thing, then it crashed.
Today I tried again, after turning off shadows.
I was doing the same things as above, and had no problems until I hit escape after looking at the Kharaa in order to change the map, at which point the game crashed the same way it has been doing.
This leads me to believe that the problem is one of memory.
I'm on Windows XP 32bit, which unfortunately leaves me with 3.25 gig of functional RAM (or so the system specs window tells me); which isn't really very much.
Is it possible that there's a memory leaking issue with the current version? Menu assets not un-loading when you can no longer access them by changing team?
Anyway, thanks for whatever help you can give me.
From what I have figured out from my own log files and what others have commented in other tech support threads there is indeed a memory leak in the game which is most likely causing these problems.
Doesn't look like we can do much until the devs fix it unfortunately.
Please fix
First time the game crashed, task manager said that the NS2 process was using 1.6 million K of memory, which seems like an awful lot.
Second time I switched to Windowed Fullscreen from normal Fullscreen, and I was watching task manager to keep an eye on the memory usage; it was jumping up and down, but didn't go much over around 600k.
I entered a map on sandbox mode, went Marines, looking at some buy windows and bought some grenades, threw them; then I went commander, checked out the multiple tabs...
And the moment I hit the "log out" button, the game crashed, giving this error message.
I kept that error message up and ran techsupport.exe, and attached the resulting .zip to this post.
This game has run perfectly fine on this computer before, and it's quite upsetting that I can't continue to play it now.
Reinforced programe bring you guys 100k $ , b ut instead on Steam forums over 1000 players are quitting this game because Crash , bug every time game update
Im love this game , but my self "patient" have a limit ....
I shouldn't have any memory problem with 8Gb running on Win7....
Devs are aware of this bug and are working on it now.
BE SURE TO USE ONLY DX9 FULLSCREEN.
Will keep you all updated here as soon as i know more.
excellent
Despite the fact that the techsupport.exe said it was creating dump files I dont see the minidump in the zip at all. I did see it in the debug report that I sent after i made the techsupport info but nothing actually in the zip file. Is there another place where these files may have been placed?
But I hope I will not have to reinstall for every updates...
If you are having this problem please do me a favor and turn down your texture settings.
This should lower your memory usage a bit and many people reporting a crash appear to be running out of memory to allocate to ns2.
No matter how much ram you have you should try this.
NS2 is a 32bit process and its memory size is limited by this fact. Even if you have 1645 gigs of ram ns2 can't use all of it. The puny 32 bit numbers just aren't big enough.
Report back with the success of trying this, please.
DX9 fullscreen is crashing like 90% more for me than dx11 at this point. Any thoughts?
HMMM...
Can you provide the # of bytes that fail to allocate with? and whether you run 64 or 32 bit?
Also be sure to lower texture quality as mentioned above, and enable Texture Streaming.
I am consolidating all "failed to allocate" errors to this thread.
Please continue there.