1.0.5 save loading crash with mods

[TheDestroyer111]

Hello there! The problems started happening for me about... A month ago? (not sure exactly :P) And this makes my 1.0.5 game unusable! The shortest definition of what happens is that the game crashes while loading saves, but this issue is likely very complex, so the explanation will be detailed.

KSP version: Mac OS X, no Steam, v1.0.5.1028

Explanation: At one point (at least several game startups after the last time I installed a mod for that install) my game started crashing during save loading and started displaying exactly this (http://i.imgur.com/9s2wHdr.png) every time I attempted to load any of my saves. The game simply becomes unresponsive, the mouse pointer becomes a "spinning rainbow wheel" indicating that an application is unresponsive, and command+alt+escape becomes the only way to exit the game. At one point, seeing that attempting to load any old save is pointless, I have created a new save, and it was actually possible to enter the save right after creating it, but after quitting the game and starting it up again, it became impossible to get into the new save. (Although I managed to get into one of the old saves while making this thread several times, the same crash always happened when I tried to use any of the space center buildings) Then, I thought up another possible solution: I have downloaded KSP again and copied the "GameData" and "saves" folders into the new install location, but didn't copy anything else. For a couple of game startups, everything worked without any issues on the new install, but later, the new install also got bugged in the same way too.

Screenshot(s): look above to see where the game stops, and look below to see my gamedata folder

Craft/save file(s): If the issue cannot be resolved without such files, I could give you my entire 1.0.5 install   but not now

Logs: http://www.This website cannot be used on these forums/download/96ym6jl1xywfhm7/KSP.log is the log for my first 1.0.5 install, and http://www.This website cannot be used on these forums/download/a6iggzaavkk3kga/KSP%282%29.log is the log for the second install (see Explanation section for an explanation).

System/computer specs: Mac OS X 10.9.4, MacBook Pro 13-inch Mid 2009, 2.26 GHz Intel Core 2 Duo processor, 4GB 1333MHz DDR3 memory, NVIDIA GeForce 9400M 256MB graphics, 44GB free disk space on a 128GB solid state SATA drive... That's all you need here, am I right?

Clean/updated installation: The first 1.0.5 installation is a clean one (no old stuff put into a newer version), the second is what you can read in the explanation.

Also, there is something you might use, my GameData folder from the 1.0.5 saves: http://i.imgur.com/7LRSBH9.png

Thanks for any help with this!

[TrooperCooper]

 

I'm not familar with MAC, but you have quite some memory intensive part mods installed there. Maybe someone with more knowledge of MAC can help you out, but my approach would be to check how much memory the KSP task uses and whether or not it keeps crashing arround a smiliar ammount of it used. Everytime you do a session change like loading a vessel etc. your memory footprint grows and at some point it exceeds the limit and crashes. If that is whats happening, you might have to reduce the ammount of large mods installed.

The other option of course is to upgrade to 1.1. which can make use of more RAM (or in your case, since you only have 4 gig, it could utilize temporary disk space).

 

Edited May 24, 2016 by TrooperCooper

[TheDestroyer111]

I have checked the memory usage, and found some weird things. First of all, I have already downloaded and started playing 1.1 (even though 1.1 somewhat hugely lowered my performance on the same graphics settings), just didn't delete that old install because I have some cool things on it. When I check the memory usage with Activity Monitor with KSP on (no matter what version), the memory is entirely full, but Mac's Activity Monitor appears to use a terrible amount of memory by itself (0,5 gigs at minimum, though most of this >0,5GB is in a separate task from the activity monitor main process). Anyway, when I check how much memory is used by my 1.0.5 install, it uses up to just above 1,3 GB during loading, and 850 MB during the crash, so it probably isn't an out of memory issue.