-
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 when staging/decoupling #2641
Comments
INFO.log added. journal's not likely; I haven't seen any pattern to the occurrences |
Decoded stack trace below. I have a vague recollection of seeing out-of-order appends in this code before... Ah, it was #2507. Principia/ksp_plugin/interface.cpp Lines 348 to 353 in 6dc7d90
Principia/ksp_plugin/plugin.cpp Lines 772 to 799 in 6dc7d90
Principia/ksp_plugin/vessel.cpp Lines 234 to 240 in 6dc7d90
Principia/ksp_plugin/vessel.cpp Lines 624 to 672 in 6dc7d90
Principia/physics/discrete_trajectory_body.hpp Lines 181 to 196 in 6dc7d90
|
Last bit of the INFO log:
The "Preparing history" message seems to indicate that we have a newly created vessel with a history containing a single point (the barycentre of the parts at the time when the vessel was created), and that we later try to insert the barycentre of the parts' histories, which has a point before the start of the new history. @lpgagnon: Did you have any engine/RCS burning at the time of the decoupling? (Grasping at straws...) |
In this case, rcs was probably active on the primary vessel ("133 station crew"). "133 station crew Debris" would be a single-part "vessel" (KzProcFairingSide2.TU) being jettisoned, so nothing firing there. |
|
I get this from time to time as well and just as unpredictably/inconsistently, but when I turned on journalling for the two times I could replicate the crash from a save... it didn't crash. |
not seen since Gallois, I believe |
Might the following fatal when decoupling while orbiting Trappist1e be related? To make the Principia logs short here is a fatal at decoupling of fairings of a probe already orbiting 1e by loading a saved game: https://drive.google.com/drive/folders/1rBWbw6P4icUrzB2m8YriKyuL_eRKSjjn?usp=sharing |
INFO.20210430-124413.18744.log I've gotten this crash in Grassmann, info log attached |
To all the people affected by this bug: I don't think we have a hope of solving it without a journal. The logs don't tell us much, other that the curious "Preparing history" message milliseconds before the crash. And as for the stack: well, I have stared at this code for quite some time without finding anything suspicious. Given that someone runs into the problem every few months I have to believe that this is a rare cornercase, and these typically require that I can reproduce them under a debugger. |
Note to self: might be the same crash as #2931, for which we have a journal. |
Crash to desktop when hitting spacebar for a staging even involving at least one decoupler.
I think I've only seen it happen after having reached LEO.
Last seen in test-2626 build, but I've been getting this one every few days since Fuchs; earliest FATAL.log instance is 2020-06-05.
ERROR.log:
INFO.log
The text was updated successfully, but these errors were encountered: