My favorites | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 105529: Memory of closed tabs is sometimes not discarded
2 people starred this issue and may be notified of changes. Back to list
Status:  Untriaged
Owner:  ----


Sign in to add a comment
 
Project Member Reported by dmikurube@chromium.org, Nov 28, 2011
I don't have an exact condition to reproduce it, but it sometimes happens with the following steps.

What steps will reproduce the problem?
1. Open a page 'A' which has a link to a page 'B' which creates many many JS objects.  Many tabs and extensions look like making it easy to reproduce it.
2. Middle-button-click or Ctrl-click the link to the page 'B'.  The page 'B' is opened in a new tab.
3. Check about:memory.  'A' and 'B' are in the same process.
4. Close the new tab.
5. Check about:memory again after some minutes.

In my observation, it frequently happened when :
* # of renderer processes is too many, and
* a link in the page is Ctrl-clicked or middle-button-clicked to open in a new tab.

Observed in Chrome 16, Linux.


What is the expected output? What do you see instead?

Memory of the process sometimes doesn't reduce.  It should always reduce.


Please use labels and text to provide additional information.

Try the attached files.

I guess its root cause might be https://code.google.com/p/chromium/issues/detail?id=102895.  If so, 102895 may happen in any web page.
bloat.html
88 bytes   View   Download
bloat.js
544 bytes   View   Download
Dec 14, 2011
#1 dmikurube@chromium.org
(No comment was entered for this change.)
Labels: TaskForce-Memory
Mar 10, 2013
#2 bugdro...@chromium.org
(No comment was entered for this change.)
Labels: -Area-Internals Cr-Internals
Sign in to add a comment

Powered by Google Project Hosting