Closed Bug 1756384 Opened 3 years ago Closed 3 years ago

[Accelerated Canvas] Crash on https://lab.hakim.se/hypnos/

Categories

(Core :: Graphics: Canvas2D, defect)

defect

Tracking

()

RESOLVED DUPLICATE of bug 1755458
Tracking Status
firefox-esr91 --- unaffected
firefox97 --- unaffected
firefox98 --- unaffected
firefox99 --- disabled

People

(Reporter: mayankleoboy1, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression)

Crash Data

Attachments

(1 file)

enable accelerated canvas
go to : https://lab.hakim.se/hypnos/

The demos takes 15s to "load", then glitches, and then finally crashes.

2022-02-21T08:35:35.192000: DEBUG : Found commit message:
Bug 1754130 - Support presenting a WebGLFramebuffer to its own swap chain without opaque FB. r=aosmond,jgilbert

Most of the support for presenting a WebGLFramebuffer to a swap chain existed as part of the
mechanism for opaque WebXR framebuffer support. However, such "opaque" framebuffer are meant
to be opaque in the sense that their attachments can't be inspected or changed, which does
not provide the requisite level of control for efficiently implementing Canvas2D snapshots.

To this end, the existing Present mechanism is slightly extended to allow presenting to the
swap chain already present in WebGLFramebuffer without the existence of a corresponding
MozFramebuffer.

This also fixes a bug in that AsWebgl() was no longer being utilized in CanvasRenderer, such
that a new mechanism that routed GetFrontBuffer() was needed to fix the code rot.

There are also some efforts to remove a couple redundant copies I noticed in profiles along
the way.

Differential Revision: https://phabricator.services.mozilla.com/D138119

2022-02-21T08:35:35.192000: DEBUG : Did not find a branch, checking all integration branches
2022-02-21T08:35:35.210000: INFO : The bisection is done.
2022-02-21T08:35:35.211000: INFO : Stopped

Blocks: gpu-canvas
Crash Signature: [@ mozilla::gfx::DrawTargetWebgl::~DrawTargetWebgl ]
Has Regression Range: --- → yes
Has STR: --- → yes
Regressed by: 1754130

should bug 1748167 be closed/resolved fixed by bug 1754130 ?

Set release status flags based on info from the regressing bug 1754130

Attached file about:support (deleted) —
Severity: -- → S3
Flags: needinfo?(lsalzman)
Flags: needinfo?(lsalzman)

This crash should also be fixed by bug 1755458 as I changed how the SharedContext is allocated/freed.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: