Random Crashes while Playing

[larkvi]

How to replicate: play for a little while, will crash in either exterior or interior scenes.

No mods, clean install of KSP downloaded from Steam, new craft.

player.log: https://www.dropbox.com/s/rew7xkm7lium66v/larkvi_playerlog_20141216_1316.log?dl=0

This computer had no problems playing .25 on OSX, I can play .25 with 40_+ mods on the Windows partition under OpenGL without crashes.

Computer:

15" MacBookPro, Retina, Mid-2012 (10,1)

2.3GHz i7

8GB RAM

GeForce GT650M w/ 1GB VRAM

Edited December 16, 2014 by larkvi
corr. version, added info

[logickal]

Can confirm. .90 on Mavericks/Macbook Pro combo is an incredibly crash-prone beast. I'm seeing the following in the Unity Player crash logs:

Exception Type: EXC_BAD_ACCESS (SIGABRT)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008

VM Regions Near 0x8:

-->

__TEXT 0000000000001000-0000000000b8e000 [ 11.6M] r-x/rwx SM=COW /Users/USER/Library/Application Support/Steam/*/KSP.app/Contents/MacOS/KSP

Application Specific Information:

abort() called

[logickal]

Sorry, I said Mavericks - I meant Yosemite.

Complete system specs:

Macbook Pro Late 2013, 2.3 GHZ i7

16 GB Ram

NVIDIA GeForce GT 750m 2048MB

OSX 10.10.1

[larkvi]

Completely uninstalled, re-downloaded from Steam, ran chmod on it, played for a while (2 hours?), got another crash while switching scenes.

Log: https://www.dropbox.com/s/dvvekxjgufex7a6/larkvi_playerlog_20141216_1800.log?dl=0

Image of the screen that displayed during the crash: https://www.dropbox.com/s/lw5sebm5kjfm4ax/Screen%20Shot%202014-12-16%20at%2018.01.09.png?dl=0

[andrew_ie]

I have the same problem. It worked fine with 0.25, but with the new upgrade it crashes continuously. This is completely stock, no mods present.

The logs for the crashes are available here

I've tried reducing the graphics quality to see if that made any difference, but it didn't appear to.

I'm using a late 2013 15" MacBook Pro Retina, 2.6Ghz i7, 16GB RAM, GeForce GT750M 2048M, running Yosemite 10.10.1

Any advice on being able to keep playing would be much appreciated!

[Master Tao]

@larkvi:

The first log shows KSP running out of memory:

DynamicHeapAllocator out of memory - Could not get memory for large allocationCould not allocate memory: System out of memory!

The second is less clear:

Receiving unhandled NULL exception

Obtained 47 stack frames.

#0 0x0000001f8ff752 in bnet::Free(void*, unsigned long)

#1 0x0000001f8d0000 in std::basic_string<char, std::char_traits<char>, bnet::ClientAllocator<char> >::_Rep::_M_dispose(bnet::ClientAllocator<char> const&)

#2 0x0000001f8d0848 in std::vector<PresenceUpdate, std::allocator<PresenceUpdate> >::~vector()

#3 0x00000093c3ef0b in __cxa_finalize

#4 0x0000008fe47f84 in (Unknown)

#5 0x0000008fe4ab71 in (Unknown)

#6 0x0000008fe52457 in (Unknown)

#7 0x0000009014eb1b in dlclose

#8 0x000000177f9efd in FreeLibrary

#9 0x00000029347018 in (wrapper managed-to-native) DLLUtils:FreeLibrary (intptr) + 0x28 (0x29346ff0 0x2934703e) [0x758ee00 - Unity Root Domain]

#10 0x00000029346eb6 in BattleNetDll:AppQuit () + 0x56 (0x29346e60 0x29346ee2) [0x758ee00 - Unity Root Domain]

#11 0x00000029346e55 in BattleNet:AppQuit () + 0x1d (0x29346e38 0x29346e5a) [0x758ee00 - Unity Root Domain]

#12 0x00000029346d6a in Network:AppQuit () + 0x42 (0x29346d28 0x29346d8c) [0x758ee00 - Unity Root Domain]

#13 0x0000002c60bfe8 in ApplicationMgr:OnApplicationQuit () + 0x10 (0x2c60bfd8 0x2c60bfef) [0x758ee00 - Unity Root Domain]

#14 0x00000005cd6d39 in (wrapper runtime-invoke) object:runtime_invoke_void__this__ (object,intptr,intptr,intptr) + 0x41 (0x5cd6cf8 0x5cd6d8d) [0x758ee00 - Unity Root Domain]

#15 0x000000012b37fe in mono_jit_runtime_invoke

#16 0x000000013e649f in mono_runtime_invoke

#17 0x00000000253c75 in scripting_method_invoke(ScriptingMethod*, MonoObject*, ScriptingArguments&, MonoException**)

#18 0x000000003573c2 in ScriptingInvocation::Invoke(MonoException**)

#19 0x00000000347a9a in MonoBehaviour::HandleNotifications(void*, int, MessageData&)

#20 0x00000000107b4b in MessageForwarder::HandleMessage(void*, int, MessageData&)

#21 0x000000000ffa48 in Unity::GameObject::SendMessageAny(MessageIdentifier const&, MessageData&)

#22 0x000000002f0052 in SendMessageToEveryone(MessageIdentifier, MessageData)

#23 0x000000002f8dd6 in NotifyPlayerQuit(bool)

#24 0x000000002f9ebb in PlayerCleanup(bool, bool)

#25 0x000000006624fa in DoQuit()

#26 0x00000000663644 in -[PlayerAppDelegate applicationShouldTerminate:]

#27 0x00000094e6db72 in -[NSApplication _docController:shouldTerminate:]

#28 0x00000094e6da70 in __91-[NSDocumentController(NSInternal) _closeAllDocumentsWithDelegate:shouldTerminateSelector:]_block_invoke

#29 0x00000094e6d7cc in -[NSDocumentController(NSInternal) _closeAllDocumentsWithDelegate:shouldTerminateSelector:]

#30 0x00000094e6d14b in -[NSDocumentController(NSInternal) __closeAllDocumentsWithDelegate:shouldTerminateSelector:]

#31 0x00000094e6cde3 in -[NSApplication _shouldTerminate]

#32 0x00000094d6e998 in -[NSApplication terminate:]

#33 0x00000097b7d2af in -[NSObject performSelector:withObject:]

#34 0x00000094d168a5 in -[NSApplication sendAction:to:from:]

#35 0x00000094d32c65 in -[NSMenuItem _corePerformAction]

#36 0x00000094d3296a in -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:]

#37 0x00000094d32021 in -[NSMenu _performActionWithHighlightingForItemAtIndex:sendAccessibilityNotification:]

#38 0x00000094d31fcd in -[NSMenu _performActionWithHighlightingForItemAtIndex:]

#39 0x00000094d31972 in -[NSMenu performKeyEquivalent:]

#40 0x00000094d2e095 in -[NSApplication _handleKeyEquivalent:]

#41 0x00000094c978a2 in -[NSApplication sendEvent:]

#42 0x00000000662ad7 in -[PlayerApplication sendEvent:]

#43 0x00000094adc1bc in -[NSApplication run]

#44 0x00000094ac4ff8 in NSApplicationMain

#45 0x00000000662dbb in PlayerMain(int, char const**)

#46 0x00000000002895 in start

@andrew_ie, logickal:

Please check your Player.log for the out-of-memory error message. If you find it, try lowering the texture resolution in the Graphics Settings or closing other programs to free up memory.

Otherwise, you'll need to provide the information requested in the Stock Support & Bug Reporting Guide to get good help.

[logickal]

[

@andrew_ie, logickal:

Please check your Player.log for the out-of-memory error message. If you find it, try lowering the texture resolution in the Graphics Settings or closing other programs to free up memory.

Otherwise, you'll need to provide the information requested in the Stock Support & Bug Reporting Guide to get good help.

Sorry, missed looking at Player.log - will give that a shot and report with more detail if necessary.

Thanks!

[andrew_ie]

@larkvi:

@andrew_ie, logickal:

Please check your Player.log for the out-of-memory error message. If you find it, try lowering the texture resolution in the Graphics Settings or closing other programs to free up memory.

Otherwise, you'll need to provide the information requested in the Stock Support & Bug Reporting Guide to get good help.

Yep - the player.log showed it ran out of memory. This never happened in previous releases, so I guess that it's something new in the changes. Pity the game can't use all of the resources of the computer (it has 16GB of RAM & a 2GB graphics card!).

Switching to half-res on the textures stopped the crashes.

[larkvi]

@larkvi:

The first log shows KSP running out of memory

I got that. Since I have twice as much memory as he game can handle and was not running any mods, *why* is a more interesting question.

[sherkaner]

Glad I'm not the only one seeing lots and lots of crashes on OS X with the beta. There doesn't seem to be any rhyme or reason -- sometimes loading a new scene, sometimes when just messing with a build. Hasn't happened in flight thought, now that I think of it.

[andrewaltogether]

It's definitely a problem with OS X and KSP. I have the same issues running out of memory even though I have 32GB installed and Activity Monitor never shows more than 2.1GB used. I switched to my Windows partition and can play at maxed out settings with mods for as long as I like. The problem existed in 0.25, too, so I don't know when they'll get around to fixing it.

[Wallygator]

Same. Crashing when changing scenes. Especially to the sph or vab. It's clearly memory related. Sad to see it lingering with every new version.

[sherkaner]

Is there anything else Squad needs to narrow this down; anything we can help test? At least for me this is distinctly a new thing in beta -- I never had crashes before. But maybe I just hit some memory threshold, although as others have said it doesn't seem like a physical limit as I have 16G and KSP doesn't seem to get close to using it.

[agenor3k]

I'm also having lots of crashes and it's new to 0.90 for me as well. Below is the typically requested information.

KSP Version: build id = 00705, 2014-12-15_13-59-25, Branch: master, 32-bit

What happens: Crashes mid game, System out of memory!

Mods / Add-Ons: All stock

Other Notes: Could not allocate memory: System out of memory!

System:

Model Name: iMac

Model Identifier: iMac14,2

Processor Name: Intel Core i5

Processor Speed: 3.4 GHz

Number of Processors: 1

Total Number of Cores: 4

L2 Cache (per Core): 256 KB

L3 Cache: 6 MB

Memory: 24 GB

Boot ROM Version: IM142.0118.B07

SMC Version (system): 2.15f7

NVIDIA GeForce GTX 775M 2048 MB

PLAYER.LOG file: https://www.dropbox.com/s/vgwgfpod3lin46b/Player.log.zip?dl=0

[agenor3k]

I may have messed up on the link to the PLAYER.LOG. Here they are again:

Example 1: https://www.dropbox.com/s/vgwgfpod3lin46b/Player.log.zip?dl=0

Example 2: https://www.dropbox.com/s/j54qhoqji61mdcj/Player2.log.zip?dl=0

[Kolhammer]

i registered here just to add to this thread. pre beta i was running this game just fine - maybe one crash every few sessions - but more than playable and totally enjoyable. i was so excited to get back into it since the beta was launched but the game is unplayable on my 6 month old macbook pro. every time i exit the plane or rocket shed it crashes. i can run other games for hours at max settings on this machine.

c'mon guys - this is a serious issue that many OS users are experiencing. i could run the game in the previous build - how can i not play it at all now!!

[AbacusWizard]

I've been seeing an awful lot of crashes recently as well, mostly when in the VAB or SPH. The game just freezes up and I can't do a thing except force-quit. At first I thought it was because I was building something with a huge number of parts, but it just crashed on a craft with only six parts too, so that can't be it. Texture rendering is set to lowest possible, and I'm on a Mac Pro with 6 GB of RAM, so that shouldn't be an issue. No mods except Procedural Fairings, and I'm not using any of the parts from that in the current craft anyway. I don't recall anywhere near this many crashes in previous versions.

[SmallFatFetus]

I am having issues horrible instability as well. This has made the game almost unplayable as it takes 5 minutes to load, play for 2 minutes, then it crashes. Rinse lather repeat. I had to cancel my Challenger mission (link in sig) because of crazy amounts of crashing.

Squad, PLEASE fix this. It's killing my enthusiasm for KSP, and if it isn't fixed by 1.0, you will have lost me as a player.

SmallFatFetus

[papics]

Same here 0.90 and Yosemite on the most powerful MacBook...

[Fourjays]

I'll just add to the list of people here with a horribly unstable KSP on OS X. I think the problem is memory related. Stock KSP starts up at 1.90GB and I know the limit for KSP on OS X is at about 2.2GB, so I don't think there is a lot of room for scene transitions to occur, etc (it typically occurs when switching scenes, but also at other times).

As an aside, I also get a low frame rate in the SPH/VAB on OS X. I easily get 60fps in space, with it dropping to 30fps near oceans (known issue, even my monster gaming rig dips). However, the SPH/VAB struggles to go above 21fps on my iMac (nVidia GT 750M graphics).

[Master Tao]

I know the limit for KSP on OS X is at about 2.2GB

Can you demonstrate that? The vmmap utility strongly indicates that KSP can access up to 3.5 GB with 1/2 GB reserved for system libraries.

You can log the Virtual Memory Map using vmmap in Terminal like this:

vmmap -v KSP > ~/Desktop/KSP_vmmap.txt

That will only work while KSP is running, so try to run it either very often, or as soon as you see graphical glitches.

It would help to post all of these:

• Player.log from that run of KSP
  
• System RAM amount
  
• Graphics RAM amount
  
• the VMMap, as above
  

[reaction_wheel]

I have been plagued by this problem ever since the 0.90 update. It doesn't make the game unplayable but it is extremely frustrating and happens to me about every half hour of game play, especially when doing anything related to the VAB. I have tried removing mods and nothing seems to change with the crashes. I will try to post the player.log, VMMap, etc. next time but I would be very very grateful for an update that clears up this issue!!

[xerogravity]

Can you demonstrate that? The vmmap utility strongly indicates that KSP can access up to 3.5 GB with 1/2 GB reserved for system libraries.

I've been running v0.9 on a new(ish) iMac with Activity Monitor running in the background. As soon as I get KSP taking over 2.45Gb of memory it beachballs on me. This is usually triggered by a scene change as these tend to make the memory usage jump up. Most of the time the memory just ratchets up, though I have noticed a few instances where it has gone down by a small amount so some processes are freeing up some memory. Since I've been monitoring memory allocations this way I've never got up to 2.5Gb.

The first sign I get of trouble is a "shadow" texture appearing over any ground textures (making it impossible to land by "eye") or misplaced floating textures overlaying space craft textures. If I have a lot of time invested in a mission this is where I exit and re-start KSP.

Running career mode (with about 15 flights active) I get about 15-20 minutes of game time before it locks up. It takes all the pleasure out of the game. I don't mind the frustrations of actually playing the game - it's what makes it enjoyable when you succeed, but crashing out like this is more trouble than it's worth. To be honest, if we get to 1.0 and this still occurs I'll leave it for 6 months and perhaps try again further down the line (after a few more releases)

Quick edit to say: prior to v9.0 I had virtually no problems running KSP and was happy with how trouble free it was. Something changed between 0.25 and 0.9 (more than just a big version number change!) For me this isn't one of those long standing bugs that are hard to locate, this is something that was altered for v9.0.

Edited April 7, 2015 by xerogravity
extra para

[Fourjays]

Can you demonstrate that? The vmmap utility strongly indicates that KSP can access up to 3.5 GB with 1/2 GB reserved for system libraries.

You can log the Virtual Memory Map using vmmap in Terminal like this:

vmmap -v KSP > ~/Desktop/KSP_vmmap.txt

That will only work while KSP is running, so try to run it either very often, or as soon as you see graphical glitches.

It would help to post all of these:

• Player.log from that run of KSP
  
• System RAM amount
  
• Graphics RAM amount
  
• the VMMap, as above
  

Is just what I observe via activity monitor and a bit of deduction. It reports 1.90GB at start (stock). If I check activity monitor when the stock game crashes it has always been 2.2GB or more. If I add mods it has always begun to crash when it reaches 2.1-2.3GB. I might give the vmmap a go today if I have the time, but honestly I've grown tired of mucking around trying to get KSP 0.25-0.90 to work on my iMac. Just hoping 1.0 is going to be more optimised at this point.

EDIT: I forgot to mention that I've never seen graphical glitches myself (other than low FPS in the VAB/SPH). It just crashes otherwise.

Edited April 21, 2015 by Fourjays

[Adriano72]

Upping with the same problem: the game is a true pearl, but it crashes randomly on my mcabook pro with Yosemite10.10.3. Removing some advanced graphic options seems to improve a little bit

Keep up the great work!

Ciao

Adriano