Issue metadata
Sign in to add a comment
|
GC is too lazy in the Worker
Reported by
cool...@gmail.com,
Apr 19 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 Steps to reproduce the problem: 1. download and unpack https://drive.google.com/open?id=0B8rMkU05qoZMaVNTbXBKZkNYU2s 2. run chrome --allow-file-access-from-files coolcmd.html What is the expected behavior? chrome.exe should allocate no more than 100 MB of RAM. What went wrong? chrome.exe allocates up to 3.5 GB of RAM! see screenshot https://drive.google.com/open?id=0B8rMkU05qoZMNWpIdkdsVU5pTTA Did this work before? Yes I do not remember Chrome version: 58.0.3029.81 (64-bit) Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Apr 19 2017
,
Apr 20 2017
If the memory is unused and we don't run into an OOM, this is probably fine. According to the graph we free up the memory when we have grown to a certain threshold. cc memory sheriffs.
,
Apr 21 2017
> If the memory is unused and we don't run into an OOM, this is probably fine. hpayer, please explain, 'fine' because there is no memory leak - or - 'fine' because keeping 3.5 GB of garbage is acceptable behavior of the browser?
,
May 1 2017
This issue causes the browser process to crash due to a lack of memory. Here is the testcase: 1. Open http://coolcmd.tk/tmp/0713344/coolcmd.html 2. In the context menu of the tab, select "duplicate". 3. Now you have 2 testcases from my report in one process. In a few minutes the process will crashed.
,
May 2 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 2 2018
this issue can be closed. chrome 60 allocates 100 mb, as expected.
,
May 3 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by bokan@chromium.org
, Apr 19 2017