Open
Bug 1928466
Opened 2 days ago
Updated 19 hours ago
MOZ_USE_PERFORMANCE_MARKER_FILE no longer works
Categories
(Core :: Performance, defect, P2)
Core
Performance
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox-esr128 | --- | unaffected |
| firefox132 | --- | unaffected |
| firefox133 | --- | wontfix |
| firefox134 | --- | affected |
People
(Reporter: denispal, Assigned: denispal)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
The profiler is not running when we use MOZ_USE_PERFORMANCE_MARKER_FILE, but we fall into a path where there is a MOZ_DIAGNOSTIC_ASSERT that crashes the content process whenever we enable MOZ_USE_PERFORMANCE_MARKER_FILE.
|
Assignee | |
Updated•2 days ago
|
Assignee: nobody → dpalmeiro
|
||
Comment 1•2 days ago
|
||
Set release status flags based on info from the regressing bug 1922494
status-firefox132:
--- → unaffected
status-firefox133:
--- → affected
status-firefox134:
--- → affected
status-firefox-esr128:
--- → unaffected
|
|
Assignee | |
Comment 2•2 days ago
|
||
|
||
Updated•2 days ago
|
Attachment #9434607 -
Attachment description: Bug 1928466: Check if MOZ_USE_PERFORMANCE_MARKER_FILE is enabled during NowUnclamped diagnostic assert. r=mstange! → Bug 1928466: Check if markerFile is defined during NowUnclamped diagnostic assert. r=mstange!
|
|
Assignee | |
Updated•19 hours ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•