Issue metadata
Sign in to add a comment
|
Timeline tool shows DOM node leak but memory profiler shows no leaked objects (again!)
Reported by
simon.al...@gmail.com,
Apr 7 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: Please see Bug 495102 . The symptoms are exactly the same. https://bugs.chromium.org/p/chromium/issues/detail?id=495102# What is the expected behavior? See Bug 495102 What went wrong? See Bug 495102 Did this work before? Yes Don't know for sure, but it was working in version 45 (and many others) Chrome version: 57.0.2987.133 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: I reported 495102 and it was fixed, but it appears to be back (or something very similar is back). I have attached the test-app.html file used in the 495102 report as it reproduces the issue. Please take this seriously, as our web app eventually crashes once it has consumed all the system memory.
,
Apr 10 2017
,
Apr 10 2017
,
Apr 11 2017
Removing the Needs-Bisect label as its already been assigned, please add it again if there is any minimal steps and expected result to investigate from TE side. The result is same on M40,M45, latest stable 57.0.2987.133 and canary 59.0.3067.0 when navigated to the above html file.
,
Dec 4
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by simon.al...@gmail.com
, Apr 7 2017