Closed
Bug 1290241
Opened 8 years ago
Closed 1 year ago
Replace GLXtest with safe in-process initialization
Categories
(Core :: Graphics, defect, P3)
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox50 | --- | affected |
People
(Reporter: acomminos, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: gfx-noted)
At the moment, blacklisting using GLXtest incurs a significant runtime cost, as we will require its output by the end of gfxPlatform initialization for the purpose of determining whether or not to use accelerated layers (currently, we return early as HW_COMPOSITION is disabled by default on Linux). Some initial research has shown that 32 out of 24,224 Linux crashes (0.1%) have successfully blacklisted GLX due to glxtest crashing. This small percentage of users is much less significant than the cost of waiting for glxtest to complete at startup. https://crash-stats.mozilla.com/search/?app_notes=~glxtest&app_notes=~received%20signal&product=Firefox&_sort=-date&_facets=signature&_columns=app_notes&_columns=date#crash-reports
Reporter | ||
Updated•8 years ago
|
Summary: Replace GLXtest with safe per-process initialization → Replace GLXtest with safe in-process initialization
Comment 1•2 years ago
|
||
The bug assignee is inactive on Bugzilla, so the assignee is being reset.
Assignee: andrew → nobody
Status: ASSIGNED → NEW
Updated•2 years ago
|
Severity: normal → S3
Comment 2•1 year ago
|
||
We don't want to block start with the test, parallel run is ok.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•