This is mostly because Chrome starts a new process for each tab. However, Firefox is also heading in this direction.
Re:Why are browsers so slow?
by traviswatkins on Wednesday December 21, 2016 @09:52AM
(#13229529)
Firefox is going for at most N+1 cores worth of processes, as I understand it (one per core for websites and one extra for compositing and the UI) and is doing to use cooperative threading (Quantum DOM) to improve responsiveness within those processes without the overhead of running a process per website.
Alright, good to know. I had the idea that they were going in the same direction as Chrome.
I use Chrome for websites that use huge amounts of JavaScript links, which are pain to use with noscript. Chrome does not like a lot of tabs open and chews up memory and performance if forced to run large numbers of tabs.