Status

()

Firefox
Developer Tools: Performance Tools (Profiler/Timeline)
P2
normal
3 years ago
a year ago

People

(Reporter: paul, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox40 affected)

Details

(Whiteboard: [polish-backlog][difficulty=medium])

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
We should highlight sync reflows in the waterfall, and point to the culprit JS function.
Assignee: nobody → jsantell
Status: NEW → ASSIGNED
Depends on: 1165504
Any ideas of what this should look like? Chrome has a [warning] icon in the parent (at a lower opacity), and a warning icon next to the culprit marker. Currently we have a stack for any reflow marker that is sync, which should indiciate it's invalidation reason, but maybe we can also get more info on invalidations on platform.
(Reporter)

Comment 2

3 years ago
(In reply to Jordan Santell [:jsantell] [@jsantell] from comment #1)
> Any ideas of what this should look like? Chrome has a [warning] icon in the
> parent (at a lower opacity), and a warning icon next to the culprit marker.
> Currently we have a stack for any reflow marker that is sync, which should
> indiciate it's invalidation reason, but maybe we can also get more info on
> invalidations on platform.

The stack points to the JS function, which is already very good. Could we have the JS line too?
Created attachment 8608129 [details]
Screen Shot 2015-05-20 at 7.53.50 AM.png

We currently already have the function name and line number in the stack on any marker that has a stack.
Priority: -- → P2
Whiteboard: [polish-backlog][difficulty=medium]
Triaging. Filter on ADRENOCORTICOTROPIC (yes).
OS: Mac OS X → All
Hardware: x86 → All
Unassigning myself from bugs I won't be able to get to due to other commitments.
Assignee: jsantell → nobody
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.