Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Heap snapshot doesn't complete #3

Closed
scriby opened this Issue · 11 comments

3 participants

@scriby

When I take a heap shapshot, it seems to never complete and the status says "Parsing..."

I'm on node v0.6.8. Are there node version requirements?

@c4milo
Owner

node >0.5.x but I haven't really make any sort of compatibility tests. Does it happen every time you try to take a heap snapshot? Are you using chrome with --remote-debugging-port or http://trac.webkit.org/export/head/trunk/Source/WebCore/inspector/front-end/inspector.html?ws=localhost:1337 ?

@scriby
@c4milo
Owner

I just tried with v0.6.17 and it worked just fine. BTW, parsing is made by the inspector front-end so if you try with chrome canary and --remote-debugging-port it will use an stable version of inspector. You can also try with https://github.com/reid/rampant

@scriby

Do you know if it works on ubuntu? That's what I'm on.

@c4milo
Owner

@scriby it should work. I think @vvo used it in ubuntu with no major problems.

@vvo

I'm on Debian and yes I have seen situations where I had "parsing" and it never finishes. Sometimes I just had to close browser, relaunch node process and be calm.

:)

@c4milo
Owner
@scriby
@vvo

Perhaps it is just a matter of heap profiler file size or race condition dunno. It seemed like this when I had the problem.

@c4milo
Owner

I'll dig further using ubuntu. Indeed, it could be the heap profiler as well.

@c4milo
Owner

I just confirmed this issue. Devtools protocol has changed. As I mentioned above, I'll grab a front-end copy from a stable chrome version to stabilize the project.

@c4milo c4milo closed this issue from a commit
@c4milo Fixes #3 and #5 0805e40
@c4milo c4milo closed this in 0805e40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.