Closed IceGuye closed 1 year ago
When I adjusted the half-extend of a collider, if I press the down arrow to reduce the number, it is a chance the editor goes panicked and crashed. Video demonstrated this bug is here: https://user-images.githubusercontent.com/7291463/230802150-6eb55c17-7b78-47b5-98ac-0416f03ed809.mp4
Backtrace message shows:
thread 'main' panicked at 'assertion failed:(left != right) left:0, right:0', /home/qs/.cargo/registry/src/github.com-1ecc6299db9ec823/rapier3d-0.17.2/src/geometry/broad_phase_multi_sap/sap_utils.rs:13:5 stack backtrace: 0: rust_begin_unwind at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library/std/src/panicking.rs:575:5 1: core::panicking::panic_fmt at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library/core/src/panicking.rs:65:14 2: core::panicking::assert_failed_inner 3: core::panicking::assert_failed 4: rapier3d::geometry::broad_phase_multi_sap::sap_axis::SAPAxis::update_endpoints 5: rapier3d::geometry::broad_phase_multi_sap::sap_region::SAPRegion::update 6: rapier3d::geometry::broad_phase_multi_sap::broad_phase::BroadPhase::update 7: rapier3d::pipeline::physics_pipeline::PhysicsPipeline::detect_collisions 8: rapier3d::pipeline::physics_pipeline::PhysicsPipeline::step 9: fyrox::scene::graph::physics::PhysicsWorld::update 10: fyrox::scene::graph::Graph::update 11: fyrox::engine::Engine::pre_update 12: fyroxed_base::update 13: fyroxed_base::Editor::run::{{closure}} 14: winit::platform_impl::platform::x11::EventLoop<T>::run_return::single_iteration 15: winit::platform_impl::platform::x11::EventLoop<T>::run 16: winit::platform_impl::platform::EventLoop<T>::run 17: winit::event_loop::EventLoop<T>::run 18: fyroxed_base::Editor::run 19: editor::main note: Some details are omitted, run withRUST_BACKTRACE=fullfor a verbose backtrace.
thread 'main' panicked at 'assertion failed:
left:
, right:
', /home/qs/.cargo/registry/src/github.com-1ecc6299db9ec823/rapier3d-0.17.2/src/geometry/broad_phase_multi_sap/sap_utils.rs:13:5 stack backtrace: 0: rust_begin_unwind at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library/std/src/panicking.rs:575:5 1: core::panicking::panic_fmt at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library/core/src/panicking.rs:65:14 2: core::panicking::assert_failed_inner 3: core::panicking::assert_failed 4: rapier3d::geometry::broad_phase_multi_sap::sap_axis::SAPAxis::update_endpoints 5: rapier3d::geometry::broad_phase_multi_sap::sap_region::SAPRegion::update 6: rapier3d::geometry::broad_phase_multi_sap::broad_phase::BroadPhase::update 7: rapier3d::pipeline::physics_pipeline::PhysicsPipeline::detect_collisions 8: rapier3d::pipeline::physics_pipeline::PhysicsPipeline::step 9: fyrox::scene::graph::physics::PhysicsWorld::update 10: fyrox::scene::graph::Graph::update 11: fyrox::engine::Engine::pre_update 12: fyroxed_base::update 13: fyroxed_base::Editor::run::{{closure}} 14: winit::platform_impl::platform::x11::EventLoop<T>::run_return::single_iteration 15: winit::platform_impl::platform::x11::EventLoop<T>::run 16: winit::platform_impl::platform::EventLoop<T>::run 17: winit::event_loop::EventLoop<T>::run 18: fyroxed_base::Editor::run 19: editor::main note: Some details are omitted, run with
for a verbose backtrace.
When I adjusted the half-extend of a collider, if I press the down arrow to reduce the number, it is a chance the editor goes panicked and crashed. Video demonstrated this bug is here: https://user-images.githubusercontent.com/7291463/230802150-6eb55c17-7b78-47b5-98ac-0416f03ed809.mp4
Backtrace message shows:
thread 'main' panicked at 'assertion failed:
(left != right)left:
0, right:
0', /home/qs/.cargo/registry/src/github.com-1ecc6299db9ec823/rapier3d-0.17.2/src/geometry/broad_phase_multi_sap/sap_utils.rs:13:5 stack backtrace: 0: rust_begin_unwind at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library/std/src/panicking.rs:575:5 1: core::panicking::panic_fmt at /rustc/90743e7298aca107ddaa0c202a4d3604e29bfeb6/library/core/src/panicking.rs:65:14 2: core::panicking::assert_failed_inner 3: core::panicking::assert_failed 4: rapier3d::geometry::broad_phase_multi_sap::sap_axis::SAPAxis::update_endpoints 5: rapier3d::geometry::broad_phase_multi_sap::sap_region::SAPRegion::update 6: rapier3d::geometry::broad_phase_multi_sap::broad_phase::BroadPhase::update 7: rapier3d::pipeline::physics_pipeline::PhysicsPipeline::detect_collisions 8: rapier3d::pipeline::physics_pipeline::PhysicsPipeline::step 9: fyrox::scene::graph::physics::PhysicsWorld::update 10: fyrox::scene::graph::Graph::update 11: fyrox::engine::Engine::pre_update 12: fyroxed_base::update 13: fyroxed_base::Editor::run::{{closure}} 14: winit::platform_impl::platform::x11::EventLoop<T>::run_return::single_iteration 15: winit::platform_impl::platform::x11::EventLoop<T>::run 16: winit::platform_impl::platform::EventLoop<T>::run 17: winit::event_loop::EventLoop<T>::run 18: fyroxed_base::Editor::run 19: editor::main note: Some details are omitted, run with
RUST_BACKTRACE=fullfor a verbose backtrace.