Open Bug 1956468 Opened 5 months ago Updated 2 months ago

[WebGPU] [@ <name omitted> | vk_queue_submit_create ]

Categories

(Core :: Graphics: WebGPU, defect)

Firefox 138
defect

Tracking

()

People

(Reporter: Surfer56, Unassigned, NeedInfo)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Attached file Fedora42.txt

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:138.0) Gecko/20100101 Firefox/138.0

Steps to reproduce:

https://martinlaxenaire.github.io/gpu-curtains/examples/compute-blur/

Actual results:

Firefox crash.

Expected results:

Should not crashing.

The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebGPU' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Graphics: WebGPU
Product: Firefox → Core
Severity: -- → S3
Crash Signature: [@ <name omitted> | vk_queue_submit_create ]

crashes seem to have started in build 20250321040811. :jnicol can you see if this was caused by bug 1955214?

Flags: needinfo?(jnicol)

Seems unlikely. That doesn't change any interaction with the adapter, it just edits a CPU side buffer after we do a readback

Flags: needinfo?(jnicol)

On a local build my terminal gets spammed with this message:

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: create_semaphore() failed: ERROR_INVALID_EXTERNAL_HANDLE (t=6.51071) [GFX1-]: create_semaphore() failed: ERROR_INVALID_EXTERNAL_HANDLE

which could potentially be related given the crash stack. I don't get a crash, but it definitely looks as if there's no synchronisation (it's jumpy and there's glitches)

ty for looking into it.., so maybe bug 1920763 which landed on 03-04 but maybe didn't crash until a later build.

Flags: needinfo?(sotaro.ikeda.g)

That one seems a lot more likely!

The bug has a crash signature, thus the bug will be considered confirmed.

Status: UNCONFIRMED → NEW
Ever confirmed: true

The bug is linked to a topcrash signature, which matches the following criterion:

  • Top 10 desktop browser crashes on nightly

:jimb, could you consider increasing the severity of this top-crash bug?

For more information, please visit BugBot documentation.

Flags: needinfo?(jimb)
Keywords: topcrash

(In reply to Dianna Smith [:diannaS] from comment #6)

ty for looking into it.., so maybe bug 1920763 which landed on 03-04 but maybe didn't crash until a later build.

Hi Oleg, can you check if the following address the problem?

  • change pref dom.webgpu.allow-present-without-readback to false in about:config
  • Restart Firefox
Flags: needinfo?(sotaro.ikeda.g) → needinfo?(Surfer56)
See Also: → 1952670

I could reproduce the crash with mesa 25.02.0 with Intel GPU on Ubuntu 24.10. And the crash did not happen when pref dom.webgpu.allow-present-without-readback = false.

Though, I did not see the crash with the following when pref dom.webgpu.allow-present-without-readback = true.
https://webgpu.github.io/webgpu-samples/?sample=rotatingCube

Hello.

Yes, I can confirm. With dom.webgpu.allow-present-without-readback = false crashes has gone.
It also fixes another bug 1954913.

Crash Signature: [@ <name omitted> | vk_queue_submit_create ]
Flags: needinfo?(Surfer56)

Based on the topcrash criteria, the crash signatures linked to this bug are not in the topcrash signatures anymore.

For more information, please visit BugBot documentation.

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

Attachment

General

Creator:
Created:
Updated:
Size: