Jump to content
  • 0

1.3 crashes more


Marshal Nedelin
 Share

Question

14 answers to this question

Recommended Posts

  • 1

In terms of graphics, you could try launching the game using openGL. See this link for details on that. Generally, OpenGL uses much less memory than the default DirectX renderer. Aside from that, it's unlikely that there's going to be a solution for the out of RAM issue - make sure as many of your apps are closed as possible, to free up as much memory as possible.

Considering the recommended amount of RAM for system's playing KSP is 4GB, and the listed minimum is only 3GB, you should be able to run it.

 

EDIT: I've noticed you haven't actually provided details of your system. Could we get those? Installed RAM, OS, CPU, GPU, et cetera.

Edited by Bilfr3d
Link to comment
Share on other sites

  • 1

@Marshal Nedelin: your output_log.txt shows you have unpacked the KSP zipfile within C:\Users. Don't, it is a widely known cause for issues, as the operating system (OS) protects content in that folder from any unauthorized application. Avoid any other folder with a special meaning for the OS, best to create one of your own (e.g., C:/Games/KSP).

Now, the above can easily be the cause of the crash, when KSP tries to write info on any file within a protected folder.

But the output_log also shows "Error while initializing dbghelp.dll", so in case it still happens after having correctly installed KSP, do check that dbghelp.dll is fine (it is a Windows stock library, within C:\Windows\System32), compare with e.g. what reported here. More info on that library here, but to be short, it is invoked to write on the log the stack trace after a crash is detected (your output_log shows a null stacktrace, the result of the dbghelp.dll not working correctly). Should you find on your system a file dbghelp.dll not matching filesize, date, version, I'd advise to scan it for possible malware (if any is found, scan everything on your system).

After having corrected both the KSP install and the issue with that library, should the issue persist, provide a new output_log file.

Link to comment
Share on other sites

  • 0

okay. changing the directory made no difference. 1.0.3 or so never crashed in the Users directory.

I followed the instructions in the links you provided, (installed various M$ crap and 2 GB worth of Windows kits). Nov I've advanced to the next level of crash. Now KSP just hangs (not responding, greyed out window) after a few minutes. output_log on the link below. Seems the poor thing ran out of memory?

https://ufile.io/i1ms5

 

Spoiler

so on repeated tests, mostly it all goes well until scenechange to spacecenter - 


[HighLogic]: =========================== Scene Change : From FLIGHT to SPACECENTER (Async) =====================
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

Unloading 1 Unused Serialized files (Serialized files now loaded: 0)
KbApp.OnDestroy NullName
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

[UIApp] OnDestroy: KSPedia
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

[UIApp] OnDestroy: ResourceDisplay
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

[UIApp] OnDestroy: ContractsApp
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

KbApp.OnDestroy Planet Info
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

KbApp.OnDestroy Unowned Info
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

[UIApp] OnDestroy: CurrencyWidgetsApp
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

KbApp.OnDestroy Vessel Info
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

KbApp.OnDestroy Planet Parameters
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

KbApp.OnDestroy Vessel Crew
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

KbApp.OnDestroy Planet Resources
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

UnloadTime: 74.556877 ms
[UIMasterController]: HideUI
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)


Unloading 2354 unused Assets to reduce memory usage. Loaded Objects now: 115017.
Total: 745.037048 ms (FindLiveObjects: 36.801350 ms CreateObjectMapping: 29.893684 ms MarkObjects: 659.712585 ms  DeleteObjects: 18.601620 ms)

[Progress Tracking]: Posted anonymous data to server successfully. Server Reply: KSP PROGRESS DATA OBTAINED
 
(Filename: C:/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 42)

Unloading 0 Unused Serialized files (Serialized files now loaded: 0)

Unloading 7 unused Assets to reduce memory usage. Loaded Objects now: 113521.
Total: 690.031311 ms (FindLiveObjects: 35.894390 ms CreateObjectMapping: 28.636160 ms MarkObjects: 623.706848 ms  DeleteObjects: 1.767721 ms)

DynamicHeapAllocator allocation probe 1 failed - Could not get memory for large allocation 8388608.
DynamicHeapAllocator allocation probe 2 failed - Could not get memory for large allocation 8388608.
DynamicHeapAllocator allocation probe 3 failed - Could not get memory for large allocation 8388608.
DynamicHeapAllocator allocation probe 4 failed - Could not get memory for large allocation 8388608.
DynamicHeapAllocator out of memory - Could not get memory for large allocation 8388608!
Could not allocate memory: System out of memory!
Trying to allocate: 8388608B with 16 alignment. MemoryLabel: GfxDevice
Allocation happend at: Line:62 in 
Memory overview

[ ALLOC_DEFAULT ] used: 283472750B | peak: 0B | reserved: 321395714B 
[ ALLOC_TEMP_JOB ] used: 953922B | peak: 0B | reserved: 4194304B 
[ ALLOC_GFX ] used: 299153202B | peak: 0B | reserved: 341038866B 
[ ALLOC_CACHEOBJECTS ] used: 449280B | peak: 0B | reserved: 10485760B 
[ ALLOC_TYPETREE ] used: 0B | peak: 0B | reserved: 0B 
[ ALLOC_PROFILER ] used: 0B | peak: 0B | reserved: 0B 
[ ALLOC_TEMP_THREAD ] used: 58213B | peak: 0B | reserved: 2621440B 
Could not allocate memory: System out of memory!
Trying to allocate: 8388608B with 16 alignment. MemoryLabel: GfxDevice
Allocation happend at: Line:62 in 
Memory overview

[ ALLOC_DEFAULT ] used: 283472750B | peak: 0B | reserved: 321395714B 
[ ALLOC_TEMP_JOB ] used: 953922B | peak: 0B | reserved: 4194304B 
[ ALLOC_GFX ] used: 299153202B | peak: 0B | reserved: 341038866B 
[ ALLOC_CACHEOBJECTS ] used: 449280B | peak: 0B | reserved: 10485760B 
[ ALLOC_TYPETREE ] used: 0B | peak: 0B | reserved: 0B 
[ ALLOC_PROFILER ] used: 0B | peak: 0B | reserved: 0B 
[ ALLOC_TEMP_THREAD ] used: 58213B | peak: 0B | reserved: 2621440B 

 
(Filename:  Line: 1029)

Unloading 6 Unused Serialized files (Serialized files now loaded: 0)

 

and here it hangs.

 

Edited by Marshal Nedelin
moar info
Link to comment
Share on other sites

  • 0

Yes, those "System out of memory!" lines really show the issue now.

Actually, you were right to provide crash logs before, the error.log in them shows memory with your system: 2048 MB user address space is really too low for a game like KSP. Doesn't help the total RAM with the system is ~3GB (pretty low, the OS really can't manage enough RAM for applications), and the paging file shows 0 MB total [2144 MB free, but that seems a mistake]. That paging file should actually be set to a value ~ 4GB (check e.g. here) for the amount of RAM and OS in your system to work best. That alone should provide enough to increase the user address space for the OS to be able to allocate memory for KSP to work.

Link to comment
Share on other sites

  • 0

Hm. setting the pagefile size to 8GB doesn't help. My computer has 4GB RAM, and 1.0.x verisons of KSP almost never crashed. 

Could fiddling with the graphics settings help?

Latest output log in the settings.

Spoiler

Unloading 3054 unused Assets to reduce memory usage. Loaded Objects now: 114601.
Total: 786.284302 ms (FindLiveObjects: 47.277817 ms CreateObjectMapping: 29.719170 ms MarkObjects: 696.809631 ms  DeleteObjects: 12.468491 ms)

Unloading 0 Unused Serialized files (Serialized files now loaded: 0)

Unloading 7 unused Assets to reduce memory usage. Loaded Objects now: 113317.
Total: 753.282227 ms (FindLiveObjects: 44.401417 ms CreateObjectMapping: 29.544146 ms MarkObjects: 678.195190 ms  DeleteObjects: 1.114321 ms)

Unloading 6 Unused Serialized files (Serialized files now loaded: 0)
DynamicHeapAllocator allocation probe 1 failed - Could not get memory for large allocation 8388608.
DynamicHeapAllocator allocation probe 2 failed - Could not get memory for large allocation 8388608.
DynamicHeapAllocator allocation probe 3 failed - Could not get memory for large allocation 8388608.
DynamicHeapAllocator allocation probe 4 failed - Could not get memory for large allocation 8388608.
DynamicHeapAllocator out of memory - Could not get memory for large allocation 8388608!
Could not allocate memory: System out of memory!
Trying to allocate: 8388608B with 16 alignment. MemoryLabel: GfxDevice
Allocation happend at: Line:62 in 
Memory overview

