Fuite: a tool for finding memory leaks in web apps

Post by brundolf » Sat, Dec 18, 2021, 1:46 AM UTC

kohlerm wrote: post #12

sillyquiet wrote: post #10

The only thing more tedious and brain-breaking than tracking down client-side JS memory leaks is tracking down server-side JS (Node) memory leaks.

Serious question, is it really more difficult fir server side JS? At least you don't have to fiddle around with DOM references. The potential impact on the server side is of course potentially bigger.

Post by servytor » Sat, Dec 18, 2021, 2:21 AM UTC

josephg wrote: post #32

brundolf wrote: post #31

Earlier quoted context omitted.

Browsers - Chrome especially - have really fantastic tooling for doing stuff like this. I think there's some way to hook those up to Node, but they're very readily available on the front-end

You can use chrome's tooling directly from nodejs. You just need to invoke nodejs with `node --inspect` (or --inspect-brk to pause before the first line of code is executed). Then open chrome's dev tools. A nodejs icon will magically appear at the top left of the dev tools pane. If you click that it'll open a new window with chrome's debugger, profiler and memory tools working directly with nodejs's v8 instance.