New issue
Advanced search Search tips

Issue 662729 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Nov 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Memory leak in kernel_task when using certain webapps

Reported by calebjam...@xwiki.com, Nov 6 2016

Issue description

Chrome Version       : Google Chrome	54.0.2840.87 (Official Build) (64-bit)
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari:
    Firefox: 49.0.2 OK
         IE:

What steps will reproduce the problem?
(1) Install patchwork https://ssbc.github.io/patchwork/ (this is an app which reliably triggers the issue)
(2) Navigate to localhost:7777 and browse patchwork for a while
(3) Leave chrome on patchwork page overnight - perhaps a few days

What is the expected result?
Chrome continues to work as it does when navigated to other sites or if the webapp is faulty, it crashes the tab and it becomes a sad-tab.

What happens instead?
Mac OSX complains that it is out of memory and begins proposing to stop various processes, closer inspection shows that kernel_task is using 6 gigabytes of memory, killing chrome causes this memory usage to drop to 2 gigs.

Please provide any additional information below. Attach a screenshot if
possible.

The only service I can find which reproduces this issue is patchwork which unfortunately you must install locally because it is a p2p webapp.

Running patchwork in firefox and everything else in chrome keeps my machine working ok still.

Machine is a MacBook Pro (Retina, 15-inch, Mid 2015) Yosemite 10.10.5 (14F2009) with 16GB of ram.
 
Cc: rbasuvula@chromium.org
Labels: TE-NeedsTriageHelp
This looks like out of scope for TE, hence adding the respective label for it to  triage further.
Project Member

Comment 2 by sheriffbot@chromium.org, Nov 8 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment