Re:From Two Guys Building Their own Browser
by gruez on Friday August 09, 2019 @09:17AM
(#20653981)
Can you elaborate more on this? My understanding is that on modern browsers, most of the memory usage comes from the tab's contents (pages), or extensions. In both cases they don't scale up with the number of windows.
[ Parent
| on HN ]
Re:From Two Guys Building Their own Browser
by arghwhat on Friday August 09, 2019 @09:40AM
(#20654197)
A lot of browser memory consumption comes with overheads from their multi-process models.
However, that aside, it makes no difference whether you have a window, tab, or "space".
Re:From Two Guys Building Their own Browser
by dleslie on Friday August 09, 2019 @10:09AM
(#20654441)
The multi process model was an improvement. In days past browsers were single process, and suffered from:
- JavaScript on one page dragging down all tabs
- Memory leaks
- JavaScript exploits that crossed tabs
And so on.
Multi process browsing is fantastic.
Re:From Two Guys Building Their own Browser
by arghwhat on Friday August 09, 2019 @12:52PM
(#20656112)
We still have all but the first issue, and that one has nothing to do with multi-process browsing, just multi-threaded processing.
So all we really won was performance regressions (the IPC is expensive) and significantly increased resource consumption.