New issue
Advanced search Search tips

Issue 749612 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

Huge memory leak

Reported by geore...@gmail.com, Jul 27 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.78 Safari/537.36

Steps to reproduce the problem:
We are using chrome headless to run our tests through Karma.

Our tests haven't changed and previously the chrome process reached a peak of ~900MB memory usage throughout the suite.

After updating from version: 59.0.3071.115-1
To: 60.0.3112.78-1

Our tests now trigger out of memory errors as the "Google Chrome" process reaches over 4GB less than 1/3rd of the way through our test suite.

What is the expected behavior?
Memory usage should stay at around 900MB

What went wrong?
Memory usage skyrockets to well over 4GB

Did this work before? N/A 

Chrome version: 60.0.3112.78  Channel: stable
OS Version: Ubuntu 12.0.4
Flash Version: 

Unfortunately our repository is private. I understand there is little information to work with here but there is clearly something very wrong here and found no information about this yet.
 

Comment 1 by geore...@gmail.com, Jul 27 2017

Did this work before? YES

Not sure how to edit the original issue.

Comment 2 by geore...@gmail.com, Jul 27 2017

I should add this occurs both on Mac OSX 10.12.5 (16F73) and Ubuntu 12.04. I have not tried it on other operating systems.
Components: -Blink Internals>Headless
Labels: Needs-Triage-M60 Needs-Bisect

Comment 5 by woxxom@gmail.com, Jul 28 2017

If you can't share the test suite, there's nothing to work on I'm afraid, but maybe you can find which revision of chrome started failing on your end:
https://www.chromium.org/developers/bisect-builds-py

Comment 6 by hdodda@chromium.org, Jul 28 2017

Cc: ligim...@chromium.org
Cc: etienneb@chromium.org
If you can send a way to repro this we can try and bisect it. Feel free to reach out internally also. 

Would be also useful to test with Beta and Canary to see if this could be solved with a cherrypick 
Labels: Needs-Feedback
Adding the label 'Needs-Feedback'.
Cc: pnangunoori@chromium.org
georeith@ - Could you please respond to comment #8 and also please check the issue using latest canary #63.0.3205.0 and please let us know if the issue still persist or not.

Thanks...!!
Cc: rbasuvula@chromium.org
@georeith : Gentle Ping! could you please respond on comment #8.Which would help us to triage the issue further.

Thanks in Advance!
Status: WontFix (was: Unconfirmed)
Mark it as WontFix since there are no feedback from user more than a month.Feel free to raise a new issue if still facing.

Thank You!

Sign in to add a comment