Re: Process count limit

[Michael Gratton <mike vee net>]

On Fri, Jun 16, 2017 at 6:46 AM, Michael Catanzaro 
<mcatanzaro igalia com> wrote:
> Advantage: significant memory use reduction when many tabs are open 
> Disadvantage: a single crashing tab will crash a quarter of your 
> tabs, instead of only itself Thoughts?

I'd like to see process-per-window, since I typically work with a 
window-per-task model that typically sees something like up to 5 or 6 
windows with 10-15 tabs each commonly being open.

While people shouldn't have to worry about things like managing memory 
use and mitigating web process crashes, process-per-window at least 
gives people a means of doing so without having to mess around with 
settings, since it provides a direct correlation between resource use 
and the most obvious GUI construct - a window. Want to free up some 
memory? Close a browser window.

This currently works with process-per-tab, but won't necessarily work 
if sharing a web process across multiple windows. That sucks since 
people seem to be used to the idea that closing a window can make their 
computer run less slowly, and it breaks that mental model.

Process-per-window obviously won't be an improvement over 
process-per-tab for people that use many windows with one or few tabs 
each, but having 50+ windows open seems unlikely. OTOH, it also doens't 
help people with a single window an 50+ tabs, which might be a more 
common case. Hence n-processes-per-window sees to be the best solution, 
if possible.

Couldn't n-processes-per-window be implemented using 
webkit_web_view_new_with_related_view() magic?

//Mike

--
⊨ Michael Gratton, Percept Wrangler.
⚙ <http://mjog.vee.net/>