Concept for improved memory management in environments with many tabs

[Horus_Sirius]

Better handling of environments with a large number of tabs is urgently needed. If I have 50 tabs open, it consumes more memory than WSL2 Ubuntu...
I’d say the memory management specifically the automatic tab unloading still doesn't really work properly. It certainly seems very buggy.

Just a quick thought:
Why not simply save or export the active webpage as an *.html file (completely unloading the tab in the background), and then when the user clicks on that tab again reload the cached HTML file from the hard drive?
This would allow you to completely unload the tab in the background, eliminating the memory overhead caused by JavaScript.
A nice feature for later: precisely restoring the scroll position and form data (by creating a webpage state file, like a *.json, alongside the HTML export).
In my view, this system would be highly performant and shouldn't be slow at all (considering the speed of opening a local HTML file).
I often have 60 or more tabs open, and that can consume up to 12 GB of RAM. That is simply far too much. After all, some tabs stay open for days or even weeks.

[Jon]

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.