Maybe the trick isn&#x27;t to do process-per-tab or 1 content process and 1 UI process but to instead do some kind of &quot;intelligent&quot; number of content processes based on CPU and tab count? Like if you had 50 tabs on a quad core processor you could have 1 UI process and say five content processes?<p>Or another idea, have some kind of upper limit of memory a tab can use before it gets its own process.