Memory Usage Dramatically Increases Over a Short Period of Time |
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.76 Safari/537.36 Steps to reproduce the problem: Cannot reproduce with control, seems to happen "randomly". (Though I'm sure it's not, I just can't correlate it to anything.) What is the expected behavior? What went wrong? The memory usage of the main "Browser" process (parent process of all the Chrome children) spikes dramatically, to the point of causing excessive swapping behavior on my laptop. This renders my laptop completely unusable for 30s-3mins, depending on memory pressure. (The mouse won't even move.) I've only been able to determine this by leaving "top" open in a pinned window, top will update once every 15-20 seconds during this period, but memory growth will hit 5-6 GB on this one process. If I disable swap, my computer does not become unusable, but Chrome gets killed by oom-killer. This happens anywhere from 3x/hour to 3x/day, and I can't seem to find any particular behavior that can reproducibly trigger the issue. Did this work before? Yes At least ~M52? Chrome version: 56.0.2924.76 Channel: beta OS Version: 4.2.0-42-generic Flash Version:
,
Feb 10 2017
Tested this issue in Ubuntu 14.04 with chrome #56.0.2924.76 These are the steps followed, opened the chrome and played multiple youtube videos for 5 hrs. Didn't observed any high spike for chrome memory usage for this time, used the top command to verify the memory usage. davidtomaschik@ could you please try the same scenario with clean profile with no apps & extensions and let us know your observations.
,
Feb 16 2017
,
Feb 16 2017
Same thing happening here but on Windows 10 58.0.3013.0 canary (64-bit), it's only been happening for the last few builds. A low on memory popup appears that tells me I should close Chrome.
,
Jul 27 2017
,
May 23 2018
As there is no action on this issue for long time closing this issue. Request you to update your Chrome to latest #66.0.3359.181 and verify. Feel free to file a new issue if the issue is still reproduced at your end. Thanks! |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nyerramilli@chromium.org
, Feb 9 2017