5 ms·
I've been keeping twitter open in its own Firefox browser on one screen (of three). It routinely refreshes itself and there is some kind of memory leak whereas
by epi0Bauqu 16y ago
I've been keeping twitter open in its own Firefox browser on one screen (of three). It routinely refreshes itself and there is some kind of memory leak whereas after a day it is consuming about half a gig of memory, forcing me to kill and restart.
- ComputerGuru 16y agoFirefox 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/firefox-3-is-still-a-memory-hog/ http://neosmart.net/blog/2008/firefox-3-is-still-a-memory-ho...
- seldo 16y agoI 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.
- deleted 16y ago[deleted]
- epi0Bauqu 16y agoThat may be the case, but I've left other sites open all day and they don't accumulate 500MB of memory.
- naner 16y agoFirefox 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.
- redthrowaway 16y agoI 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 just use firefox with the modify headers extension to watch domain-specific video, and have no plans to go back.
- riobard 16y agoSame problem here with Safari. I'll vote for process-per-tab as the single best feature of Chrome.
- redthrowaway 16y agoMe too. The overhead is slightly higher, but having crashes and memory leaks confined to a single tab is awesome.
- mkramlich 16y agoI left Firefox for Safari because Safari was prettier, faster and used less memory. Lately, I'm close to leaving Safari for Chrome because it's faster, uses less memory and crashes less (in fact, it's never crashed so far, vs 100's of times total probably with Safari.) Unfortunately, Chrome is a little uglier, and has certain less user conveniences. So it's not an easy jump to make.
- redthrowaway 16y agoYou think Chrome is ugly and inconvenient? I think it's the best looking browser out there, and the omnibox is fantastic. The only thing I don't like about Chrome on OSX is some flash players don't play nice with it.
- 16y ago
- 1337p337 16y agoFirefox's memory leaks are mostly due to JS. On the other hand, if you read the article, you'll notice that the problem is cross-browser.
- Qz 16y agoAre you using FF4 beta? I've had two pages of newtwitter open in app tabs for months now and never ever have problems with it.
- didip 16y agoEndless pagination/Infinite scrolling is pretty much the definition of memory leak, no?