Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Memory Leak when attaching property to template in event #1997
i revisited the memory test i did a while ago while searching for leaks i'm seeing still in my app.
If you uncomment
Shouldn't the template instance passed into the event get cleared up properly as well?
Hi @frozeman, thanks for keeping us on our toes with memory leaks :)
I've confirmed this issue, and it comes down to event handlers not being cleaned up when a component is destroyed (see a comment in domrange.js:
I'm happy you found a workaround in the meanwhile. We should fix this, but since @dgreensp is rehauling the Blaze component API and DOM range-tracking mechanism it's best to wait until that's done to see if it's been resolved or not.
But i guess in the future when more and more goes towards single page apps we will see memory management becoming a bigger issue.
You can check out the beta of our app here http://beta.tunedin.de. The memory is kind of stable (except for that image slider on the featured page), but its a lot ± 100mb.
Sorry german is hardcoded for now you can help yourself by typing
@avital Is there any progress or a workaround for this issue? I have a kanban board I'm building in meteor, and when switching between boards (similar to the TODO list example) with ~100 tasks, my memory usage rockets up. If I quickly click between two boards I can get the memory footprint well over 200mb in a few minutes.
As with @frozemanm I've narrowed this down to so many templates being created/destroyed.