Skip to content
This repository has been archived by the owner on May 7, 2022. It is now read-only.

memory leak when updating tiles? #173

Open
kyunghoon opened this issue Sep 10, 2021 · 3 comments
Open

memory leak when updating tiles? #173

kyunghoon opened this issue Sep 10, 2021 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@kyunghoon
Copy link

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.

@kyunghoon kyunghoon added the bug Something isn't working label Sep 10, 2021
@joshuajbouw
Copy link
Owner

joshuajbouw commented Sep 13, 2021

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?

@joshuajbouw
Copy link
Owner

I can confirm the memory leak on tile update. Haven't found a solution yet but still looking.

@joshuajbouw
Copy link
Owner

Turns out it is related to this: bevyengine/bevy#2439

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants