4 ms·

Going fullscreen in youtube is always instant in Chrome. In Firefox however, it is very slow (like 5s) when you have 1000 tabs open. Even opening a select box

by atesti 6y ago

Going fullscreen in youtube is always instant in Chrome. In Firefox however, it is very slow (like 5s) when you have 1000 tabs open. Even opening a select box is slow, if you have several 1000 tabs. Funny enough, opening a new window (and keeping all the other tabs open) makes it fast again, if you are in that window. Seems like Firefox has some slow code paths, like notifying every tab about going fullscreen?

krzyk 6y ago
> Going fullscreen in youtube is always instant in Chrome. In Firefox however, it is very slow (like 5s) when you have 1000 tabs open. Is it possible to have 1000 tabs open in Chrome? When I had like 50, it ate my whole 8GB last time I tried it. In Firefox I frequently have 1000 tabs with no issues. (almost none, recently I noticed that there is some memory leak and the ram slowly disappears). This is the reason why I went back to Firefox after using Chrome for like 2 weeks, it is great for 1-10 tabs.
- atesti 6y ago
  I don't know if anybody REALLY can have more than 1000 tabs open as in completely loaded into RAM. When my computer is slow I pray that I don't have any unsent edit windows or unfinished youtube/twitch videos and just kill all the render processes. Chrome kills them regularly on it's own, which means they simply crash with out of memory. For me, Chrome generally handles killed renderers better, e.g. it shows a popup about crashed extensions and just reloads them. Firefox requires me to quickly disable and enable adblock and I lose the build in screenshot extension permanently (except disabling and renabling it with about:config). But for chrome a renderer often just freezes and only a day later there is a popup about it which offers to kill it. Firefox seems to handle the tabs better overall, but at some point session resume fails with javascript errors in the shell. Chrome seems to handle session restore a bit better.

by atesti 6y ago

krzyk 6y ago

> Going fullscreen in youtube is always instant in Chrome. In Firefox however, it is very slow (like 5s) when you have 1000 tabs open. Is it possible to have 1000 tabs open in Chrome? When I had like 50, it ate my whole 8GB last time I tried it. In Firefox I frequently have 1000 tabs with no issues. (almost none, recently I noticed that there is some memory leak and the ram slowly disappears). This is the reason why I went back to Firefox after using Chrome for like 2 weeks, it is great for 1-10 tabs.

atesti 6y ago
I don't know if anybody REALLY can have more than 1000 tabs open as in completely loaded into RAM. When my computer is slow I pray that I don't have any unsent edit windows or unfinished youtube/twitch videos and just kill all the render processes. Chrome kills them regularly on it's own, which means they simply crash with out of memory. For me, Chrome generally handles killed renderers better, e.g. it shows a popup about crashed extensions and just reloads them. Firefox requires me to quickly disable and enable adblock and I lose the build in screenshot extension permanently (except disabling and renabling it with about:config). But for chrome a renderer often just freezes and only a day later there is a popup about it which offers to kill it. Firefox seems to handle the tabs better overall, but at some point session resume fails with javascript errors in the shell. Chrome seems to handle session restore a bit better.