4 ms·
Same for me. I discovered it was Slack that had some live leak, one time it had eaten 33GB of RAM. An auto-reload extesion did the trick to prevent it from goin
by magicalhippo 3y ago
Same for me. I discovered it was Slack that had some live leak, one time it had eaten 33GB of RAM. An auto-reload extesion did the trick to prevent it from going too far, but I'd really wish Firefox would handle it more gracefully.
Unless I say so, a normal web page shouldn't eat gigs of RAM or tons of CPU.
- galangalalgol 3y agoSo wouldn't chrome have the same issue?
- plorkyeran 3y agoI do have similar problems with chrome and have to restart it every few days.
- kefabean 3y agoAnd Safari on MacOS. It occasionally gets into a state where it becomes unresponsive to clicking on links.
- Zardoz84 3y agoI noticed a similar problem with Twitch client.
- dwattttt 3y agoGiven how well web pages are coded, I'm curious whether a Firefox that's browsed to 50 static pages fares. At some point the pages themselves should get some blame (and yes, they can be offloaded, but we're back to balancing responsiveness & long term resource usage, and people are complaining about the pages being reloaded after exit as a delay)
- cpeterso 3y agoChrome recently added a setting so you can display a tab’s memory usage when you mouse over the tab. In Firefox, you can check the memory usage of each tab in Firefox’s Task Manager (about:processes). https://support.mozilla.org/en-US/kb/task-manager-tabs-or-extensions-are-slowing-firefox https://support.mozilla.org/en-US/kb/task-manager-tabs-or-ex...
- magicalhippo 3y agoOr use the much more detailed about:memory, that's how I discovered the live leak.