I've read through the comments here and on Reddit, and it does sound like leaking windows (ghost windows), which is what is showing up in the about:memory report. For anybody who is experiencing this issue, if they want to see if they are experiencing ghost windows without waiting until they build up so much that it brings your system to a halt, they can go to about:memory, click on "minimize memory usage", wait for that to finish, then click on "measure". In the resulting report, you can search for ghost-windows, and see if there are any entries that are non-zero. (In reply to Mike Conley (:mconley) (:⚙️) from comment #54) > Hey mccr8, what's the best way for taiteclark1 to diagnose this ghost window problem? I'm looking at their extension list, and I'm not seeing anything obvious. Any suggestions? It could be anything, really. Looking at bug 1651416 comment 7, somebody says they found a (regression range)[https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e4b11f027efc1f8c2710ae3f52487a8f10a8fb39&tochange=bc973d369db58faf254ddcef201089dc28e6d3be] for the issue. There aren't really all that many changesets in there, once you ignore the wpt stuff. Baku has some cookie-related changes, which is suspicious given that there are a few cooking and tracking related addons in that list, but as far as I can tell his patches were backed out and so they wouldn't actually be in the build. It still might be worth looking at cookie related addons. There's also a number of Sync changes in that range, so maybe it could be related to that?
Bug 1658571 Comment 56 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I've read through the comments here and on Reddit, and it does sound like leaking windows (ghost windows), which is what is showing up in the about:memory report. For anybody who is experiencing this issue, if they want to see if they are experiencing ghost windows without waiting until they build up so much that it brings your system to a halt, they can go to about:memory, click on "minimize memory usage", wait for that to finish, then click on "measure". In the resulting report, you can search for ghost-windows, and see if there are any entries that are non-zero. (In reply to Mike Conley (:mconley) (:⚙️) from comment #54) > Hey mccr8, what's the best way for taiteclark1 to diagnose this ghost window problem? I'm looking at their extension list, and I'm not seeing anything obvious. Any suggestions? It could be anything, really. Looking at bug 1651416 comment 7, somebody says they found a [regression range](https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e4b11f027efc1f8c2710ae3f52487a8f10a8fb39&tochange=bc973d369db58faf254ddcef201089dc28e6d3be) for the issue. There aren't really all that many changesets in there, once you ignore the wpt stuff. Baku has some cookie-related changes, which is suspicious given that there are a few cooking and tracking related addons in that list, but as far as I can tell his patches were backed out and so they wouldn't actually be in the build. It still might be worth looking at cookie related addons. There's also a number of Sync changes in that range, so maybe it could be related to that?