Phantasmogasm

i found this thread after googling this same problem, after reading the thread for a bit i started watching GCM and saw some odd stuff when i turned up the precision on the graph drawing. http://i.imgur.com/JQ7DORW Its more easy to see on the higher precision graph: http://i.imgur.com/TNTgwFu.jpg but for my game it looks like the system is dumping a boatload of memory into mono, continuously, mono then bricks itself, dumps all the excess memory, and stutters, causing what looks like the entire application to hang, and then the whole process starts again. whats even more confusing, is if this had anything to do with the memory required to do real time physics processing, why the hell would: http://i.imgur.com/kAd52vb.png it be happening at the start menu? on start up my KSP uses 4.2GB of RAM, rising to about 5.5/6 during intensive gameplay, but the memory graph for KSP remains relatively constant and so does my fps, even during the stutters, which really points the finger at mono. Though by no means am i an expert or claim to be. I really hope a fix for this comes about soon, i love KSP and will continue to play the life out of it, but the stuttering is so off putting its almost headache inducing to watch. Sys Specs: FX-8320 3.4GHz GTX-970 4GB (3.5/.5) VRAM 16GB 1600MHz Corsair XMS3 Ubuntu 15.04 x64 / KSP x64

ive discovered GCM works fine when i run the x86 version of KSP. i have no idea why, but maybe thats where the problem lies.

hey m4v, would it be possible to update the CKAN repo for the new version?

george@Sovereignty:~$ ls -l /home/george/.local/share/Steam/steamapps/common/Kerbal\ Space\ Program/KSP_Data/Mono/x86_64/GameData/GCMonitor/getRSS_x64.so ls: cannot access /home/george/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/x86_64/GameData/GCMonitor/getRSS_x64.so: No such file or directory george@Sovereignty:~$ ls -ld /home/george/.local/share/Steam/steamapps/common/Kerbal\ Space\ Program/KSP_Data/Mono/x86_64/GameData/GCMonitor ls: cannot access /home/george/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/x86_64/GameData/GCMonitor: No such file or directory george@Sovereignty:~$ ls -ld /home/george/.local/share/Steam/steamapps/common/Kerbal\ Space\ Program/KSP_Data/Mono/x86_64/GameData ls: cannot access /home/george/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/x86_64/GameData: No such file or directory george@Sovereignty:~$ ls -ld /home/george/.local/share/Steam/steamapps/common/Kerbal\ Space\ Program/KSP_Data/Mono/x86_64/GameData ls: cannot access /home/george/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/x86_64/GameData: No such file or directory george@Sovereignty:~$ ls -ld /home/george/.local/share/Steam/steamapps/common/Kerbal\ Space\ Program/KSP_Data/Mono/x86_64 drwxrwxr-x 2 george george 4096 May 31 17:34 /home/george/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/x86_64 george@Sovereignty:~$ ls -ld /home/george/.local/share/Steam/steamapps/common/Kerbal\ Space\ Program/KSP_Data/Mono/ drwxrwxr-x 5 george george 4096 May 31 17:34 /home/george/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Mono/ george@Sovereignty:~$ ls -ld /home/george/.local/share/Steam/steamapps/common/Kerbal\ Space\ Program/KSP_Data/ drwxrwxr-x 6 george george 4096 May 31 17:35 /home/george/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/ george@Sovereignty:~$ ls -ld /home/george/.local/share/Steam/steamapps/common/Kerbal\ Space\ Program/ drwxrwxr-x 16 george george 4096 Jun 1 15:46 /home/george/.local/share/Steam/steamapps/common/Kerbal Space Program/ george@Sovereignty:~$ ls -ld /home/george/.local/share/Steam/steamapps/common/Kerbal\ Space\ Program drwxrwxr-x 16 george george 4096 Jun 1 15:46 /home/george/.local/share/Steam/steamapps/common/Kerbal Space Program george@Sovereignty:~$ inside mono/x86_64 is a file called libmono.so and nothing else. its ubuntu 15.04

Having looked at my Player_log i suspect there might be something up with my mono installation?

thanks for the assist, which log is it? i dont see a GCM made log so is it a standard KSP generated log? i already have KSP process checked, and the graph is empty, when unchecked i get a decent graph but still under 700mb is that the mono heap size? thanks

Hi there, part of me feels like this is going to be a silly question, but does this mod have any issues with KSP linux? i recently switched over as i was told it was more stable. In game the FPS counter works but the memory usage counter shows as 0, but when i open the memory usage graph window, it shows KSP using only around 500mb of RAM, where as the system monitor says 4.2GB which seems more likely given i have 70 odd mods installed. Mod was installed using CKAN.

I tried KSPx86, when i tried to launch, KSP bricked itself and i got a whole load of error messages saying mods (that worked in x64) were not supported. KSP also default launches x64 for me, why would the default/loads of mods written for x64 if its not the main supported version? EDIT: Disregard, after fresh reinstall and game verification, i see i only have 1 version of the KSP exe left EDIT 2: If it was x86 i was using, then I understand how problem 1 was occurring, too many mods, too much RAM usage, but what about problem 2? launch stabilizers in space isnt a RAM issue.

KSP 1.0.2 has for me been the most unstable KSP version I have ever played, ive had stock and modded issues, but i play mostly modded so ill ask here. KSP: 1.0.2 Windows 64bit (KSP x64) Problem: mono.dll caused an Access Violation (0xc0000005) Mods installed: [COLOR=#00000A][FONT=sans-serif]*[x]science [/FONT][/COLOR][COLOR=#00000A][FONT=sans-serif]*AIES[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Chatterer[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Community Resource Pack[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Contract Window +[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Crew Manifest [/FONT][/COLOR][COLOR=#00000A][FONT=sans-serif]*DM Orbital Science[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Docking port alignment indicator[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*editor extensions[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Firespitter Core[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Heat Management[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*IR model rework core/expansion[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*intake build aid[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*interstellar fuel switch[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*karbonite/plus[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*KAS/KIS[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*KAS portable science container[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*KAX[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Kerbal alarm clock[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Kerbal engineer[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Kerbal Flight Data[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*KJR[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*KSP-AVC[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*KW Rocketry[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Landing Height Display[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*MSI Infernal Robotics[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*modular fuel Tanks[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Module Manager[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Module RCS FX[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*NF Construction[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*NF Props[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*NF Solar[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Precise Node[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Procedural Fairings[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Procedural Parts[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*RasterPropMonitor/Core[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*RCS build aid[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*RealChute[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Scansat[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Scatterer[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*ScienceAlert[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Ship Manifest[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*SpaceY Heavy lifter parts pack[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Switch active vessel[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Targetron[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Texture Replacer[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*Toolbar[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*TweakScale[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*universal Stortage[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*USI Kolonization Systems (MKS/OKS)[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*USI Exploration[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*USI Freight transport[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*USI Life support[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*USI survival pack[/FONT][/COLOR] [COLOR=#00000A][FONT=sans-serif]*USI tools[/FONT][/COLOR] previously had DE and FAR, but removed due to causing issues with other mods NOTE: All mods installed and managed by CKAN Reproduction steps: No known reproduction, can occur during flight, landing or ship change/return to KSC I have read online that this suggests a memory issue but only found references to x86 KSP having a 3.5GB memory limit, does KSP x64 have this same issue? Also, this crash does not produce an output_log. KSP: 1.0.2 Windows 64bit (KSP x64) Problem: Orbital trajectory launch stabilizers http://i.imgur.com/wKt498U.jpg http://i.imgur.com/shHL5zr.jpgMods installed: See Above Reproduction steps: Make and launch 2 stage ship using launch stabilizers, detach lower stage in upper atmosphere (becomes labeled "debris") change ship to new debris ship, the dropped stage is gone, replaced by the launch stabilizers you used, now high up in atmosphere, on an out of orbit/Solar system trajectory. Once switched to, are classed as "under acceleration" despite no engines, and thrust power set to none, preventing swapping back to the original ship. (see Spoilers for images)

I had this issue. If you have Deadly Reentry Continued installed, then that is your problem, the part config of the nose cone refers to a modifier that DE doesnt like (thats at least my understanding), the fix is: http://forum.kerbalspaceprogram.com/threads/51037-1-02-KW-Rocketry-v2-7-Available-1-02-Compatibility%21-16-05-2015/page247 however be aware, its suggested on that thread that the unofficial fix will break existing games.