Closed Bug 1014351 Opened 12 years ago Closed 10 years ago

Massive instability with Twitter Deck not present in Chrome

Categories

(Core :: General, defect)

29 Branch
x86_64
Windows 8.1
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
platform-rel --- -

People

(Reporter: akayanni, Unassigned)

Details

(Whiteboard: [platform-rel-Twitter])

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 (Beta/Release) Build ID: 20140506152807 Steps to reproduce: Run https://tweetdeck.twitter.com/ Set up columns with busy tags like #auspol Actual results: Crashes FF in < 15 minutes Memory leak to the limit of a 32bit app Expected results: Stability Initial testing shows Chrome is releasing memory and giving at least somewhat most stable performance. Still testing this comparison.
Component: Untriaged → General
Product: Firefox → Core
Done further testing. I fairs better with plugins disabled. That said I allowed the Twitter Deck to run in Chrome for ~13 hours and it is using 450mb and stable. On Firefox I'm still testing it's hit about the same level 450mb of memory user after ~1 hour. (I have looked at other pages in both browsers during testing). It's better without plugins but it is still climbing. It's exceeding Chrome now after ~3 hours. Really I had a much more stable browser when I was using Minefield 64bit on Windows.
Whiteboard: [platform-rel-Twitter]
platform-rel: --- → ?
Yani, is this still a problem with current builds of Firefox?
Flags: needinfo?(akayani)
You can mark this fixed
Great, thank you!
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
platform-rel: ? → -
Flags: needinfo?(akayani)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.