Live data from Hacker News

Fuite: a tool for finding memory leaks in web apps

nolanlawson.com

21–30 of 34 posts

Re: Fuite: a tool for finding memory leaks in web apps

#21
post #14

When I worked at Facebook, I worked on a web memory tracking tool I was particularly proud. It went through links, grabbed heap snapshots, diff'ed them, found objects that weren't cleaned up and gave detailed information about its retain chain. You can see a lighting talk I did on it at BlinkOn: https://www.youtube.com/watch?v=JuyaGFApifA&t=1427s&ab_chann... We used it to find a problem fixed in React 18 that caused…

Colleague of bgirard at Facebook here, we are planning to open source the tool in 2022. Great to find someone also working on memory tooling here :) Fuite seems really interesting, will try it out!

Re: Fuite: a tool for finding memory leaks in web apps

#22
post #14

When I worked at Facebook, I worked on a web memory tracking tool I was particularly proud. It went through links, grabbed heap snapshots, diff'ed them, found objects that weren't cleaned up and gave detailed information about its retain chain. You can see a lighting talk I did on it at BlinkOn: https://www.youtube.com/watch?v=JuyaGFApifA&t=1427s&ab_chann... We used it to find a problem fixed in React 18 that caused…

Hi bgirard! I support the FB team that works on this - it's on the roadmap to open source hopefully H1 next year :) It's continued to find significant leaks in other parts of our infra too, so hopefully it will be equally helpful to others. Great to see others looking at memory tools now too - I'll definitely be checking Fuite out

Re: Fuite: a tool for finding memory leaks in web apps

#23
post #13

Almost all SPAs do have memory leaks in my experience. I was once involved in Eclipse Memory Analyzer project(for Java, short MAT), and I mentored a student who built a prototype to support JS in MAT. We easily found significant memory leaks everywhere. That prototype was never released for reasons I cannot comment on in public.

misunderstood, nvm!

Re: Fuite: a tool for finding memory leaks in web apps

#24
post #23
post #13

Almost all SPAs do have memory leaks in my experience. I was once involved in Eclipse Memory Analyzer project(for Java, short MAT), and I mentored a student who built a prototype to support JS in MAT. We easily found significant memory leaks everywhere. That prototype was never released for reasons I cannot comment on in public.

misunderstood, nvm!

I think they meant the student built a prototype leaks detector for SPAs.

Re: Fuite: a tool for finding memory leaks in web apps

#26
Very cool. Looks extremely easy to use which is the difference between people using tools or just reading about them :)

As an aside, I created some tooling for identifying memory leaks in Python apps. Once I started sending the results to Slack and formatting them nicely, I found people ran the tool more frequently. Usability is everything.

Re: Fuite: a tool for finding memory leaks in web apps

#30
post #29

Most SPAs nowadays load JS for new components dynamically on route change. I expect this to increase the stack, too. Just something to keep in mind.

Great point! This is exactly why fuite does a preflight iteration before the "real" iterations. One-time setup costs shouldn't count against the "leak" – only sustained memory growth.
Post reply on HN