Project

General

Profile

Bug #5016

Crashes on long spaceplane voyages

Added by SubOne over 9 years ago. Updated over 8 years ago.

Status:
Closed
Severity:
Normal
Assignee:
-
Category:
Gameplay
Target version:
-
Start date:
05/16/2015
% Done:

100%

Version:
1.0
Platform:
Linux
Expansion:
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

I've tried several times to reach my contracts in various locations on Kerbin, but I don't get much further in distance than from KSC to the west coast before the game inexplicably crashes. It's happened in the air as well as while landed.

Reported version in the game is actually v1.0.2.0, but I only see 1.0 and 1.0.1 as options in the bug tracker.

Intel® Core™ i7-4770K CPU @ 3.50GHz × 8
GeForce GTX 760/PCIe/SSE2
Ubuntu 14.04 LTS 64-bit

buildID.txt (60 Bytes) buildID.txt Nukesforbreakfast, 05/17/2015 11:55 PM
error.log (48.3 KB) error.log Nukesforbreakfast, 05/17/2015 11:57 PM
report.ini (2 Bytes) report.ini Nukesforbreakfast, 05/17/2015 11:57 PM
output_log.txt (588 KB) output_log.txt Nukesforbreakfast, 05/17/2015 11:57 PM
DxDiag.txt (29.6 KB) DxDiag.txt Nukesforbreakfast, 05/17/2015 11:57 PM

History

#1 Updated by AlphaAndOmega over 9 years ago

  • Status changed from New to Confirmed
  • % Done changed from 0 to 10

This happens to me as well. When flying in kerbin atmosphere for long periods of time the game simply crashed to desktop. Every time.

#2 Updated by AlphaAndOmega over 9 years ago

Im using Windows OS 8.

#3 Updated by Nukesforbreakfast over 9 years ago

I'm seeing this happen on Windows 7 64-bit as well. I've uploaded the logs created from the crash to desktop, the buildID file, and a DxDiag file for my system. Hopefully, this information will help.

#4 Updated by Friendship7 over 9 years ago

This looks like Large Object Heap Fragmentation. On Windows 8.1 the virtual memory space goes up to 4GB before crashing with OutOfMemoryException when allocating an object that belongs on the Large Object Heap.

I assume there's an issue with the new aerodynamics or heat system allocating many large arrays. I have attached a two resources, one explaining the Problem in the .Net CLR (It doesn't completely apply to Mono but it is very detailed explanation) and the other describing a Mono workaround.

CLR Large Object Heap: https://msdn.microsoft.com/en-us/magazine/cc534993.aspx
Mono Large Object Heap: http://tirania.org/blog/archive/2009/Nov-09.html

#5 Updated by sal_vager almost 9 years ago

  • Status changed from Confirmed to Resolved
  • % Done changed from 10 to 100

There was a memory leak with the edge highlighter used by the heat system to warn the player of hot parts, this has since been disabled, solving the issue.

#6 Updated by TriggerAu over 8 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF