Issue metadata
Sign in to add a comment
|
Memory profiler stuck when loading heapsnapshots of moderate size
Reported by
davidj...@gmail.com,
Nov 1
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. Take a heapsnapshot of a V8 process with a heap size of 180MB or more. I took mine from a Node app. 2. Load the heapsnapshot into the Chrome DevTools memory profiler What is the expected behavior? It'd be fair to expect the snapshot to be fully loaded within a couple of minutes, especially when on previous versions of Chrome it would take mere seconds for even larger snapshots. What went wrong? Heapsnapshot takes ages to load, as it gets stuck at the "Building dominator tree" stage. I interrupted the load process after a good 15min of waiting for it to finish so I don't really have an idea of how long it takes to fully load but there have been reports of it taking +3 hours for 230MB images. See link: https://github.com/bnoordhuis/node-heapdump/issues/113 Did this work before? Yes Don't know Chrome version: 70.0.3538.77 Channel: stable OS Version: Flash Version: Loading heapsnapshots smaller than 100MB completes within a few seconds. It is much slower than it used to but it finishes within 30 seconds. Anything beyond that shoots up the load times beyond what's reasonable.
,
Nov 2
Thanks for the issue... As per comment #0, Tried to reproduce the issue on reported chrome 70.0.3538.77 Using Ubuntu 17.10. Attaching screenshot for reference. Steps: ----- 1. Launched reported chrome 2. Navigated to https://github.com/bnoordhuis/node-heapdump 3. Downloaded the file and extracted >> Opened Dev tools >> Memory >> tried to load the but the file size was 36kb only @Reporter: It would be really helpful if a sample URL/Extension (with a heap size of 180MB or more) is provided, so that we can investigate the issue further. Thanks.!
,
Nov 2
Hi Phanindra. Here is the snapshot in question: https://drive.google.com/file/d/14j6vh-o-limYnkUvoeGxNcfdrv2dNnNp/view Also forgot to mention that I'm running Chrome on Fedora 27, if that helps.
,
Nov 2
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 2
Thanks for the report. alph@, could you please take a look?
,
Nov 2
The dominators algorithm has O(n^2) worst case complexity. For the given heap dump it actually finished, but it took 7200 seconds on my laptop.
,
Nov 5
Is there nothing that can be done to shorten the amount of time it takes for a snapshot to load then? Can I switch off a feature flag or something to go back to the previous implementation which was able to do it within seconds for a similar data size? |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Nov 2