[ ALLOC_DEFAULT ] used: 298769910B | peak: 0B | reserved: 330606466B 
[ ALLOC_TEMP_JOB ] used: 437502B | peak: 0B | reserved: 4194304B 
[ ALLOC_GFX ] used: 296521626B | peak: 0B | reserved: 324261650B 
[ ALLOC_CACHEOBJECTS ] used: 57524B | peak: 0B | reserved: 10485760B 
[ ALLOC_TYPETREE ] used: 0B | peak: 0B | reserved: 0B 
[ ALLOC_PROFILER ] used: 0B | peak: 0B | reserved: 0B 
[ ALLOC_TEMP_THREAD ] used: 30721B | peak: 0B | reserved: 2621440B 
Could not allocate memory: System out of memory!
Trying to allocate: 8388608B with 16 alignment. MemoryLabel: GfxDevice
Allocation happend at: Line:62 in 
Memory overview

[ ALLOC_DEFAULT ] used: 298769910B | peak: 0B | reserved: 330606466B 
[ ALLOC_TEMP_JOB ] used: 437502B | peak: 0B | reserved: 4194304B 
[ ALLOC_GFX ] used: 296521626B | peak: 0B | reserved: 324261650B 
[ ALLOC_CACHEOBJECTS ] used: 57524B | peak: 0B | reserved: 10485760B 
[ ALLOC_TYPETREE ] used: 0B | peak: 0B | reserved: 0B 
[ ALLOC_PROFILER ] used: 0B | peak: 0B | reserved: 0B 
[ ALLOC_TEMP_THREAD ] used: 30721B | peak: 0B | reserved: 2621440B 

 
(Filename:  Line: 1029)

 

Link to comment
Share on other sites

  • 0

Could you please show a new error.log after having set the pagefile? Previously was reported the OS had allocated only 2GB address space to the application, and KSP really can't work with that low amount of memory. I hoped the pagefile could allow the address space be increased, would like to see if the issue is still that or a new one.

Link to comment
Share on other sites

  • 0

Huh. No matter how I set the pagefile, or play with the windows control panel, the error.log still shows 2048 MB user address space. ( https://ufile.io/rnypk )

I'm running a laptop, win7 ultimate, on core2 duo, 4GB ram and GeForce 9500M.

After switching to openGL (thanks Bilfr3dhave a cookie!) rendering, there were no crashes at all during 2 hours or so of playing. I'll play some more and try to see if KSP crashes now.

Edited by Marshal Nedelin
typo
Link to comment
Share on other sites

  • 0

ok, thanks for that latest log. It still shows the pagefile being = 0 MB, though I'm sure you noticed. Actually, pagefile serves to allow RAM be swapped between applications, without that any other process loaded (even if currently inactive) stays resident in RAM and can't be swapped out. Meaning, the effective RAM available for KSP to run is even less (indeed, was reported as 725 MB free with that last error.log). With a pagefile large enough, OS swaps RAM content of inactive processes to disk, so to let all RAM available to the process in foreground.

Am I right your system is Windows7 32bit? 32bit OS can only map up to 4GB memory with any application; however the low 2GB of RAM are by default to the system itself. Is possible to change how the system reserves RAM by use of 4GT and /userva system settings (info here).

Glad you see launching in OpenGL works, indeed that mode takes less RAM. But if you observe the amount of RAM used by KSP (e.g., from a Task Manager reading) you'll notice to be quite close to the limit; anything like a complex game or add-ons will push over that. Indeed, before KSP_x64 was stable, I also had to use OpenGL with the 32bit versions of the game (plus some add-ons to reduce textures size, now no more required as KSP changed the format of those files to be smaller).

Link to comment
Share on other sites

  • 0

25 GB free space should be enough for a 8GB pagefile, I think. And yes, it's 32bit, so that's probably the root issue.

Peeking at KSP while it runs in openGL mode does show it to consume about 1,5GB memory (and no crashes at all! wheee!). I've been putting off buying a new laptop, but I'll do it to keep playing KSP :D

Edited by Marshal Nedelin
Link to comment
Share on other sites

This thread is quite old. Please consider starting a new thread rather than reviving this one.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...