Closed
Bug 1614013
Opened 5 years ago
Closed 5 years ago
One marker and one profiler label got moved to a different scope accidentally
Categories
(Core :: Gecko Profiler, defect, P2)
Core
Gecko Profiler
Tracking
()
RESOLVED
FIXED
mozilla75
Tracking | Status | |
---|---|---|
firefox75 | --- | fixed |
People
(Reporter: mstange, Assigned: mozbugz)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
The second patch from bug 1578329 contained two mistakes: AUTO_PROFILER_*
RAII objects were moved into a more limited scope than before. For AUTO_PROFILER_TEXT_MARKER_*
, this means that the marker duration will be too short, and for AUTO_PROFILER_LABEL_*
, this means that the label won't show up on the stack where it's needed.
https://hg.mozilla.org/integration/autoland/rev/4b97efacdf38#l3.27
https://hg.mozilla.org/integration/autoland/rev/4b97efacdf38#l10.18
Flags: needinfo?(gsquelart)
Assignee | ||
Comment 1•5 years ago
|
||
Thank you Markus. On it.
Assignee: nobody → gsquelart
Flags: needinfo?(gsquelart)
Priority: -- → P2
Assignee | ||
Comment 2•5 years ago
|
||
In bug 1578329 I introduced two scoping mistakes:
- A marker was made to have a shorter duration.
- A label was scoped too short and so would most likely be missed during
sampling.
This patch reverts to the original wider scope.
Pushed by gsquelart@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ead246c1f024
Fix RAII Profiler object scopes - r=gregtatum
Reporter | ||
Comment 4•5 years ago
|
||
Thank you for fixing this so quickly!
Comment 5•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox75:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
Updated•5 years ago
|
Has Regression Range: --- → yes
Keywords: regression
You need to log in
before you can comment on or make changes to this bug.
Description
•