New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 727249 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Possible memory leak

Reported by petargilmour94@gmail.com, May 29 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/58.0.3029.110 Chrome/58.0.3029.110 Safari/537.36

Steps to reproduce the problem:
1.Have several tabs open
2. Browse on few tabs over few hours and watch on task manager as RAM usage increases over time until it hits 100%
3. Chromium goes black or weird graphical glitches happen

The only solution is to try to pull out a tab out of a window, essentialy creating a new window. Or killing all processes and restarting it.

What is the expected behavior?
Unfunctional behavior.

What went wrong?
Memory overload. I have assigned 11GB in vmware for Ubuntu and Chromium manages to eat it all up in 30 min.

Did this work before? N/A 

Chrome version: 58.0.3029.110  Channel: n/a
OS Version: 17.04
Flash Version: not sure

The only solution is to try to pull out a tab out of a window, essentialy creating a new window. Or killing all processes and restarting it.
 
Cc: jbanavatu@chromium.org
Components: Internals>Core
Adding respective component for someone from memory team to help in further triaging this issue.

Thanks!
Cc: kavvaru@chromium.org
Labels: Needs-Feedback
petargilmour94@ could you please confirm are you still facing this issue on latest beta 60.0.3112.72.

Unable to reproduce the issue on windows 7,Ubuntu 14.04 using chrome version 59.0.3071.115 and beta.
Request you once try the issue on latest beta using new profile without any extensions/flags and update the thread if the issue still persists.

Thanks,


Cc: etienneb@chromium.org
We fixed multiple memory leaks recently.

Can you confirm the bug is still present?
If so, can you grab us a trace with a memory dump (memory-infra)?
Status: WontFix (was: Unconfirmed)
Since reporter hasn't responded for comment #2 & 3, closing this issue for now.

petargilmour94@ Could you please file a new bug if the issue still exists in latest chrome builds.

Thanks!

Sign in to add a comment