What’s Next for Multi-Process Firefox
I feel like my case is an anomaly compared to others on this thread, but this has been a consistent experience for me.<p>I hoard tabs and easily reach 40 tabs in a single session. It is typical to have 60-100 tabs open at any point in time. I find that firefox handles this much better than chrome does. Any time the tab count exceeds 15 or so in Chrome, my whole system slows down and freezes. I am forced to close some tabs and restart chrome to get some sanity. Often system reboot is the only option.<p>In firefox the same system slowdown happens, but rarer than chrome, usually I have nearly 200 tabs open and running for a long time. In such cases, I just have to restart firefox. Firefox presents me with the restore window which is a much saner way to select only the tabs I want. Even in that case, when I restore, it does not load all the tabs, only the active ones, so it does not impact system performance.<p>The only time firefox becomes slow even on startup is when I have restore windows several levels deep (yes, there is such a thing :) ) and I believe I am wholly responsible for that and not firefox.<p>So it really surprises me when people say Chrome is more performant.<p>Also, maybe because of familiarity, I find firefox Developer Tools more usable than Chrome&#x27;s.  But what do I know? I am a server side person dabbling in UI for my personal projects, not a web designer :)<p>I dread Firefox following the footsteps of Chrome!<p>Oh, and not to mention the scores of chrome processes that pollute the process list!<p>when I run the `ps` command or the `top` command, it is difficult to locate the process that I am actually looking for.  Also, it is much, much harder to estimate how much memory and processor time Chrome is really consuming when there are so many processes of Chrome running. May be I am doing it wrong. Some one please enlighten me.