[GPU-canvas] Testcase from bug 1828940 doesnt animate with gpu-canvas
Categories
(Core :: Graphics: Canvas2D, defect, P2)
Tracking
()
People
(Reporter: mayankleoboy1, Assigned: lsalzman)
References
(Regression)
Details
(Keywords: regression)
Attachments
(3 files)
Use latest nightly on windows. This shpuld have gpu-canvas enabled
Open the testcase from bug 1828940 (https://bugzilla.mozilla.org/attachment.cgi?id=9329296)
AR: The green thing stops after a second
ER: The whole red box should have been covered by the green thing
Additional steps: Each time you reload the testcase, the green thing moves a little further as if it remembers its previous position.
Bisection:
Bug 1829026 - Handle KERN_ABORTED from semaphore_wait. r=aosmond
Differential Revision: https://phabricator.services.mozilla.com/D195952
Reporter | ||
Comment 1•1 year ago
|
||
Reporter | ||
Comment 2•1 year ago
|
||
Comment 3•1 year ago
|
||
Set release status flags based on info from the regressing bug 1829026
:lsalzman, since you are the author of the regressor, bug 1829026, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Comment 4•1 year ago
|
||
Mayank, does disabling Accelerated Canvas2D (gfx.canvas.accelerated
) in about:config
fix the issue?
Assignee | ||
Comment 6•1 year ago
|
||
When we fallback from accelerated canvases to non-accelerated canvases, there may
be a stale PathRecording left around that DrawTargetSkia can't use. In this case,
we need to create a PathSkia with the PathRecording's contents.
Updated•1 year ago
|
Reporter | ||
Comment 10•1 year ago
|
||
This is fixed for me on the latest Nightly
Comment 11•1 year ago
|
||
:lzlazman is this needed in Fx130, do you want to add a beta uplift request?
Assignee | ||
Comment 12•1 year ago
•
|
||
I would rather let this ride the trains.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 13•11 months ago
|
||
Reproducible on a 2024-07-31 Nightly build on Windows 10 using the testcase from Comment 2.
Verified as fixed on Firefox 131.0b5 and Firefox Nightly 132.0a1 on Windows 10, Ubuntu 22, macOS 14.
However, it’s worth mentioning that on Windows 10 on both Fx 131.0b5 and Nightly 132.0a1 the animation takes longer to fully render compared to macOS/Ubuntu.
Is this expected or should I file a follow-up bug for Windows-only??
Thank you.
Assignee | ||
Comment 14•11 months ago
|
||
Windows and Linux/macOS use different acceleration systems, so it's expected.
Comment 15•11 months ago
|
||
Thank you for the confirmation!
Removing the qa-verify+ flag and updating the bug.
Description
•