Kerbal Space Program

And finally, we just replicated the issue quickly in windowed mode (same textures problem).
SCREEN_RESOLUTION_WIDTH = 1600
SCREEN_RESOLUTION_HEIGHT = 900
FULLSCREEN = False
ANTI_ALIASING = 2

Thanks, though I can't replicate it here as I don't have a Mac, it's likely related to the other Mac graphics issues that have been reported recently, some players have had multicolor effects in the VAB/SPH while others have completely broken terrain shading.

Most of those reports have stated they use Intel gfx hardware though.

Also your log from the freeze just stops, KSP didn't have a chance to write to the KSP.log but may have written to the player.log, if it freezes again the player.log would be more useful.

Something I do see however is a very old graphics driver (2013).

SM: 30 (OpenGL 2.1 [2.1 NVIDIA-8.26.29 310.40.55f01])

This is all I could find on this driver, it's not available separately for OSX, https://www.nvidia.com/object/freebsd-x64-310.40-driver

You say you're on Mavericks, would you be able to update and see if that fixes this ?

I may just have to upgrade to the latest OSX in order for KSP to work smoothly...

Crash report from recent hard crash when switching from flight/gameplay to SPH ATTACHED

I can't read OSX logs, it might as well be Swahili and if there's something in there explaining this I'll not be able to find it.

I see the update to el capitan did update the gfx driver, to the slightly less ancient 310.42, the latest unix (not OSX unfortunately) driver is 352.63, I have no idea why Apple use such old drivers :/

https://www.nvidia.com/download/driverResults.aspx/95163/en-us

Your last KSP.log where it hung also just stops with no errors, you really need to post the Player.log next time, as that log will often contain more detail including the stack trace.

The log before (the one you posted with the OSX log) does show a null reference exception however.

[EXC 14:29:07.007] NullReferenceException
UnityEngine.Component.get_transform ()
SpriteRoot.set_ClippingRect (Rect3D value)
AutoSpriteControlBase.set_ClippingRect (Rect3D value)
UIListItemContainer.set_ClippingRect (Rect3D value)
UIScrollList.ClipItems ()
UIScrollList.ScrollListTo_Internal (Single pos)
UIScrollList.UpdateContentExtents (Single change)
UIScrollList.PositionItems ()
UIScrollList.RemoveItem (Int32 index, Boolean destroy, Boolean doEasing)
UIScrollList.RemoveItem (IUIListObject item, Boolean destroy, Boolean doEasing)
UIScrollList.RemoveItem (IUIListObject item, Boolean destroy)
ApplicationLauncher.RemoveApplication (.ApplicationLauncherButton button)
UIApp.OnDestroy ()

This isn't in the other logs, ApplicationLauncher is the notification area in the top right of the flight scene, but the rest appear to be built-in Unity classes and functions.

Have you tested a completely fresh install yet ?

If I may ask, what is the method you used to find the file? It'd be useful to know an easy way that I can share with others.

Also, the player.log has some new info.

KSP malloc: *** mach_vm_map(size=4198400) failed (error code=3)

• error: can't allocate region
• set a breakpoint in malloc_error_break to debug
  KSP malloc: *** mach_vm_map(size=2101248) failed (error code=3)
• error: can't allocate region
• set a breakpoint in malloc_error_break to debug
  Receiving unhandled NULL exception
  Obtained 12 stack frames.

malloc is short for "memory allocate" and is a C/C++ function ( https://en.wikipedia.org/wiki/C_dynamic_memory_allocation ) which the engine uses to dynamically manage memory.

This isn't limited to KSP, it can be an issue in any software written in C/C++ that is trying to use more memory than is available, such as the Unity engine which is written in C++.

A search shows the same error in a variety of other software ( https://duckduckgo.com/?q=malloc%3A+***+mach_vm_map+failed+%28error+code%3D3%29&t=canonical ).

This doesn't look to be the cause of the graphical issue, as this just results in a crash or freeze, the only things I can suggest are to reduce your texture quality so less memory is demanded by KSP, or try to free up RAM on your system.

OSX can be very memory hungry and likes to keep apps in RAM in case the user goes back to them, so it may be an idea to monitor the memory used by the system as a whole while playing KSP.

Player.log: I followed the instructions mentioned on http://bugs.kerbalspaceprogram.com/projects/ksp/wiki :

Mac OSX: Open Console, on the left side of the window there is a menu that says 'files'. Scroll down the list and find the Unity drop down, under Unity there will be Player.log Aka Files>~/Library/Logs>Unity>Player.log

This worked, and I could easily navigate to the Player.log file. I was surprised to find that my user's ~/Library directory was hidden, making it and its contents invisible to Mac OS X Spotlight search.

As for malloc and RAM starvation, this Mac has 16GB and I never get close to running out of real memory. Nonetheless, I'll try running KSP with reduced texture quality (grumble) to see if the game plays more reliably.

Hi all,

I see this bug's status is set to Needs More Info. Is there anything else I can do to help clarify and confirm this trouble?

Well, if you can figure out what conditions cause this that'd be great, it doesn't look to be affecting many players but all these graphical issues have been on OSX so far.

Right now I don't know if this is KSP, Unity, OSX, old drivers, a faulty gfx card or anything else, and it may be resolved in 1.1 due to the terrain shader rewrite, see the devnotes for details.

http://forum.kerbalspaceprogram.com/index.php?/topic/126828-devnote-tuesday-forums-letters-and-development/