Open Bug 2000509 Opened 1 month ago Updated 1 month ago

Crash in [@ loader_preload_icds]

Categories

(Core :: Graphics: WebGPU, defect)

defect

Tracking

()

People

(Reporter: gsvelto, Unassigned)

Details

(Keywords: crash)

Crash Data

Attachments

(1 file)

Crash report: https://crash-stats.mozilla.org/report/index/b1762ade-86e4-499c-b11a-2b2780251116

Reason:

SIGSEGV / SEGV_MAPERR

Top 7 frames:

0  ?  @0xfffffffffffffea0
1  libvulkan.so.1  loader_preload_icds  /usr/src/debug/vulkan-icd-loader/Vulkan-Loader/loader/loader.c:2342
1  libvulkan.so.1  loader_preload_icds  /usr/src/debug/vulkan-icd-loader/Vulkan-Loader/loader/loader.c:2333
1  libvulkan.so.1  terminator_EnumerateInstanceExtensionProperties  /usr/src/debug/vulkan-icd-loader/Vulkan-Loader/loader/loader.c:7567
2  libvulkan.so.1  vkEnumerateInstanceExtensionProperties  /usr/src/debug/vulkan-icd-loader/Vulkan-Loader/loader/trampoline.c:240
3  libvulkan.so.1  loader_delete_layer_list_and_properties  /usr/src/debug/vulkan-icd-loader/Vulkan-Loader/loader/loader.c:4437
3  libvulkan.so.1  loader_scan_for_implicit_layers  /usr/src/debug/vulkan-icd-loader/Vulkan-Loader/loader/loader.c:4441

This is most likely caused by a CPU bug in Raptor Lake CPUs, as all the crash reports we currently have on file are from one. Filing so that people won't waste time on it, we can revisit if different CPUs show up under this signature.

It's possible that this is a user with a raptor lake cpu who is hitting the same non-raptor lake cpu bug many times from looking at the install times: there are only 4 different install times. And they all have the same platform version.

Not sure if this should be classified as S3 or S4. I'll do S3 for now. Let's revise if this continues to show up in a meaningful volume.

Severity: -- → S3
Attached file crashtest.html

(In reply to Gabriele Svelto [:gsvelto] from comment #0)

This is most likely caused by a CPU bug in Raptor Lake CPUs, as all the crash reports we currently have on file are from one.

Bug 2000509 is not specific to Raptor Lake. For example, I can also reproduce it from Coffee Lake: https://crash-stats.mozilla.org/report/index/9f8cca1a-59e9-4ae0-8320-b374c0251125 . I suspect bug 2000509 may generally affect clients that are running an entire Wayland compositor under optirun when dom.webgpu.enabled is enabled.

Steps to reproduce:

  1. Open Sway under Bumblebee: optirun sway
  2. Open Firefox 145.0.1 and enable dom.webgpu.enabled
  3. Open the testcase

Some sites that reproduce bug 2000509:

Thank you, adjusting the bug accordingly.

No longer blocks: cpu-raptor-lake-bugs
Summary: Crash in [@ loader_preload_icds] on Raptor Lake CPUs → Crash in [@ loader_preload_icds]
Component: Graphics → Graphics: WebGPU
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: