Getting in a orbit that fly pass 4 outer planets in a row in RSS will crash the game when time warp

[xiaoqianWX]

For some reason, that happened every time trying to time warp, to even 2x
Hardware:
CPU: i7-6700HQ
RAM: 16g DDR4
Graphic: GTX 1070
because this is on my friends' computer, and he's not online yet, so I will sent principia.dll when he sent it to me.
By changing into a orbit that is far enough from Neptune can warp to 100x without crashing the game, but we are still passing Saturn, and we have to get in a orbit like this.

[xiaoqianWX]

WARNING.20180627-125954.17364.txt

[xiaoqianWX]

INFO.20180627-125559.17364.txt
and this one

[xiaoqianWX]

The game freeze itself when warping, for minutes, so I just quit the game. So there is no crash logs

[pleroy]

Note for ourselves: partially decoded stack trace:

integrators/embedded_explicit_runge_kutta_nyström_integrator_body.hpp:178

ksp_plugin/vessel.cpp:252
ksp_plugin/interface.cpp:987

It appears that we broke stack traces with the DLL split 5 months ago. This doesn't help debugging this problem.

[pleroy]

Note for ourselves: full trace obtained by guessing the base address of the Physics DLL until I got something sensible:

physics/ephemeris_body.hpp:973
physics/ephemeris_body.hpp:1065
physics/ephemeris_body.hpp:1095
physics/ephemeris_body.hpp:467

integrators/embedded_explicit_runge_kutta_nyström_integrator_body.hpp:178
physics/ephemeris_body.hpp:516
ksp_plugin/vessel.cpp:252
ksp_plugin/interface.cpp:987

and the failure message:

F0627 12:59:54.624032 11408 continuous_trajectory_body.hpp:161] Check failed: t_max() >= time (+3.75912000000000000e+08 s vs. +3.75912000000000119e+08 s) 

This could be related to #1839, which is a bug where I could never figure out what was happening.

[pleroy]

@EthanWang706: I think that I have figured out what's happening, so I don't need more data from you. The problem appears to be a subtle numerical error in the integrator used to compute the prediction, see #1867.

The fix will be in version Δημόκριτος, to be released around July 13th.

Unfortunately I don't have a good work-around for you in the meantime, but I suggest that you try to tweak the Tolerance parameter of the prediction in the Prediction Settings in the main Principia UI. With some luck, reducing the tolerance might cause the problem to go away. If you try this and it helps, please let us know by commenting on this issue.

Thank you for taking the time to report this problem.

[xiaoqianWX]

many thanks