News for hackers. Stuff that matters.
Re:Chrome will aggressively throttle background tabs by cookiecaper on Tuesday January 24, 2017 @11:47AM (#13472975)
You're doing something wrong. I use Chrome on Windows as my main now and I usually have more than 100 tabs open. I just switched a few months ago from Firefox on Linux, also usually with 100 tabs or more open. Both are very stable. Chrome is worse with handling tons of tabs, but I certainly don't have daily crashes.

People who have extremely unstable/inconsistent experiences with these platforms usually have a rogue extension or some other problem lurking beneath the surface.

Also consider occasionally VACUUMing your browser's DBs, and on Firefox, taking advantage of the profile reset option.

Re:Chrome will aggressively throttle background tabs by overcast on Tuesday January 24, 2017 @11:57AM (#13473086)
For every person that has my symptoms, there is someone to counter it. I'm not going to get into an argument about how I'm using my browser incorrectly. Every computer / browser combo I've ever used exhibits the same thing, and I'm pretty religious with keeping things trim and clean.
Re:Chrome will aggressively throttle background tabs by mulrian on Tuesday January 24, 2017 @12:17PM (#13473306)
Using a lot of extensions?
Re:Chrome will aggressively throttle background tabs by rhizome on Tuesday January 24, 2017 @12:43PM (#13473579)
Could be the sites themselves.
Re:Chrome will aggressively throttle background tabs by mikeash on Tuesday January 24, 2017 @12:42PM (#13473563)
Why is it that whenever somebody has a problem that less than 100% of people experience, the response is always "you must be doing it wrong" rather than "I must be lucky"?
Re:Chrome will aggressively throttle background tabs by cookiecaper on Tuesday January 24, 2017 @03:45PM (#13475294)
Because the quantity isn't just less than 100%, it's a small minority. Chrome and Firefox are among the most widely-used pieces of software in the world. I'm not saying they don't have weird bugs, but they don't crash daily for most users.

While the OP may not be doing anything "wrong", he is almost definitely doing something unusual, or has deeper issues like malware or malfunctioning hardware.

If the ratio were inverted and most users were experiencing daily crashes from normal use, I would consider myself lucky. That's just not been my experience with Chrome/Firefox.

Re:Chrome will aggressively throttle background tabs by overcast on Tuesday January 24, 2017 @04:27PM (#13475676)
I would suspect a majority of the world does not keep dozens of tabs open, on an computer that never shuts down. You have to remember which forum you're on here. Any software issue, usually rears its head relatively quickly from one of our machines around here.
Re:Chrome will aggressively throttle background tabs by cookiecaper on Wednesday January 25, 2017 @12:53AM (#13478982)
That's the use case I'm most familiar with. I've done this on many different machines for many years and not had anything like a crash once a day. I stand by my belief that your negative experiences are likely caused by a rare collision of variables and not representative of the typical experience among similar use cases. As I said in my post, it's totally legitimate that such an atypical experience may be caused by real bugs, but it's still an unfair generalization to say that Chrome and Firefox crash daily.
Re:Chrome will aggressively throttle background tabs by mikeash on Tuesday January 24, 2017 @04:19PM (#13475589)
Bugs which only affect a small minority of users don't exist, nor do unusual but perfectly legitimate usage patterns?
Re:Chrome will aggressively throttle background tabs by cookiecaper on Wednesday January 25, 2017 @12:53AM (#13478986)
You probably want to re-read my post, as I said neither of these things.
Re:Chrome will aggressively throttle background tabs by mikeash on Wednesday January 25, 2017 @10:06AM (#13481924)
You're right. I was confused because in your other comment you just said they were doing something wrong, and I didn't realize you'd reversed course on that.