Status: Unconfirmed
Owner: ----
Labels: Type-Bug Pri-2 OS-All Area-Misc
New issue 9987 by Jason.Strese: Memory oddity.. possibly a memory leak
http://code.google.com/p/chromium/issues/detail?id=9987
Chrome Version : 2.0.174.0 (Developer Build 13499)
URLs (if applicable) : gmail.com
Other browsers tested: N/A
Add OK or FAIL after other browsers where you have tested this issue:
Safari 4: N/A
Firefox 3.x: N/A
IE 7: N/A
IE 8: N/A
What steps will reproduce the problem?
1. Go to (any page I presume, but for example:) gmail.com
2. Observe the memory in the task manager (Chrome's)
3. Open a new tab, close it, open a new tab, close it, open a new tab,
close it (pause for like a second before closing it)
4. Observe that the gmail tab memory usage USED to be high, now it's
substantially lower, however increasing a few KB every second.
What is the expected result?
Explanation below
What happens instead?
""
Please provide any additional information below. Attach a screenshot if
possible.
I opened Chrome with gmail.com as my last tab opened, so it of course
opened as well. I was curious to see how much memory Chrome was using, so I
opened task manager -- 30k for the GMail tab, high.
While I still had the task manager opened, I went to test a blank page --
then after I observed its memory usage, I closed it. Here's where I noticed
something odd, a pattern: when you open a new tab, and take the gmail tab
out of focus, it loses memory -- possibly the GC -- however, when you take
it out of focus, and back into focus, over and over, it keeps losing memory
due to, what I assume is, the garbage collector.
My tab memory usage started out at 30K+, and when I was done toying around
(about 15 open-closes), it was at 8K. Moreover, the memory usage kept
crawling up a few K every second -- until reaching about 27K, then it
stopped (I'm observing this now, from a separate tab).
-- One of these scenarios is true, or I'm wrong. --
1. Garbage collecting gets rid of USELESS, UNUSED memory -- so why does
your GC process (once again, I -THINK- this is the GC that's bugged) take
away memory, only to be re allocated in the matter of a minute? It's
obviously throwing away USEFUL memory, only to have that memory re
allocated, right?
2. There's a memory leak somewhere, and GC isn't catching/cleaning it up.
So what I observed might have been GC at work, then the memory leak raising
the memory back up. HOWEVER, why would the assumed memory leak only go to
27k memory? Shouldn't it go higher? What's stopping it?
There's something odd.. this shouldn't happen, or should it? You decide =)
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
