You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using rapier 0.18.0 through bevy_rapier2d 0.24.0 and noticed occasional attempt to subtract with overflow in update_after_subregion_removal() on subtract from self.subproper_proxy_count. I cloned rapier repo, added some debug and turns out that axis.delete_deleted_proxies_and_endpoints_after_subregion_removal() call returns 1 but self.subproper_proxy_count equals 0 so subtraction causes panic in debug build.
As quick workaround I changed the subtraction to self.subproper_proxy_count = self.subproper_proxy_count.saturating_sub(num_deleted_proxies) but it's out of my rapier knowledge to fix this properly.
I'm attaching log containing debug outputs and stack backtrace + diff with changes I made. I know how to reproduce this problem (~50% chance) with current state of my project so it's possible to provide additional logs if needed. log.txt diff.txt
The text was updated successfully, but these errors were encountered:
I am using rapier 0.18.0 through bevy_rapier2d 0.24.0 and noticed occasional
attempt to subtract with overflow
inupdate_after_subregion_removal()
on subtract fromself.subproper_proxy_count
. I cloned rapier repo, added some debug and turns out thataxis.delete_deleted_proxies_and_endpoints_after_subregion_removal()
call returns 1 butself.subproper_proxy_count
equals 0 so subtraction causes panic in debug build.As quick workaround I changed the subtraction to
self.subproper_proxy_count = self.subproper_proxy_count.saturating_sub(num_deleted_proxies)
but it's out of my rapier knowledge to fix this properly.I'm attaching log containing debug outputs and stack backtrace + diff with changes I made. I know how to reproduce this problem (~50% chance) with current state of my project so it's possible to provide additional logs if needed.
log.txt
diff.txt
The text was updated successfully, but these errors were encountered: