Closed Bug 1153006 Opened 9 years ago Closed 9 years ago

[marker] Add timeline markers to trace setTimeout/setInterval callback execution

Categories

(DevTools :: Performance Tools (Profiler/Timeline), defect)

Product:
DevTools
Component:
Performance Tools (Profiler/Timeline)
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1050500

People

(Reporter: fitzgen, Unassigned)

References

Details

Similar to bug 1152881 but for setTimeout/setInterval. We shouldn't just enter JS out of nowhere, we should see what operation caused us to enter JS. Usually this is a DOM event, but setTimeout/setInterval callbacks aren't DOM events and so we don't get this info.
Summary: Add timeline markers to trace setTimeout/setInterval callback execution → [marker] Add timeline markers to trace setTimeout/setInterval callback execution
I see both setTimeout and setInterval causes for JS markers -- is this already done, or is there another component of this?
Flags: needinfo?(ttromey)
I think this was done by the first part of bug 1050500.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(ttromey)
Resolution: --- → DUPLICATE
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.