Closed
Bug 1873244
Opened 2 years ago
Closed 2 years ago
MOZ_USE_PERFORMANCE_MARKER_FILE doesn't work any more
Categories
(Core :: DOM: Performance APIs, defect)
Core
DOM: Performance APIs
Tracking
()
RESOLVED
FIXED
123 Branch
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox121 | --- | unaffected |
| firefox122 | --- | unaffected |
| firefox123 | --- | fixed |
People
(Reporter: mstange, Assigned: mstange)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
I missed this in my review of D196332 (part 2 in bug 1869835): This patch accidentally removed the only call to Performance::MaybeEmitExternalProfilerMarker, so the capability from bug 1835513 broke.
This doesn't matter for end users but it breaks some local sp3 profiling workflows.
|
||
Comment 1•2 years ago
|
||
Set release status flags based on info from the regressing bug 1869835
:bas.schouten, since you are the author of the regressor, bug 1869835, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
status-firefox121:
--- → unaffected
status-firefox122:
--- → unaffected
status-firefox-esr115:
--- → unaffected
Flags: needinfo?(bas)
|
Assignee | |
Updated•2 years ago
|
Assignee: nobody → mstange.moz
Flags: needinfo?(bas)
|
|
Assignee | |
Comment 2•2 years ago
|
||
Pushed by mstange@themasta.com:
https://hg.mozilla.org/integration/autoland/rev/60a61e3e54f9
Reintroduce a call that was accidentally removed in bug 1869835. r=jrmuizel
|
||
Comment 4•2 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 123 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•