Demo is slower with GPU-Canvas (as compared to non-gpu-canvas)
Categories
(Core :: Graphics: Canvas2D, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox108 | --- | fixed |
People
(Reporter: mayankleoboy1, Assigned: lsalzman)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
Enable gpu-canvas
go to : https://js1k.com/2016-elemental/demo/2497
non-gpu-canvas: https://share.firefox.dev/3FGSB43
GPU-canvas: https://share.firefox.dev/3FI1OJu
Reporter | ||
Updated•2 years ago
|
Reporter | ||
Comment 1•2 years ago
|
||
Updated•2 years ago
|
Assignee | ||
Comment 2•2 years ago
|
||
Some canvas users attempt to set .width=.width to have the canvas reset as a
side-effect. When this happens, we throw out the buffer provider on reset. However,
this makes it impossible to do any sort of profiling for accelerated canvas inside
the buffer provider since its state is continually reset every frame in these
sorts of use-cases.
To work around this, we make our best attempt to keep the buffer provider around
so long as the size remains the same. The only caveat is that we still need to
keep the side-effect of clearing the buffer when this happens so that the
behavior is similar regardless.
Updated•2 years ago
|
Comment 4•2 years ago
|
||
bugherder |
Reporter | ||
Comment 5•2 years ago
|
||
This is fixed in the latest Nightly: https://share.firefox.dev/3Ei7kS1
Updated•2 years ago
|
Updated•2 years ago
|
Description
•