Issue metadata
Sign in to add a comment
|
AJAX MEMORY LEAK
Reported by
tomsmith...@gmail.com,
Apr 13 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36 Steps to reproduce the problem: 1. goto https://login.trackserver.co.uk 2. Username martiniquejetrace - No Password 3. Watch memory climb What is the expected behavior? No major impact on system emmory What went wrong? On each AJAX call it gets around 166kb of data, the memory usage in chrome climbs steadily, before crashing. Have tested to point where we removed everything except the AJAX call to isolate the problem. think the data isnt being collected by GC or being released once call complete Did this work before? N/A Chrome version: 57.0.2987.133 Channel: stable OS Version: 10.0 Flash Version:
,
Apr 16 2017
Taking a memory snapshot after a while, it shows an unexpectedly large amount of HTMLCollection objects being kept around. Fixed by issue 707544 , I reckon; I cannot reproduce with current Canary builds. Assigning to mlippautz@ for verification.
,
Apr 18 2017
Thanks Sigbjorn for already checking! This looks like the leak with node lists that was recently fixed. Starting from M58 this should be gone. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dglazkov@chromium.org
, Apr 14 2017Labels: -OS-Windows OS-All
Status: Untriaged (was: Unconfirmed)