Closed Bug 1399965 Opened 7 years ago Closed 7 years ago

activity stream periodically pegs a content process


(Firefox :: New Tab Page, defect)

Not set



Firefox 57
Tracking Status
firefox57 --- fixed


(Reporter: aswan, Assigned: k88hudson)




(1 file)

I've attached a profile, the relevant part is content process #3 beginning about 7s into the profile.
Also, the Activity Stream version is: 2017.09.12.1376-781e5de5
Hm, I wonder if the extra data URIs for highlights is what's causing this. We could take a look at profiling that specifically, maybe turn on the dev version of react locally if that doesn't turn anything up
Flags: needinfo?(khudson)
After some investigation it looks like the Sections component's render function is being called 9 times on every load (since it is receiving 9 SECTION_UPDATE_CARD events), that's something we might want to look more into
Hopefully fixed by to be uplifted via bug 1399970.
Assignee: nobody → khudson
Blocks: 1399970
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 57
The current Nightly 57.0a1 (2017-09-15) (Built from should have a fix. Can you see if that improves things / avoids the jank?
Flags: needinfo?(aswan)
Blocks: 1394533
(In reply to Ed Lee :Mardak from comment #6)
> The current Nightly 57.0a1 (2017-09-15) (Built from
> 893fe1549e1e7342a66514b65960f08d40810a34) should have a fix. Can you see if
> that improves things / avoids the jank?

I just re-enabled activity stream, I'll let you know if I see the same thing again.
I'm curious though, the lag this created for me made the browser nearly unusable, but it doesn't seem like this was reported by anybody else?  Could there be something specific about my profile that made this especially noticeable for me?
Flags: needinfo?(aswan)
Component: Activity Streams: Newtab → New Tab Page
You need to log in before you can comment on or make changes to this bug.