[gpu-canvas] Modified testcase from bug 1238309 will completely lockup the whole browser till the drawing is complete
Categories
(Core :: Graphics: Canvas2D, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox123 | --- | wontfix |
firefox124 | --- | wontfix |
firefox125 | --- | wontfix |
People
(Reporter: mayankleoboy1, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
Use latest Nightly on Windows
Set the following prefs
gfx.direct2d.disabled = true
gfx.canvas.accelerated = true
gfx.canvas.remote.worker-threads = 0
Open the attached testcase
AR: Till drawing is complete, the whole browser is completely lockedup. You can increase the loop count to indefinitely freeze the browser.
ER: Not so. Previously, the browser would continue to be responsive while the page rendered.
gpu-canvas Good (1Oct2023): https://share.firefox.dev/3wr8cT3
gpu-canvas Bad (22Feb2024): https://share.firefox.dev/42NjMUq
Regression range:
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
|
||
works really well with d2d-canvas and skia-canvas.
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
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Reporter | ||
Comment 4•1 year ago
|
||
After bug 1863257 and co, the browser remains fully fluid.
Only switching to the demo tab takes some user-noticeable time. But that can be tracked in a different bug.
Calling this fixed by bug 1863257 and co.
Description
•