Quantcast
Viewing all articles
Browse latest Browse all 3491

Re : CanJS and Memory Leaks

Justin, I agree that the statement should be updated to "CanJS makes it impossible to leak event handlers from discarded controls."

That line of code is actually supposed to be commented out/removed. It was meant to update the control's copy of the status objects, but I don't think it's necessary. 


As far as figuring out what line is causing the leak, I don't know. That is what I was seeking advice from the zen masters for. I do know that if I turn off polling that there is no leak. Except if you click the destroy button. It seems to leave behind detached DOM. But that is the second issue. I'd like to figure out why polling, which is just re-issuing a findAll call and letting live-binding handle the DOM updates is leaking.

So commenting out the polling results in no leak. But that makes sense. The page loads and it's done.

If I leave polling in, but have it do nothing when the poller fires, there seems to be a very very small increase of memory usage over time. 

Also, I am not sure what is related to jsFiddle itself.

What are your thoughts?




Viewing all articles
Browse latest Browse all 3491

Trending Articles