Closed TheDude53 closed 3 years ago
Looks like the reload and reset routine is overlapping and causing an unhandled exception.
Reloading when backspace works from the top menu but using the keyboard shortcut:
Thread 1 "RoR" received signal SIGSEGV, Segmentation fault.
0x00005555558214b4 in RoR::Actor::SyncReset (this=0x55555de39450, reset_position=<optimized out>)
at /home/babis/Downloads/ror-dependencies/rigs-of-rods/source/main/physics/Actor.cpp:1525
1525 ar_nodes[i].Velocity = Vector3::ZERO;
(gdb) bt
#0 0x00005555558214b4 in RoR::Actor::SyncReset (this=0x55555de39450, reset_position=<optimized out>)
at /home/babis/Downloads/ror-dependencies/rigs-of-rods/source/main/physics/Actor.cpp:1525
#1 0x0000555555617517 in RoR::GameContext::ModifyActor (this=0x555555be3e00 <RoR::App::g_game_context>, rq=...)
at /home/babis/Downloads/ror-dependencies/rigs-of-rods/source/main/GameContext.cpp:266
#2 0x00005555555eb4bb in main (argc=<optimized out>, argv=<optimized out>)
at /home/babis/Downloads/ror-dependencies/rigs-of-rods/source/main/main.cpp:595
or
Thread 1 "RoR" received signal SIGSEGV, Segmentation fault.
0x0000555555821463 in RoR::Actor::SyncReset (this=0x55555f01ada0, reset_position=<optimized out>) at /usr/include/c++/10.2.0/bits/stl_vector.h:1043
1043 operator[](size_type __n) _GLIBCXX_NOEXCEPT
(gdb) bt
#0 0x0000555555821463 in RoR::Actor::SyncReset (this=0x55555f01ada0, reset_position=<optimized out>)
at /usr/include/c++/10.2.0/bits/stl_vector.h:1043
#1 0x0000555555617527 in RoR::GameContext::ModifyActor (this=0x555555be3e00 <RoR::App::g_game_context>, rq=...)
at /home/babis/Downloads/ror-dependencies/rigs-of-rods/source/main/GameContext.cpp:266
#2 0x00005555555eb4d1 in main (argc=<optimized out>, argv=<optimized out>)
at /home/babis/Downloads/ror-dependencies/rigs-of-rods/source/main/main.cpp:595
I'm unable to reproduce it with current master, the vehicle always respawns fine and remains in "interactive reset" mode.
Tried with scania-milktruck, Desperado and MeanMachine-monster, both Debug and Release dev builds.
Yes, no segfault now.
Steps to reproduce
Expected behaviour
RoR shouldn't crash, and possibly instead ignore Ctrl+Shift+R as there is no mapping for it in
input.map
(or at least none that I could find)Actual behaviour
Rigs of Rods freezes briefly before crashing
System configuration
OS: Windows 10 Home 64-bit Renderer used: DirectX 9 GPU: Intel(R) Iris(R) Xe Graphics
Additional information, logs and screenshots
RoR.log: