-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash on entering flight scene after spending more than $(max history length) in editor with EditorTime installed #1641
Comments
Got the crash again, with more or less an identical stderr.log, after just working on a rocket in the VAB and running a few KRASH sims. Didn't touch the Principia history length/prediction steps settings; they are still at the minimum allowed. |
I can haz journal? (Assuming of course that you manage to make it semi-reproducible.) |
I'm working on it. Unfortunately, I'm no closer to figuring out how to reproduce it than before, so it's likely that the first journal I can provide will be from a fairly long play session. |
Got a journal! It's quite large, unfortunately (about 3.2GB). I had been sitting in the VAB for some time, working on a new satellite + launcher, then the game crashed when I went to simulate. |
I got another journal, but it's even bigger, at 5.36GB, so I'll hold off on uploading it unless the first one doesn't help. The crash happened again after spending some time in the VAB, then trying to start a sim. I'll start messing with that next. |
Got a significantly smaller journal, at ~650MB. All I did was start KSP, start building a new rocket for a Molniya orbit contract, and crash upon launching a sim. |
I was able to reproduce the problem. As usual, thanks for the journal. Because we are in prelaunch we skip |
I think I finally figured out how to reproduce this. It requires EditorTime and Principia to be installed:
I tried this with Principia built from the current master (f7af30c), altered to allow max history lengths down to 128 seconds. I don't get a crash with @eggrobin's PR. |
stderr.log:
Unfortunately, I can't really provide much more info than this. It was after a fairly long play session, and the problem didn't arise again after restarting KSP. The only relevant actions I can think of was turning number of prediction steps and history length down to the minimum allowed to improve performance.
The text was updated successfully, but these errors were encountered: