Re:Why users cannot create Issues directly
by transcriptase on Thursday January 01, 2026 @11:29PM
(#46461428)
I wonder if a good public flogging would compel chrome and web devs to have 80 tabs take up far less than a gigabyte of memory like they should in a world where optimization wasn’t wholesale abandoned under the assumption that hardware improvements would compensate for their laziness and incompetence.
[ Parent
| on HN ]
Re:Why users cannot create Issues directly
by refulgentis on Friday January 02, 2026 @12:08AM
(#46461612)
They do this stuff.
I’m honestly amazed OP is managing 30 GB regularly. I’d wager it’s a tall tale. It’s sort of perfect troll bait on a forum because you end up with people sounding nuts, defending web browser ram usage, against the common position, that browsers are RAM hogs.
Re:Why users cannot create Issues directly
by abenga on Friday January 02, 2026 @04:46AM
(#46463164)
Is there a straightforward way to have one-process-per tab in browsers without using significant amounts (O(n_tabs)) of memory?
There is no justification for that IMHO. The program text only needs to be in memory once. However, each process probably has its own instance of the JS engine, together with the website's heap data and the JIT-compiled code objects. That adds up.
Re:Why users cannot create Issues directly
by abenga on Friday January 02, 2026 @06:07AM
(#46463645)
I'd very much like a crash in one tab not to kill other tabs. And having per tab sandboxing would be more secure, no?
What do you mean? All these features are provided by process per tab.
Re:Why users cannot create Issues directly
by m-schuetz on Friday January 02, 2026 @07:08AM
(#46464003)
The high memory usage is due to the optimization. Responsiveness, robustness and performance was improved by making each tab independent processes. And that's good. Nobody needs 80 tabs, that's what bookmarks are for.