Potential memory leak in syncer. |
||
Issue descriptionI'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 ~12k objects in syncer that it did not destroy. This is suggestive of a large leak. Each screenshot shows: 1) # of objects created [that have not been destroyed] 2) The stack trace of the code that created the object.
,
Jun 15 2017
,
Jun 15 2017
Screenshots 2, 3, and 4 are allocations for objects synced with server that sync engine needs to keep in memory. We are working on addressing this with USS project (go/uss-dd) Screenshots 1 and 5 correspond to entries in FaviconCache that map from page url to favicon url. I posted a change to cleanup this map when favicon is deleted. (http://crrev.com/c/537114)
,
Jun 19 2017
see: https://bugs.chromium.org/p/chromium/issues/detail?id=734236 Bruce reported a trace with +30k objects.
,
Jun 20 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by pav...@chromium.org
, Jun 13 2017