Profiler "render reason" strings are broken
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox122 | --- | wontfix |
firefox123 | --- | wontfix |
firefox124 | --- | fixed |
People
(Reporter: mstange, Assigned: glandium)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Example profile: https://share.firefox.dev/47Apb1U
The render reasons in the profiler markers no longer have readable strings. Now it says things like "Render reason RenderReasons(32768)" instead of "Render reason VSYNC".
if add_markers {
let event_str = format!("Render reason {:?}", reason_bit);
add_event_marker(&event_str);
}
It looks like the Debug implementation on bitfields has changed.
Comment 1•1 year ago
|
||
Almost filed a duplicate. mozregression says: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=d0a48f87ca55781281108541c014ad59d6334268&tochange=b3d4dd6d5b436ace9de5430fd3ebdd2869014ce8 -> bug 1852209
Comment 2•1 year ago
|
||
Set release status flags based on info from the regressing bug 1852209
:glandium, since you are the author of the regressor, bug 1852209, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Assignee | ||
Comment 3•1 year ago
|
||
Ah, this is happening for all the types with a Debug derive where the "custom derive" method is used (https://docs.rs/bitflags/latest/bitflags/#custom-derives)
Updated•1 year ago
|
Comment 4•1 year ago
|
||
Mike, could you please assign Priority/Severity ratings to this report when you get a chance?
Assignee | ||
Comment 5•1 year ago
|
||
bitflags 2 has a shortcoming with using custom derives: you can't use
custom derives (for e.g. MallocSizeOf) at the same time as bitflags's for
the derives it supports.
See https://github.com/bitflags/bitflags/issues/395
Assignee | ||
Updated•1 year ago
|
Comment 7•1 year ago
|
||
bugherder |
Comment 8•1 year ago
|
||
The patch landed in nightly and beta is affected.
:glandium, is this bug important enough to require an uplift?
- If yes, please nominate the patch for beta approval.
- If no, please set
status-firefox123
towontfix
.
For more information, please visit BugBot documentation.
Assignee | ||
Comment 9•1 year ago
|
||
Marcus, what do you think?
Reporter | ||
Comment 10•1 year ago
|
||
I'm ok with this being broken on Release a bit more. I mostly look at profiles from Nightly.
Description
•