New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Memory snapshots analysis #64
Comments
Hi @MaheshDevaraj, please check out the documentation website, specifically the tutorial page which could be useful in understanding the terminal output. Here's the link: https://facebook.github.io/memlab/docs/guides/guides-detached-dom The memory leak trace produced by MemLab is a reference chain that starts from the GC (garbage collector) root and ends at the leaked object. This reference chain is similar to the retainer path in Chrome DevTool, and there are various online resources available to help you debug a retainer path. Although the V8 heap snapshot captures limited source information, there are some effective ways to narrow down the scope and identify the relevant code. One way is to use It's recommended to run the web application being tested with non-minified JS code. |
Hi @JacksonGL , Thanks for the updates. While using Chrome Dev tools memory profile, I'm able to see a link to the code that causes the leak. Can you guide me here? Not sure if I've missed something while using memlab. Memlab logs from my application:- --Similar leaks in this run: 13-- --Similar leaks in this run: 32-- --Similar leaks in this run: 3-- --Similar leaks in this run: 1-- --Similar leaks in this run: 3-- --Similar leaks in this run: 1-- --Similar leaks in this run: 1-- |
Hi,
I'm trying to use memlab for leak detection, once I run the script I get three snapshots and also some logs on the terminal. Tried to understand what they mean but was not able to. I'm actually trying to drill down on a leak and get to the code that causes the leak. Is there a way to analyse the heaps better and get to the exact code that causes the leaks?
Thanks,
Mahesh
The text was updated successfully, but these errors were encountered: