DevTools Heap snapshot does not show Detached DOM tree
Reported by
mvishnu0...@gmail.com,
Mar 7 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3364.0 Safari/537.36 Steps to reproduce the problem: 1.Take Heap snapshot using chrome canary 67. What is the expected behavior? What went wrong? chrome canary 67 didn't show Detached DOM tree in V8 heap snapshot for a gmail website.But Detached DOM was seen in V8 heap snapshot of chrome 64. Did this work before? N/A Chrome version: 67.0.3364.0 Channel: canary OS Version: OS X 10.13.3 Flash Version:
,
Mar 9 2018
Thanks for filing the issue! Checked the issue on reported chrome version 67.0.3364.0 using Mac 10.13.1 with the below mentioned steps. 1. Launched Chrome 2. Opened gmail account 3. Devtools->Memory->Heapsnap shot-> Take snapshot Attaching the screen cast of the same. As mentioned in comment#0 where there is no issue in M64, we even checked on it. @Reporter: As ET team is not very clear about "Detached DOM tree in V8 heap snapshot", it would be highly helpful if provided with the screenshots of good and bad behaviour, which helps us to triage the issue in a better.
,
Mar 9 2018
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
,
Mar 11 2018
,
May 2 2018
This bug also occurs on: Google Chrome Version 66.0.3359.139 (official Build) (64-Bit) (Windows 10) Here is a description of the "expected behaviour": https://developers.google.com/web/tools/chrome-devtools/memory-problems/#discover_detached_dom_tree_memory_leaks_with_heap_snapshots |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Mar 8 2018