Potential memory leak in ProcessTabRestoreServiceNotification |
||||||
Issue descriptionWe are running a chrome webbrowser for multiple days with an extension that keeps opening/closing tabs. The browser is instrumented with MEMLOG (out-of-process heap profiling) which is collecting metrics on memory allocations. By looking to remaining allocated objects, we can see that there is potentially a memory leak in: JumpList::ProcessTabRestoreServiceNotification() The attached image show some of the top stackframes and the allocations stackframes.
,
Nov 3 2017
+brucedawson, who did some fixes in jump list code not too long ago.
,
Nov 3 2017
+chengx, who recently changed this class quite a bit.
,
Nov 3 2017
I'll take a look. Thanks.
,
Nov 3 2017
The three reports we received from our test lab shows malloc with > 1.2G of private memory. This is really frightening. Also note, this is part of M63. We may think back-porting the patch.
,
Nov 3 2017
I agree that this is indeed frightening. Although I have rewritten almost the whole jumplist code to fix a bunch of severe bugs in it, I don't think I have touched the code inside JumpList::ProcessTabRestoreServiceNotification. I renamed the method though. Besides, I have landed 60+ patches to the jumplist class in the past few months, so the back-porting idea may not work. Anyway, I will take a look shortly for sure. Was this issue there before M63?
,
Nov 3 2017
We do not have enough users running HP-OOP yet, so I can't easily tell when this bug make it's way into the code. Also note, they were ASAN build (can't tell if this useful). The load doesn't represent a normal user. The extension installed keep opening tabs to google.com and close it quickly. Which may help figuring out what is happening. I know that some changes occurred recently on the way we detect a process shutdown. Is that something that may cause trouble here? I'm gonna keep eyes on our dashboard and bringing back information on this bug. 1) What is the oldest version with that bug 2) Is that bug still in M64.
,
Dec 5
etienneb@: Is there any update on this one? Thanks!
,
Dec 11
If the bug is too old, let close it. The current memlog pipeline will catch it again. I do not recall seeing these stackframes on the dashboard.
,
Dec 11
Thx, Etienne, closing - I figured the memlog pipeline would tell us if this were still happening. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by erikc...@chromium.org
, Nov 3 2017