NodeJS: debugging memory use

Question

I've got a web crawler that is eating up a bunch of memory. I've tried node --trace-gc as posted in "NodeJS 0.3.1 app leaking memory" and the problem is similar. I am using the async lib for multiple gets to the server.

Can someone point me in the right direction to find the leak? Any good tools or methods that i could use?

Looks like jsdom has a memory leak... groups.google.com/group/nodejs/browse_thread/thread/… I was using the wonderful jquery lib for my crawler which depends on jsdom. — leech
– leech, Commented Aug 24, 2011 at 3:46

goatslacker · Accepted Answer · 2011-08-23 23:56:12Z

5

You could try node-inspector which would allow you to use WebKit's WebInspector.

Get it via npm npm install node-inspector

answered Aug 23, 2011 at 23:56

goatslacker

10.2k2 gold badges17 silver badges15 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

leech Over a year ago

This is fantastic! It does show global/local/context. What's really cool is that you can do breakpoints.

leech Over a year ago

Looks like jsdom has a memory leak... groups.google.com/group/nodejs/browse_thread/thread/… I was using the wonderful jquery lib for my crawler which depends on jsdom.

Glenjamin Over a year ago

You can also take heap snapshots via node-inspector if you require('v8-profiler') somewhere in your code. See the readme for more information: github.com/dannycoates/node-inspector

Collectives™ on Stack Overflow

NodeJS: debugging memory use

1 Answer 1

3 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Related