&gt; I had to disable e10s because whenever I switched tabs the page would sometimes be replaced indefinitely by a white screen with a big loading indicator.<p>I&#x27;m pretty sure I know what loading indicator you&#x27;re talking about, though I don&#x27;t have a screenshot handy.<p>Basically, this is because one of the other tabs is hogging the rendering process. Since the Firefox UI[0] is controlled by a separate process under e10s, it&#x27;s still responsive while the other process is rendering webpages. So, you&#x27;re able to switch tabs before there&#x27;s something there to switch to.<p>Without e10s, under this situation, the Firefox UI will be unresponsive while the tab is rendering web content (the browser will appear to lock up). That doesn&#x27;t necessarily mean the tab will always be fully rendered by the time you&#x27;re able to switch, but the loading indicator was added to e10s specifically because multiprocess mode makes this situation more likely to occur than under single-process mode.<p>If you want to see what I&#x27;m talking about, try visiting an Amazon product page both in an e10s window and in a non-e10s window[1].<p>[0] Confusingly referred to as the chrome, a name that predates the browser with the same name<p>[1] Unless they&#x27;ve fixed it recently, there&#x27;s a longstanding, known &quot;bug&quot; that&#x27;s caused by Amazon &quot;prefetching&quot; the content of all links on an Amazon product page. This Javascript is included <i>only</i> when the page is loaded in Firefox, and it&#x27;s rather redundant, because the content is still re-fetched when the link is clicked. Unfortunately, Amazon hasn&#x27;t fixed this, and I don&#x27;t think there&#x27;s much Mozilla can do about it.