Warning spam from !Theme::ThemeSupportsWidget(aFrame->PresContext(), aFrame, aAppearance)
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | fixed |
firefox114 | --- | wontfix |
firefox115 | --- | wontfix |
firefox116 | --- | fixed |
People
(Reporter: mccr8, Assigned: emilio)
References
(Blocks 1 open bug, Regression)
Details
(Keywords: regression)
Attachments
(1 file)
48 bytes,
text/x-phabricator-request
|
RyanVM
:
approval-mozilla-esr115+
|
Details | Review |
In a recent Linux debug try run I did, the second most frequent source of NS_WARNING spam was:
WARNING: '!Theme::ThemeSupportsWidget(aFrame->PresContext(), aFrame, aAppearance)', file widget/gtk/nsNativeThemeGTK.cpp:1085
There were almost 390,000 instances of this.
Looking at one log, there are two individual tests where the warning was spammed around 200 times, and not occurring in other ones:
browser/base/content/test/plugins/browser_private_browsing_eme_persistent_state.js
browser/components/uitour/test/browser_UITour_private_browsing.js
Could this warning be silenced or somehow changed so we only get it once instead of over and over again?
Comment 1•1 years ago
|
||
Set release status flags based on info from the regressing bug 1817396
Reporter | ||
Comment 2•1 years ago
|
||
This only affects log spam in debug builds, so there's no need to backport anything.
Assignee | ||
Comment 3•1 years ago
|
||
Yeah the fact that it only happens in PB mode was a good hint.
Assignee | ||
Comment 4•1 years ago
|
||
Usually, this warning points at a problem (we're rendering a native
widget in light mode in a page where we should render it in dark mode).
However there are cases where we do this legitimately, for example for
the -moz-window-titlebar appearance. We render the light titlebar behind
the tabs to be able to render shadows appropriately.
We could probably only warn in some cases but honestly I don't think
that is particularly appealing, so let's remove it.
Updated•1 years ago
|
Comment 6•1 years ago
|
||
bugherder |
Comment 7•1 year ago
|
||
Can we take this on ESR115 to cut down on the logspam there for the next year+? :-)
Assignee | ||
Comment 8•1 year ago
|
||
Comment on attachment 9339106 [details]
Bug 1838468 - Remove noisy warning. r=mccr8
ESR Uplift Approval Request
- If this is not a sec:{high,crit} bug, please state case for ESR consideration: comment 7
- User impact if declined: none
- Fix Landed on Version:
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): debug-only
Comment 9•1 year ago
|
||
Comment on attachment 9339106 [details]
Bug 1838468 - Remove noisy warning. r=mccr8
Approved for 115.0esr.
Comment 10•1 year ago
|
||
bugherder uplift |
Description
•