I have noticed, quite by accident, that Google Chrome may have a memory leak. I left an instance running for a week or so (maybe longer, maybe shorter) and found it consuming nearly 1GB in private memory for its single tab. Of course, since Chrome forks its process, it is absolutely a single tab. This tab is Google Analytics Real Time view, so any bug on the web page would again be in Google's court.
UPDATE: This slow memory leak *does* persist in the latest version. It will eventually grow and consume all available virtual memory if left unchecked. The factors that influence this memory leak are unknown at this time. Leaving a single Chrome instance/tab open with Google Analytics Real Time view can reproduce it.
UPDATE2: After getting independent verification in the comments, I reported this bug to Google, so hopefully it gets fixed. It is a surprise anyone noticed, or verified.
UPDATE3: Verified more times since the original Feb 2 report. Bug tracker on Chromium is this issue: http://code.google.com/p/chromium/issues/detail?id=112424 - Continues as of 08/01/2012 (latest build not in screenshot).
UPDATE4: Bug VERIFIED by Google, moved for Triage. New (merged) issue: http://code.google.com/p/chromium/issues/detail?id=140028
I can confirm this issue!
ReplyDeleteExcellent! Well, not excellent I suppose ;p. But, with repetition hopefully some notice will be taken of it, and it will be fixed. I continue to see it here. In the meantime, I have to restart that instance every once and a while. It is very inconvenient and obviously not what the developers intended.
ReplyDeletei also confirm this;
ReplyDeleteat this moment for example, i have just started up chrome, i have 6 tabs opened, and the memory usage is around 500 mb; a few days a single chrome process was eating up over 800mb after a few hours. hope they fix this soon, cause it's starting to become a serious problem.
ditto, noticing it also, back to firefox until it's fixed :(
ReplyDeleteIt seems there has *finally* been activity on this ticket, http://code.google.com/p/chromium/issues/detail?id=140028 . No fix yet, but finally verified as a bug by Google and subject to later processing.
ReplyDelete