If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

JS Tree View/Flamegraph sometimes doesn't render any frames

RESOLVED WORKSFORME

Status

()

Firefox
Developer Tools: Performance Tools (Profiler/Timeline)
P1
normal
RESOLVED WORKSFORME
3 years ago
2 years ago

People

(Reporter: jsantell, Assigned: jsantell)

Tracking

37 Branch
x86
Mac OS X
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Can't consistently recreate this, but once it fails, it seems to fail until restart. It's like no profiler data exists.
(Assignee)

Updated

3 years ago
Blocks: 1075567
Blocks: 1145697
No longer blocks: 1075567
What happens is the profiler start time is X, and when we receive the samples from the back end, all the samples have times < X, so no samples are rendered. this is very bad. Maybe this only happens when you have the profiler running for awhile. All my sample profiles are only about 2-3 seconds long.

earliest time, latest time, profiler start time
3244051 - 3270404 - 3390269

3440575.5 - 3466624 - 3552771

3924127.5 - 3950841.5 - 4048497
It seems as if some point, the profiler restarted, and gProfilerStartTime was not reset. Causing our profiler start time from startProfiler() (so Date.now() - gProfilerStartTime) to no longer match the internal timing used by profiler to match its samples.
To clarify, with no toolboxes open or anything, and opening a new toolbox to start a new recording, the profiler is considered "active"
(Assignee)

Updated

3 years ago
Depends on: 1145824
This is more than a papercut - this makes all of the profiler literally unusable
Blocks: 1075567
No longer blocks: 1145697
Seeing this in old profiler in Fx38 as well. I think it mostly happens with long running instances.
Haven't seen this in awhile, but we need to keep an eye on this and ensure this doens't happenf or long running instances.
Assignee: nobody → jsantell
Priority: -- → P1
Status: NEW → ASSIGNED
Haven't seen this at all, luckily.. CLOSING
Status: ASSIGNED → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.