Closed Bug 1799069 Opened 2 years ago Closed 2 years ago

Demo is slower with GPU-Canvas (as compared to non-gpu-canvas)

Categories

(Core :: Graphics: Canvas2D, defect, P2)

defect

Tracking

()

RESOLVED FIXED
108 Branch
Tracking Status
firefox108 --- fixed

People

(Reporter: mayankleoboy1, Assigned: lsalzman)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Blocks: gpu-canvas
Attached file about:support (deleted) —
Severity: -- → S3
Priority: -- → P2

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.

Assignee: nobody → lsalzman
Status: NEW → ASSIGNED
Pushed by lsalzman@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8baf918fe8e8 Preserve buffer provider on same size canvas resets. r=aosmond
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch

This is fixed in the latest Nightly: https://share.firefox.dev/3Ei7kS1

Flags: qe-verify+
Flags: qe-verify+
Regressions: 1800807
Regressions: 1800826
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: