-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Memory leak in Context2d #93
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
Comments
damn. will valgrind it up in a bit |
on a side note, what app is that? looks similar to node-inspector |
I was investigating memory leaks in my app and discovered that I had a memory leak from the Context 2d. I was wondering if any progress has been made in resolving this? |
Update to my previous comment: It turns out the the memory leak was in fact in my code. I was defining the onload and onerror closures in such a way where they were not getting garbage collected. By using fs.readFile rather than the onload, I was able to avoid having the closure persisting in memory. |
I think this is fixed (maybe by #1003), but also don't have any repro instructions to go from. |
The text was updated successfully, but these errors were encountered: