-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Components should Dropo once are destroyed #288
Comments
You could use |
Sorry to do not clarify, yes, I did that, but destroy does not drop the object from memory. Anyway, good to know that is planned :) |
@deniskolodin is there an outline of how one would make this happen? |
I believe this is now fixed in 0.9 (#651) please re-open otherwise |
Description
I implemented Drop for a component, hoping that is going to be executed, once the component is destroyed, but it doesn't. I think component should drop once destroyed because the memory usage may increase a lot if you instantiate many components of the same time. And this is normal on a webapp that use, for example React.
Expected Results
Components should drop once are destroyed.
Actual Results
Components are never drop
Context (Environment)
Latest git code (0.5, hash bde3612) with Rust 1.27
The text was updated successfully, but these errors were encountered: