-
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 during flight planning #2640
Comments
Can I get the INFO log? I need it to decode the stack. |
sorry about that, I evidently read the instructions diagonally. INFO.log added to same gist |
Seen again; this time in Galileo, and with no flight plan involved. Just one vessel slowly approaching another in LEO, tuning trajectory with RCS. Additional INFO.log added to same gist. I'm presuming it's the same issue based on the identical "check failed" message |
Decoded stack trace. This is going to be really hard without a journal: Principia/ksp_plugin/interface_renderer.cpp Lines 72 to 79 in 6dc7d90
Principia/ksp_plugin/plugin.cpp Lines 972 to 977 in 6dc7d90
Principia/physics/apsides_body.hpp Lines 34 to 106 in 6dc7d90
Principia/physics/discrete_trajectory_body.hpp Lines 325 to 326 in 6dc7d90
Principia/physics/discrete_trajectory_body.hpp Lines 643 to 644 in 6dc7d90
|
You're (I'm?) in luck, got a semi-reproducible case. 3 crashes in a row, the last 2 with as close to the same steps as I could recall, the last with a journal. link Steps: (I may have got some of these in the wrong order)
[edit: added corresponding INFO.20200716-230953.8156.log to gist) |
Got 2 or 3 more crashes trying to do things differently; in every case, the crash trigger was trying to do keyboard input in a numerical field (at least plan duration and prograde dv; might also have happened with time-until-burn). I seem to be having better luck sticking to the sliders. There's more to it than that, given my 2nd report of getting "the same" crash without a flight plan; but that's now the odd one out. |
Haven't seen this happen again since upgrading from Galileo to Gallai |
now seen in gateaux. trigger was again 'type in flight plan duration box' |
Confirming the stack for the INFO log posted on July 17 (apologies for the delay). Principia/ksp_plugin/interface_renderer.cpp Lines 72 to 79 in 5fa2cec
Principia/ksp_plugin/plugin.cpp Lines 972 to 977 in 5fa2cec
Principia/physics/apsides_body.hpp Lines 34 to 106 in 5fa2cec
Principia/physics/discrete_trajectory_body.hpp Lines 325 to 326 in 5fa2cec
Principia/physics/discrete_trajectory_body.hpp Lines 643 to 644 in 5fa2cec
|
Groan, running into #2778 when trying to replay the journal. |
Replaying this journal was a bit of a pain because, due to #2778, the journal was incorrectly constructed so I had to hack around the corruptions. Anyway, what is happening is that we are trying to compute the closest approaches between one vessel and itself (name I am going to fix the numerical libraries, but we should also understand how that situation can happen, because I wouldn't be surprised if it caused crashes elsewhere. |
re: became its own target: now idea how that might happen, but speculating:
There's a good chance "select the 001" was done via double-clicking. I'm unclear on principia's click-through behavior, but double-click is one way to set/unset targets... |
Using build test-2626, on Windows.
While fiddling with a LEO rendez-vous flight plan, got a crash to desktop. Happened twice in a row in same situation. In both cases I was in the middle of typing a new number in an input box - flight plan duration in one case, burn time start in the other.
FATAL.log:
F0712 00:59:31.438285 14304 discrete_trajectory_body.hpp:644] Check failed: t_min() <= time (-1.28353034162678909e+09 s vs. -nan(ind) s)
ERROR.log and INFO.log
The text was updated successfully, but these errors were encountered: