Closed
Bug 1583244
Opened 5 years ago
Closed 5 years ago
Provide unfuzzed timings for UserTiming markers
Categories
(Core :: Gecko Profiler, task, P2)
Core
Gecko Profiler
Tracking
()
RESOLVED
FIXED
mozilla71
Tracking | Status | |
---|---|---|
firefox71 | --- | fixed |
People
(Reporter: gregtatum, Assigned: jlast)
Details
Attachments
(1 file)
Right now the timing for user timing markers is fuzzed. We should record the unfuzzed timings.
This is creating issues with using the user timing markers and how they are laid out in visual charts: https://perfht.ml/2kzBIRT
Assignee | ||
Comment 1•5 years ago
•
|
||
Some notes from slack
https://searchfox.org/mozilla-central/source/dom/performance/Performance.cpp#329-332
startTimeStamp, endTimeStamp are the fuzzed values
It looks like here is where the fuzzing happens for startTime https://searchfox.org/mozilla-central/source/dom/performance/Performance.cpp#280
And likewise for endTime: https://searchfox.org/mozilla-central/source/dom/performance/Performance.cpp#294
Docs for our memory tooling: https://deploy-preview-2261--perf-html.netlify.com/docs/#/./memory-allocations
Assignee | ||
Comment 2•5 years ago
|
||
Pushed by jlaster@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/b15c0747d702 Provide unfuzzed timings for UserTiming markers. r=gregtatum
Comment 4•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
Updated•5 years ago
|
Assignee: nobody → jlaster
You need to log in
before you can comment on or make changes to this bug.
Description
•