Created attachment 8879370 [details] memory-report.json.gz I opened my macbook pro tonight and noticed extremely sluggish behavior. It turns out one of the content processes had 7+ GB of heap-unclassified for some reason. This process only had 4 tabs in it: 7,866.99 MB (100.0%) -- explicit ├──7,472.84 MB (94.99%) ── heap-unclassified ├────186.11 MB (02.37%) ++ heap-overhead ├────145.11 MB (01.84%) -- window-objects │ ├───61.85 MB (00.79%) ++ top(https://mail.google.com/mail/u/0/#inbox, id=4294967297) │ ├───45.84 MB (00.58%) ++ top(https://twitter.com/, id=4294967301) │ ├───24.25 MB (00.31%) ++ top(https://calendar.google.com/calendar/render?tab=mc#main_7, id=4294967355) │ └───13.18 MB (00.17%) ++ top(https://bugzilla.mozilla.org/page.cgi?id=mydashboard.html, id=4294967299) └─────62.93 MB (00.80%) ++ (20 tiny) This was after refreshing the twitter tab.
I'm not sure exactly what rev of nightly this was. It was probably only a day or two old, though.
Ben, was this w/ e10s enabled? Multi or non? Was the computer plugged in or on batter? By any chance do you recall having a bunch of gcal notifications? I feel like I've seen that come up before. The next step would be a DMD build, luckily those work on mac again.
Whiteboard: [MemShrink] → [MemShrink:P1]
Summary: 7+ GB of heap-unclassified on nightly → 7+ GB of heap-unclassified on nightly after resuming laptop
(In reply to Eric Rahm [:erahm] (please no mozreview requests) from comment #2) > Ben, was this w/ e10s enabled? Multi or non? Was the computer plugged in or > on batter? By any chance do you recall having a bunch of gcal notifications? > I feel like I've seen that come up before. e10s. multi=4. a/c adapter. Not sure about gcal notifications, but probably a lot of twitter/telegram web notifications. > The next step would be a DMD build, luckily those work on mac again. I haven't been able to reproduce. So not sure how long I would be willing to suffer DMD on the off chance it happens again.
Lets close this for now, feel free to reopen.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.