Constant Crashes, asking for help

[mecki]

Hey there!

I'm keeping getting crashes and I would appreciate finding out what is causing the problem since I'm lost.

The game crashes mostly when I'm switching sites (Space Center -> VAB, VAB -> Launchpad, loading vessels, etc.).

Most of the times I only have a few minutes, often it's not more than two minutes.

I don't have that many mods that add any parts.

According to activity monitor the game is nowhere near the 4GB RAM cap (1,89GB after start, around 2,2GB after most crashes).

My machine:

Mac

OSX 10.10.1

16GB RAM

NVIDIA GeForce GT 650M 1024 MB

My Mods:

000_FilterExtensions

000_Toolbar

ActiveTextureManagement (x86 Basic)

AJE

BetterBuoyancy

blackheart

Chatterer

CommunityResourcePack

CommunityTechTree

ConnectedLivingSpace

CrossFeedEnabler

CustomBiomes

DDSLoader

DeadlyReentry

DMagic Orbital Science

EngineGroupController

EngineIgnitor

FerramAerospaceResearch

Fusebox

KAS

KerbalConstructionTime

KerbalJointReinforcement

KronalUtils

KSP-AVC

MechJeb2

ModuleManager.2.5.9.dll

ModuleRCSFX

NASAmission

ProceduralDynamics

ProceduralFairings

ProceduralParts

RCSBuildAid

RealChute

RealFuels

RealismOverhaul

RealSolarSystem

Regolith

RemoteTech

RP-0

RSSTextures (2048px DDS)

SafeChute

ScienceAlert

SmokeScreen

Squad

StretchySNTextures

SXT

TechManager

ThunderAerospace

TriggerTech

TweakScale

UniversalStorage

My Logs:

https://www.dropbox.com/s/gi31422umol6y76/20150121_KSP.zip?dl=0

Any ideas?

Thank you so much!

[NathanKell]

Moved to Support (Modded)!

Hmm, none of the logs say anything about crashing. Are you sure those are the logs from *right after* you crash?

[mecki]

Moved to Support (Modded)!

Hmm, none of the logs say anything about crashing. Are you sure those are the logs from *right after* you crash?

Thanks for your reply!

I'm absolutely sure. Two crashes with their corresponding logs.

I did two things that improved the situation:

I added the latest version of the TAC config file from RO to my install.

I removed Universal Storage with its dependencies (Community Ressource Pack and Regolith)

Even after reading Vens Stock Revamp my situation is improved (although not "perfect"). I don't know exactly why…

Any help is still appreciated!

[cashaber]

Hey I am getting the same thing at leat I think its the same... Mecki please correct me if I am wrong. okies before you guys say its a mod doing it .. .No its not. Doesnt matter if a Mod is installed or not still crashes... What happens at least in my situation The game crashes each and every time after you complete a mission and end it doesnt matter if you abort of finish the mission.

When you finish a mission or not just go back to the space center the game crashes to desktop. my friends wonder why they see my playing it so many times on Steam. Any way even if it does not crash when you try to enter a building it does. I have tested this both with and with out mods installed. I have about 50 dumps or more in my KSP dir and a Note saying the Devs would love for you to send these.. well who do I send them too... would be easier to just have a send button.

[BENDERr]

for 50 years, never in my life met a buggy program! it is even buggy than Vista!

I really like the content of the game, but crash every hour (usually when you try to launch a ship) and the problem at startup, when instead Space Center UNclickable wall of sheds ... so furious that even i decided to write here.

[mecki]

absolutely!

I wish I could play for an hour!

[Master Tao]

@BENDERr:

KSP is a work-in-progress at the moment. Post good bug reports so the developers can identify and fix as many of them as possible. Try reading the Stock Support and Bug Reporting Guide for how to make good bug reports.

@mecki:

Your KSP is, in fact, running out of memory:

KSP(937,0xa05e21d4) malloc: *** mach_vm_map(size=2822144) failed (error code=3)*** error: can't allocate region

*** set a breakpoint in malloc_error_break to debug

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

Trying to allocate: 2796208B with 32 alignment. MemoryLabel: Texture

Allocation happend at: Line:411 in

Memory overview

[ ALLOC_DEFAULT ] used: 449986927B | peak: 0B | reserved: 498608801B

[ ALLOC_GFX ] used: 293783149B | peak: 0B | reserved: 354236548B

[ ALLOC_CACHEOBJECTS ] used: 158808B | peak: 0B | reserved: 10485760B

[ ALLOC_TYPETREE ] used: 5703B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 97272B | peak: 0B | reserved: 4194304B

Could not allocate memory: System out of memory!

Trying to allocate: 2796208B with 32 alignment. MemoryLabel: Texture

Allocation happend at: Line:411 in

Memory overview

[ ALLOC_DEFAULT ] used: 449986927B | peak: 0B | reserved: 498608801B

[ ALLOC_GFX ] used: 293783149B | peak: 0B | reserved: 354236548B

[ ALLOC_CACHEOBJECTS ] used: 158808B | peak: 0B | reserved: 10485760B

[ ALLOC_TYPETREE ] used: 5703B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 97272B | peak: 0B | reserved: 4194304B

(Filename: Line: 909)

KSP(937,0xa05e21d4) malloc: *** mach_vm_map(size=2822144) failed (error code=3)

*** error: can't allocate region

*** set a breakpoint in malloc_error_break to debug

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

Trying to allocate: 2796208B with 32 alignment. MemoryLabel: Texture

Allocation happend at: Line:411 in

Memory overview

[ ALLOC_DEFAULT ] used: 449987107B | peak: 0B | reserved: 498608801B

[ ALLOC_GFX ] used: 293783344B | peak: 0B | reserved: 354236548B

[ ALLOC_CACHEOBJECTS ] used: 158808B | peak: 0B | reserved: 10485760B

[ ALLOC_TYPETREE ] used: 5703B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 97308B | peak: 0B | reserved: 4194304B

Could not allocate memory: System out of memory!

Trying to allocate: 2796208B with 32 alignment. MemoryLabel: Texture

Allocation happend at: Line:411 in

Memory overview

[ ALLOC_DEFAULT ] used: 449987107B | peak: 0B | reserved: 498608801B

[ ALLOC_GFX ] used: 293783344B | peak: 0B | reserved: 354236548B

[ ALLOC_CACHEOBJECTS ] used: 158808B | peak: 0B | reserved: 10485760B

[ ALLOC_TYPETREE ] used: 5703B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 97308B | peak: 0B | reserved: 4194304B

(Filename: Line: 909)

KSP(937,0xa05e21d4) malloc: *** mach_vm_map(size=2822144) failed (error code=3)

*** error: can't allocate region

*** set a breakpoint in malloc_error_break to debug

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

Trying to allocate: 2796208B with 32 alignment. MemoryLabel: Texture

Allocation happend at: Line:411 in

Memory overview

[ ALLOC_DEFAULT ] used: 449987287B | peak: 0B | reserved: 498608801B

[ ALLOC_GFX ] used: 293783539B | peak: 0B | reserved: 354236548B

[ ALLOC_CACHEOBJECTS ] used: 158808B | peak: 0B | reserved: 10485760B

[ ALLOC_TYPETREE ] used: 5703B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 97344B | peak: 0B | reserved: 4194304B

Could not allocate memory: System out of memory!

Trying to allocate: 2796208B with 32 alignment. MemoryLabel: Texture

Allocation happend at: Line:411 in

Memory overview

[ ALLOC_DEFAULT ] used: 449987287B | peak: 0B | reserved: 498608801B

[ ALLOC_GFX ] used: 293783539B | peak: 0B | reserved: 354236548B

[ ALLOC_CACHEOBJECTS ] used: 158808B | peak: 0B | reserved: 10485760B

[ ALLOC_TYPETREE ] used: 5703B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 97344B | peak: 0B | reserved: 4194304B

(Filename: Line: 909)

KSP(937,0xa05e21d4) malloc: *** mach_vm_map(size=2822144) failed (error code=3)

*** error: can't allocate region

*** set a breakpoint in malloc_error_break to debug

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

Trying to allocate: 2796208B with 32 alignment. MemoryLabel: Texture

Allocation happend at: Line:411 in

Memory overview

[ ALLOC_DEFAULT ] used: 449987467B | peak: 0B | reserved: 498608801B

[ ALLOC_GFX ] used: 293783734B | peak: 0B | reserved: 354236548B

[ ALLOC_CACHEOBJECTS ] used: 158808B | peak: 0B | reserved: 10485760B

[ ALLOC_TYPETREE ] used: 5703B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 97380B | peak: 0B | reserved: 4194304B

Could not allocate memory: System out of memory!

Trying to allocate: 2796208B with 32 alignment. MemoryLabel: Texture

Allocation happend at: Line:411 in

Memory overview

[ ALLOC_DEFAULT ] used: 449987467B | peak: 0B | reserved: 498608801B

[ ALLOC_GFX ] used: 293783734B | peak: 0B | reserved: 354236548B

[ ALLOC_CACHEOBJECTS ] used: 158808B | peak: 0B | reserved: 10485760B

[ ALLOC_TYPETREE ] used: 5703B | peak: 0B | reserved: 4194304B

[ ALLOC_PROFILER ] used: 97380B | peak: 0B | reserved: 4194304B

Possible explanation:

Repeat after me: Don't trust Activity Monitory. Don't trust Activity Monitor. Don't trust Activity Monitor.

Activity Monitor seems to underreport memory usage. I suspect it's related to the compressed memory feature introduced in OS X 10.9, but don't quote me on that. I believe it only reports real RAM usage rather than address space usage, which is what matters for KSP. If you're ever really bored, add up the Memory column and compare it to the reported memory usage. You may be able to see more accurate usage figures by using the process status utility (ps in the command line), but I haven't checked it extensively.

KSP 0.90 uses quite a bit more RAM than 0.24 and earlier did – those SP+ parts are beautiful, but take up a sizeable chunk of RAM, and there were other significant assets added to the game.

There also appear to be issues specific to OS X 10.10, but I haven't been able to test them myself.

Workarounds:

Switch to ATM-aggressive if you're not already using it. Otherwise, change the scale setting in KSP/GameData/ActiveTextureManagement/settings.cfg. The default for Aggressive is 2, so 4 or even 8 should be enough to keep you from crashing.

[BENDERr]

warning that the x64 version is not stable looks mockery!

my laptop is easy to play: Crysis2,3, DeusEX, Farkray3 and others, but the KSP is just awful! The description says it supports up to 250 units-it is a lie! 5 units at a distance of 2.3 km (how to disable this folly? I thought delete the folder DokinFish get out of it !!!) and autosave every 2 \ 5 minutes completely kill the desire again to play the game.

Nevertheless, as I wrote, I like the content. I hope the developers will have in the next version release a playable product.

yet, it is only for testers!

[Major999]

I get the same 2.2 to 2.5 GB number. My KSP_OSX folder is only 2.6 GB in total anyway, so I can't see how the game can crash when It's supposed to be able to run at 3.5 to 4 GB without Issue. This is infuriating! Someone tell SQUAD! (I don't know how)

[Master Tao]

@BENDERr:

Crysis 2 and 3, Deus Ex, and Far Cry 3 are all graphics-heavy games, so they're usually GPU-bound. KSP is physics-heavy, so it's usually CPU-bound, hence the 2.3 km physics limit. Crafts in orbit outside of that range still follow gravity, but aren't fully simulated. I believe the Lazor System mod can change that range, though.

As far as autosave, I can't tell whether you're objecting to the rate or its existence. You can change the autosave rate by editing the AUTOSAVE_INTERVAL entry in KSP/settings.cfg. The default is 300 seconds.

There's also no 64-bit version of KSP for Macs.

@Major999:

Size on disk is not the same as size in memory. Textures in particular are compressed when they're saved.

[mecki]

Although KSP might be more CPU-heavy than other games it should be noted that it's memory management seems to be terrible and the lack of working 64bit versions (only Linux is stable, Windows seems to be horrible, OS X is nonexistent) doesn't make it better.

I hope for a feature-less update which makes it a stable and performant game but I guess that won't happen ever.

[BENDERr]

@BENDERr:

Crysis 2 and 3, Deus Ex, and Far Cry 3 are all graphics-heavy games, so they're usually GPU-bound. KSP is physics-heavy, so it's usually CPU-bound, hence the 2.3 km physics limit. Crafts in orbit outside of that range still follow gravity, but aren't fully simulated. I believe the Lazor System mod can change that range, though.

As far as autosave, I can't tell whether you're objecting to the rate or its existence. You can change the autosave rate by editing the AUTOSAVE_INTERVAL entry in KSP/settings.cfg. The default is 300 seconds.

.

thanks for the offer -Lazor System, I go to try it. I know that the KSP using more CPU then GPU -can see it in a task tray. just a little bit disappointed - the theme of the game is good!

and i see your status - may be U can advice why some of my units collected on Duna 2 weeks , fall down true a surface? (now i use HiperEdit,so,it's not a big deal,but - i don't like cheating ).