3 ms·
I'm still unsure why certain websites result in browser processes using up substantial resources in terms of CPU time or system memory. I typically will search
by u801e 6y ago
I'm still unsure why certain websites result in browser processes using up substantial resources in terms of CPU time or system memory. I typically will search for "Web Content" processes in top and kill the ones that are taking more than a certain percent of resident memory or using more than 20% CPU time just to keep the computer usable.
That's not a problem I recall encountering in the days of Firefox 2.0.
- speedgoose 6y agoFirefox 2 had other issues. You don't remember that a website could freeze the whole browser and that it didn't have any thread or process separation between tabs?
- u801e 6y agoI do remember the days where there was no thread or process separation, but, at least for the set of websites I would frequent back in those days, it rarely happened. And, even then, it didn't render the computer unusable due to constant swapping due to insufficient memory.
- speedgoose 6y agoI think you should really consider to upgrade your hardware if a website can make your computer unusable. I agree it shouldn't be the case but that's how it is.
- u801e 6y agoIt really only happens with certain websites, like Facebook. If I leave a browser tab open overnight, then it can get to that point where I see a browser tab taking 50% of the resident memory, I guess it's too much to ask companies not to implement websites that leak memory.