Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

How to identify closures #3

OrangeDog opened this Issue Oct 31, 2011 · 3 comments


None yet
2 participants

Maybe get some input from @fgnass too?

Trying to debug a memory leak, and its only retainer is marked (closure). Unfortunately there are hundreds of anonymous functions and callbacks in my code. How could I go about labelling them (or getting v8 to label them) without manually re-writing the whole thing?


felixge commented Nov 1, 2011

I could be wrong, but I think you need to name them.

Tried a quick sed to replace function( with function file_line(, but it didn't show up in the profiler.


ghost commented Jun 11, 2012

I cannot see the profiler tab... my environment is:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment