MemLab: An open source framework for finding JavaScript memory leaks
engineering.fb.com
MemLab: An open source framework for finding JavaScript memory leaks
1–10 of 15 posts
Re: MemLab: An open source framework for finding JavaScript memory leaks
#2Ah I think this was mentioned in a comment on a previous thread:
https://news.ycombinator.com/item?id=29595441
Glad to see it finally open sourced!
Re: MemLab: An open source framework for finding JavaScript memory leaks
#3Ah I think this was mentioned in a comment on a previous thread: https://news.ycombinator.com/item?id=29595441 Glad to see it finally open sourced!
Yup, that's the previous thread :)
Re: MemLab: An open source framework for finding JavaScript memory leaks
#4If there is any memory leaks in a garbage-collected language, isn't it a bug of V8 instead?
Re: MemLab: An open source framework for finding JavaScript memory leaks
#5If there is any memory leaks in a garbage-collected language, isn't it a bug of V8 instead?
You can just leak memory by leaving references to it around. Sometimes called memory abandonment.
With some systems you can pin it and forget to unpin it.
Re: MemLab: An open source framework for finding JavaScript memory leaks
#6Memory leak because of console.log? Wow, news to me. Not that I really ever use it for much since I believe in writing unit tests over outputting logs to the console. But I can see how others might get bitten by this for sure.
Re: MemLab: An open source framework for finding JavaScript memory leaks
#7its incredibly difficult to debug memory leak even with dev tools, I will look into this and hope it helps
Re: MemLab: An open source framework for finding JavaScript memory leaks
#8Memory leak because of console.log? Wow, news to me. Not that I really ever use it for much since I believe in writing unit tests over outputting logs to the console. But I can see how others might get bitten by this for sure.
Can confirm, have been bitten in production. Therefore we have a lint rule that disallows `console.log` for production builds.
Re: MemLab: An open source framework for finding JavaScript memory leaks
#9its incredibly difficult to debug memory leak even with dev tools, I will look into this and hope it helps
I learned recently that Edge has a "Detached Elements" panel that identifies leaked DOM elements and the code / object holding the reference.
It basically automates the process of diff'ing heap snapshots.
Re: MemLab: An open source framework for finding JavaScript memory leaks
#10Node heap profiler in chrome is pretty good, often it will show the largest retainers and if your hookes to a live vm (not a snapshot) you can inspect the object and eventually go "oh yeah this array just grows and grows..."