Closed Bug 1295142 Opened 8 years ago Closed 8 years ago

www.talkingpointsmemo.com unusable compared to chrome *(with profile)

Categories

(Core :: Layout, defect)

50 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: mcmanus, Unassigned)

Details

I'm going to need some help routing this to the right people (nathan can you help?).

I was on PTO and indulging in some politics - and most pages on talkingpointsmemo.com were border line unusable in firefox and, while slower than normal, quite usable in chrome. That's true of nightly and release, e10s and single process, and linux and windows. Even with a clean profile.

here's a specific page, but basically any article linked from the main page will do:

http://talkingpointsmemo.com/livewire/donald-trump-ideological-test-immigrantion

and here's a profile from nightly on linux I just made, but as I said its obviously a problem on multiple platforms.

https://cleopatra.io/#report=9a1b9b425791b6ce959a391d0850f193aa637056

The page itself is notably slower, but the real showstopper is when you close the tab. I tend to open a tab per article and close them when done reading. Closing the tab totally janks the browser for 1+seconds.

hopefully there is some low hanging fruit here.
Flags: needinfo?(nfroyd)
So it looks like you have one big time-wasting stack that ends in __poll; that's just our event loop, waiting for something to happen.

The other stack appears to be something in Ant Video Downloader; it looks like it's hooking into tab switching and then doing sync IPC?

Can you provide a profile with a clean, no-addons profile that shows the problems?
Flags: needinfo?(nfroyd)
that video downloader addon was definitely responsible for the tab switching problem. I did test it out in a clean profile, but was probably too chill in choosing the tabs to swap to for a comparison.

sorry for the noise - still not an awesome experience on first load, but much more competitive.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.