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
{{ message }}
This repository has been archived by the owner on May 7, 2022. It is now read-only.
Huh, thats interesting. I hadn't noticed that on my end but clearly, it appears to keep grabbing the tile mutably ... ? Should be only updating the one memory position. Shouldn't be making copies of it without dropping it, as per how Rust typically works. Do you have a more specific use case that could possible be doing something odd?
Bevy Tilemap version
0.4
Operating system & version
MacOS 11.3
What you did
tried to update tiles using
Tilemap.get_tile_mut(..)
What you expected to happen
expected the memory usage to remain flat (~80 MB)
What actually happened
memory usage slowly grows and grows (2 GB and counting), visually looks correct.
Additional information
if i comment out the single line of code that does the modification, the memory issue goes away.
The text was updated successfully, but these errors were encountered: