Render tab is committing a lot of memory that it doesn't seem to be releasing
Reported by
drpi...@gmail.com,
Mar 15 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.18 Safari/537.36 Steps to reproduce the problem: I have a long-running (about 80 hours wall clock, 1 hour CPU) renderer process powering two tabs (one is Slack, the other a page on github) What is the expected behavior? What went wrong? The renderer looks like it is leaking committed memory. Chrome's own task viewer says that the tab is using about 305 MB (I assume this value to represent private working set). Windows, however, says that it's at about 1.7 GB committed/private bytes. Working set for this process peaked at 1.6 GB. Did this work before? Yes Before the switch to oilpan I think? Chrome version: 50.0.2661.18 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 21.0 r0
,
Mar 16 2016
I had this open for about 24 or 36 hours: http://www.eagles.org/dceaglecam/ It grew to about 3.7 GB of committed memory in the renderer process (even though it's using Flash for the video).
,
Apr 1 2016
,
Apr 20 2016
,
Sep 1 2016
I will investigate this issue after new tracing tool is available.
,
Aug 2
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by rnimmagadda@chromium.org
, Mar 16 2016