Skip to content

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

Closed
kkaefer opened this issue May 23, 2011 · 5 comments
Closed

Memory leak in Context2d #93

kkaefer opened this issue May 23, 2011 · 5 comments

Comments

@kkaefer
Copy link
Contributor

kkaefer commented May 23, 2011

@tj
Copy link
Contributor

tj commented May 23, 2011

damn. will valgrind it up in a bit

@tj
Copy link
Contributor

tj commented May 24, 2011

on a side note, what app is that? looks similar to node-inspector

@joecroninallen
Copy link

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?

@joecroninallen
Copy link

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.

@zbjornson
Copy link
Collaborator

I think this is fixed (maybe by #1003), but also don't have any repro instructions to go from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants