-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
memory leak? #17
Comments
Could you let me know if you take a memory snapshot of the editor or player? Also, would you be able to provide a simple step-by-step guide on how I can reproduce the issue? |
Check the video attachment. 20241121_193501.mp4 |
…pshot, then closing and reopening Heap Explorer to take another snapshot. This changeset resolves issue #17.
Thank you for the extra information. I managed to reproduce the memory leak and have fixed it. The fix is included in Heap Explorer 4.3, which I've just released. Please let me know if this resolves the issue for you too. |
Seems to fix a little bit. Now not every time close and open to analyze makes memory goes up.But still, when window is closed, memory won't go down.Also, if redo Capture again for several times without closing the window, memory usage goes up rapidly. |
Everytime when I do "Capture and Analyze", Unity memory usage go up, and it will never go down again, even if after I close Heap Explorer window.
Unity Editor verison: 2019.4.40.f1
The text was updated successfully, but these errors were encountered: