Normally this occurs only under load when records arrive faster than they can be sent out. To show us the log, upload the Player.log to a site like (And no, isn't good enough, the file is far too large).ĮDIT: Also consider posting at Squad's Official Support forum with your Player.log files.The producer groups together any records that arrive in between request transmissions into a single batched request. To view the log when not playing KSP, and to upload it for others to see, the file is actually stored at ~/Library/Logs/Unity/Player.log To view the log while playing, launch /Applications/Utilities/Console.app and look for Unity>Player.log on the left side list.

Telling us you're crashing without a Player.log isn't really helpful toward diagnosing the cause, and if you can't diagnose it, you can't fix it.

In previous versions of KSP, hitting 2.89 GB of RAM would invariably crash KSP, because it's a 32-bit process.Īnd please post a Player.log file for others to parse, and maybe they can find something to give a clue as to the cause of the crashes. So at least try deleting ~/Library/Saved Application State/ Space Program.savedState/, and maybe consider deleting it every time KSP crashes.Īlso, use Activity Monitor to see what KSP's RAM usage is at. It's like an appendix, not very useful (for KSP) but can result in instability of it's corrupted. Hence why I think it made it past Squad's internal bug testing.Īnyway, have you tried removing the Application's Saved State? KSP doesn't really rely on Application Saved States to remember anything of consequence, so you can just delete it. So I think it's safe to say that while this is a problem, it's not a universal one.

I'm on a 2011 MBP, and I'm not seeing the frequent crashing other Mac users are.

Parts list is empty ksp mac