> I was under the impression that because e10s is only a single process for all content (at least right now) a background tab can still negatively affect the foreground tab.
That's right, but we also tested e10s in the process-per-tab configuration > Have we ever considered building something like the unload tab addon into the platform or Firefox directly? We have talked about it (BarTab Heavy is another example) and the code that Yoric wrote for measuring per-compartment main-thread CPU-usage in about:performance could be used for this. It's unclear how to prioritize it though because doing 100% reliable heavy tab detection will require non-trivial effort (see issues with slow-addon info bar) and the background tab problem will mostly be mitigated by process-per-tab e10s. On Fri, Jun 26, 2015 at 5:12 PM, Nick Fitzgerald <nfitzger...@mozilla.com> wrote: > From your blog post: > > > Heavy activity in background tabs badly affects desktop Firefox’s > scrolling performance1 (much worse than other browsers — we need E10S) > > I was under the impression that because e10s is only a single process for > all content (at least right now) a background tab can still negatively > affect the foreground tab. > > Have we ever considered building something like the unload tab addon into > the platform or Firefox directly? I know we do some throttling of timeouts, > but perhaps we should also consider this heavier handed approach when there > are many tabs open. > > https://addons.mozilla.org/en-US/firefox/addon/unloadtab/ > > """ > An essential add-on for power users that have many tabs open. Curb your > resource usage by unloading tabs that you haven't visited for a while. An > unloaded tab is restored back to its original state when you need it again. > """ > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
