New issue
Advanced search Search tips

Issue 732870 link

Starred by 1 user
Status: Assigned
Owner:
rdevlin....@chromium.org
Cc:
etienneb@chromium.org
erikc...@chromium.org
mac-bugs-priority@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: Bug



Sign in to add a comment

Potential memory leak in policy::ConfigurationPolicyPrefStore::Refresh().

Project Member Reported by erikc...@chromium.org, Jun 13 2017 
I've been looking at sources of browser memory bloat by using native heap profiling on my own browser. Full details:
https://docs.google.com/document/d/1fN5balfyrd7sRpd6DRaUI1TwoOwYjLyRSd7mwZT5US8/edit#

Over the course of 1 week, the browser process created ~100k objects in policy::ConfigurationPolicyPrefStore::Refresh() that it did not destroy.

This is suggestive of a large leak. rdevlin, can you take a look?
Screen Shot 2017-06-13 at 10.42.20 AM.png
243 KB View Download
Screen Shot 2017-06-13 at 10.42.15 AM.png
192 KB View Download
Screen Shot 2017-06-13 at 10.42.02 AM.png
179 KB View Download
Screen Shot 2017-06-13 at 10.41.46 AM.png
251 KB View Download

Comment 1 by erikc...@chromium.org, Jun 13 2017 

Each screenshot shows:
  1) # of objects created [that have not been destroyed]
  2) The stack trace of the code that created the object.
►

Sign in to add a comment