Earlier quoted context omitted.
Firefox has crazy memory leaks. Don't blame it on twitter, regardless how bad their code may be. A tab should be completely and utterly destroyed when refreshed. It doesn't matter how much memory it used, refreshing it or navigating away from that page should (ignoring optimizations, caching, etc. etc. etc.) be like you were never there. Just look at the hundreds of complaints here: http://neosmart.net/blog/2008/fire…
Firefox has crazy memory leaks. Proof? This was the case with Firefox 2 but now it just seems like this is part of their reputation and is not necessarily grounded in fact.
New Twitter Has Become Browser Poison
31–40 of 108 posts
Re: New Twitter Has Become Browser Poison
#32Re: New Twitter Has Become Browser Poison
#33Earlier quoted context omitted.
Firefox has crazy memory leaks. Proof? This was the case with Firefox 2 but now it just seems like this is part of their reputation and is not necessarily grounded in fact.
I routinely leave my browser open for days on end and simply cycle through tabs, closing and opening new ones as needed, with usually ~10 open at a given time. I, too, noticed that firefox was eating up about half a gig of ram even when it wasn't doing anything, didn't have any youtube tabs open, etc. It got to the point where I would have to close firefox and restart after a day or two. Chrome fixed that. Now, I jus…
I'll vote for process-per-tab as the single best feature of Chrome.
Re: New Twitter Has Become Browser Poison
#34otoh, Twitter.app on the Mac is awesome.
Re: New Twitter Has Become Browser Poison
#35Am I the only person who doesn't keep twitter open constantly?
However, this is because I use Google Reader to follow feeds and only use Twitter to keep up to date with friends and acquaintances. That's not the typical use-case.
Re: New Twitter Has Become Browser Poison
#36Agreed, the new twitter is way demanding compared to the older version. Once they stop allowing the old version, I'll probably have twitter loaded much less. On a core 2 duo, even scrolling in new twitter is way below par. Is there a low cpu-usage client? I tried one of the flash based ones, but it brought the fans permanently on on my MacBook... Yeah, that's not going to fly.
I'm using the new Twitter client from the Mac App Store - it's quite good: http://itunes.apple.com/us/app/twitter/id409789998?mt=12
Re: New Twitter Has Become Browser Poison
#37Re: New Twitter Has Become Browser Poison
#38Earlier quoted context omitted.
Firefox has crazy memory leaks. Don't blame it on twitter, regardless how bad their code may be. A tab should be completely and utterly destroyed when refreshed. It doesn't matter how much memory it used, refreshing it or navigating away from that page should (ignoring optimizations, caching, etc. etc. etc.) be like you were never there. Just look at the hundreds of complaints here: http://neosmart.net/blog/2008/fire…
I have been using it in Chrome and new Twitter has been unreasonably slow. A friend who works at Twitter has acknowledged that they know about the issue and are working on it.
Re: New Twitter Has Become Browser Poison
#39Am I the only person who doesn't keep twitter open constantly?
I'm still looking for a reason to even use twitter. I understand _what_ it is, just not any useful purposes for me.
I did think of it as a way to send broadcast "secret" messages, or something along those lines, or when you are posting mundane stuff (went 2 bathroom had shit). Possibly it could be used as a form of a system downtime monitor, similar to what status.4chan.org is.
But use it for me? That's what emails, txts, and phone calls are for.
Re: New Twitter Has Become Browser Poison
#40Earlier quoted context omitted.
I routinely leave my browser open for days on end and simply cycle through tabs, closing and opening new ones as needed, with usually ~10 open at a given time. I, too, noticed that firefox was eating up about half a gig of ram even when it wasn't doing anything, didn't have any youtube tabs open, etc. It got to the point where I would have to close firefox and restart after a day or two. Chrome fixed that. Now, I jus…
Same problem here with Safari. I'll vote for process-per-tab as the single best feature of Chrome.