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
Using Rapier 0.17.2 in a game where objects spawn and despawn (but the total number remains roughly constant), I observe a linear increase in total QueryPipeline memory usage over time (ultimately harming bandwidth usage).
Here I plot serialized size, in bytes, of the QueryPipeline (y axis) against game tick # (x axis):
I was able to reproduce this on Rapier 0.18.0 (warning: don't mouse over the testbed window as it will crash):
Using Rapier
0.17.2
in a game where objects spawn and despawn (but the total number remains roughly constant), I observe a linear increase in totalQueryPipeline
memory usage over time (ultimately harming bandwidth usage).Here I plot serialized size, in bytes, of the
QueryPipeline
(y axis) against game tick # (x axis):I was able to reproduce this on Rapier
0.18.0
(warning: don't mouse over the testbed window as it will crash):At first I thought the
refit_and_rebalance
algorithm wasn't running but, as far as I can tell, it is.Workaround
Applications can occasionally reset the query pipeline:
The text was updated successfully, but these errors were encountered: