Open Bug 1838576 Opened 2 years ago Updated 2 years ago

AMD GPU driver crash on a canvas demo with gpu-canvas enabled

Categories

(Core :: Graphics: Canvas2D, defect)

defect

Tracking

()

Tracking Status
firefox-esr102 --- unaffected
firefox-esr115 --- unaffected
firefox114 --- unaffected
firefox115 --- unaffected
firefox116 --- fix-optional

People

(Reporter: mayankleoboy1, Unassigned)

References

(Blocks 1 open bug, Regression, )

Details

(Keywords: regression)

Crash Data

Attachments

(1 file)

Summary: GPU driver crash on a canvas demo with gpu-canvas enabled → AMD GPU driver crash on a canvas demo with gpu-canvas enabled
Crash Signature: [@ atidxx64.dll ] [@ OOM | unknown | atidxx64.dll | gl::Context::onSubjectStateChange ]
Attached file about:support
Flags: needinfo?(lsalzman)

I have the latest AMD GPU drivers from April2023

This superficially seems like some sort of out-of-memory condition, but could be related to just requesting a really big buffer allocation. You look like you have plenty of physmem in those profiles. But when I run it locally, my system thrashes a ton and grinds to a halt because it starts to go to swap, though it runs to completion.

Flags: needinfo?(lsalzman)
Severity: -- → S4

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

I can reproduce this crash on Nightly116.0a1 Windows10. And I confirmed the regressor bug 1837068.
AMD Ryzen 5 5600G w/ Radeon(TM) Graphics, Driver Version 31.0.14057.2005, Driver Date 5-12-2023.

marking as fix-optional given S4 classification and comment 4

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

Can also occur on certain configurations of this page: https://www.fxhash.xyz/generative/slug/midnight-garden (click on the "params" button)

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: