Bug #3923
Crash to desktop after 3.5 hours of game play (2nd time today.)
100%
Description
Two separate CTD's today - each after an extended period of game time.
I've included some Windows Task Manager snaps showing that the main system memory is good - 16GB with 12 of that free at the time of the crashes.
Looks like the 32-bit version of KSP is running into the 2GB .NET memory barrier after a slow memory leak somewhere.
Game ran for about 3 hours 40 minutes since last crash to desktop.
NARRATIVE:
----------
I designed a new craft X1-V2 (file included) - an experiment using the newly acquired jet engine.
Craft was flown generally north east from KSP launch pad and observed the nice river cut into the mountains. After buzzing the jagged edges of the mountains, I extended flight toward an island and ran out of fuel just before making it. During the flight across the water, I ran the maximum time warp possible. (4 chevrons.)
Once the X1 Craft ran out of fuel, it splashed down on 3 chutes about 100m from the shoreline. I then stopped the time warp. (Note: It almost looked like the time warp was still running nonetheless. What I mean by this is that the game graphics have a sharp, stilted movement in time warp and the highlighting of craft body parts is very quick/acute. While the surrounding scene appeared to have smooth transitions after the time warp was returned to 1X normal, the body part highlighting when mouse-over still appeared as they do when the warp is active.) I clicked on 'Recover Craft' and the screen transitioned briefly to the space center scene then it CTD'd.
History
#1
Updated by Redgum almost 10 years ago
Updated by - File REDGUM_SysInfo.txt REDGUM_SysInfo.txt added
There should have been 13 attached files (logs/memory dumps et al) and all I see is the craft file.
What gives? o.O
#2
Updated by Redgum almost 10 years ago
#3
Updated by Redgum almost 10 years ago
#4
Updated by Redgum almost 10 years ago
- File output_log.txt output_log.txt added
#5
Updated by Redgum almost 10 years ago
- File persistent.sfs persistent.sfs added
#6
Updated by Redgum almost 10 years ago
- File REDGUM_DxDiag.txt REDGUM_DxDiag.txt added
#7
Updated by Redgum almost 10 years ago
#8
Updated by Redgum almost 10 years ago
Third CTD tonight.
Would have had more, but I kept an eagle-eye on the process ram used by KSP.exe - I was able to see that it appears there is a small memory leak.
I was able to capture a snapshot of the process ram a split second before it crashed. Normally, KSP.exe appears to run with around 2.5GB - starts the game with about 2.2GB consumed. As you play, it slowly ramps up, passing into 2.8 and 2.9GB. When it reached 3GB I shut the game down, saving (ALT-F5) my game and restarted the save game (ALT-F9) to see if it was something about the terrain or the area. Nope. The game started and continued from where I left off at 2.2GB and stayed there for awhile until it started creeping up over the next few hours.
This time, I let it go but took a few snaps as it approached the 3.0GB mark. It went over, still playing till around 3.5 -- the highest I'd seen it. I quickly snapped an image of the process memory and a split second later, CTD.
Gents, you have a memory leak. Because I'm noticing this after many hours of game play, I'd say it's going to be a nasty one to find.
The entire Kerbal-kind is depending on you.
-Red
#9
Updated by Redgum almost 10 years ago
- File Redgum_3rdCTD_error.log Redgum_3rdCTD_error.log added
You can only upload ONE file at a time.. this is painful.
#10
Updated by Redgum almost 10 years ago
- File Redgum_3rdCTD_KSP.log Redgum_3rdCTD_KSP.log added
#11
Updated by Redgum almost 10 years ago
#12
Updated by Redgum almost 10 years ago
#13
Updated by Redgum almost 10 years ago
#14
Updated by Squelch over 9 years ago
Updated by - Platform Win32 added
- Platform deleted (
Windows)
#15
Updated by TriggerAu over 8 years ago
Updated by - Status changed from New to Needs Clarification
#16
Updated by Redgum over 8 years ago
Well, after this bug sat untouched for more than a year, I'm not sure whether to laugh or cry when I read, "Needs Clarification."
I don't know how much more clearer I can be. You have a memory leak. I quit playing the game because it keeps crashing to desktop after about the same amount of time.
All it would take is for some intrepid bug smasher to follow along, use the game files I included and run the game and see if it doesn't happen to their game as well.
And hey, if it doesn't crash, then maybe I got the extra special custom copy that nobody else has. :-)
I might recommend a memory profiler. Good luck!
#17
Updated by Gaarst over 8 years ago
Updated by 
The bug tracker is currently being cleaned from all outdated/solved bugs.
Switching to "Needs Clarification" is the first part of the process for cleaning a bug and is normal.
As you observed the bug in an old version of KSP (0.90), you need to confirm that the bug still occurs in the latest version (1.1.3) or the bug report will be closed (since it will be considered outdated).
I have not read through your entire report and seen your files, but your bug seems to be a memory leak. These were known on the 32bit version of the game since the 32bit format could not physically handle greater RAM amounts than 4GB.
Since 1.1, the 64bit version, that does not suffer this problem, is stable and the memory leak issue is considered as solved since no one uses 32bit anymore.
#18
Updated by TriggerAu over 8 years ago
Sorry about the misunderstanding Redgum, as Gaarts said we are doing a mass cleanup on the bugs that havent had a lot of love. If your interested you can read more here: http://forum.kerbalspaceprogram.com/index.php?/topic/143980-time-to-clean-up-the-bug-tracker/
It isn't an indication of anything wrong with your report, just to be clear
#19
Updated by TriggerAu about 8 years ago
- Status changed from Needs Clarification to Closed
- % Done changed from 0 to 100
Closing for age