Closed
Bug 1359886
Opened 8 years ago
Closed 8 years ago
Regression April 12th in accelerated Flash async plugin drawing use
Categories
(Core Graveyard :: Plug-ins, defect)
Core Graveyard
Plug-ins
Tracking
(firefox55 affected)
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox55 | --- | affected |
People
(Reporter: jimm, Assigned: jimm)
References
()
Details
https://wiki.mozilla.org/Plugins/Async_Drawing#Telemetry_Links
We have a regression in accelerated rendering use within the async drawing populations of sites. Originally we were running around 70%/30% accelerated/un-accelerated. Around April 12th this reversed to 25%/70%. Thi s is significant enough that we'll have to hold rollout until it's addressed.
The regression showed up in both nightly and aurora. Gfx says nothing major landed in both repos on that date. Plugin code didn't have any landings with uplifts either.
In general this looks like a regression in Flash's April 11th point release.
![]() |
Assignee | |
Updated•8 years ago
|
Assignee: nobody → jmathies
![]() |
Assignee | |
Comment 1•8 years ago
|
||
Drawing modes:
NPDrawingModelAsyncBitmapSurface - un-accelerated
NPDrawingModelAsyncWindowsDXGISurface - accelerated
Updated•8 years ago
|
Blocks: win64-rollout
Summary: Regression April 12th in accelerated async plugin drawing use → Regression April 12th in accelerated Flash async plugin drawing use
Updated•8 years ago
|
status-firefox55:
--- → affected
status-firefox57:
affected → ---
![]() |
Assignee | |
Updated•8 years ago
|
Blocks: flash-async-drawing
![]() |
Assignee | |
Comment 2•8 years ago
|
||
Fixed May 8th, likely through a Flash update.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•