Closed Bug 1638400 Opened 4 years ago Closed 4 years ago

Crash in [@ gfx_memory::allocator::allocate_memory_helper<T>] with WebGPU

Categories

(Core :: Graphics: WebGPU, defect, P3)

Unspecified
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr68 --- unaffected
firefox76 --- disabled
firefox77 --- disabled
firefox78 --- disabled

People

(Reporter: mccr8, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-82dc3697-7260-4a61-b889-14d5f0200515.

Top 10 frames of crashing thread:

0 xul.dll RustMozCrash mozglue/static/rust/wrappers.cpp:16
1 xul.dll mozglue_static::panic_hook mozglue/static/rust/lib.rs:89
2 xul.dll core::ops::function::Fn::call<fn ../4fb7144ed159f94491249e86d5bbd033b5d60550/src/libcore/ops/function.rs:232
3 xul.dll std::panicking::rust_panic_with_hook ../4fb7144ed159f94491249e86d5bbd033b5d60550//src/libstd/panicking.rs:474
4 xul.dll std::panicking::begin_panic_handler ../4fb7144ed159f94491249e86d5bbd033b5d60550//src/libstd/panicking.rs:378
5 xul.dll core::panicking::panic_fmt ../4fb7144ed159f94491249e86d5bbd033b5d60550//src/libstd/panicking.rs:332
6 xul.dll gfx_memory::allocator::allocate_memory_helper<gfx_backend_vulkan::Backend> /builds/worker/workspace/obj-build/toolkit/library/build/<::std::macros::panic macros>:5
7 xul.dll gfx_memory::allocator::general::GeneralAllocator<gfx_backend_vulkan::Backend>::alloc_from_entry<gfx_backend_vulkan::Backend> third_party/rust/gfx-memory/src/allocator/general.rs:364
8 xul.dll gfx_memory::allocator::general::GeneralAllocator<gfx_backend_vulkan::Backend>::alloc_block<gfx_backend_vulkan::Backend> third_party/rust/gfx-memory/src/allocator/general.rs:418
9 xul.dll gfx_memory::allocator::general::GeneralAllocator<gfx_backend_vulkan::Backend>::alloc_from_entry<gfx_backend_vulkan::Backend> third_party/rust/gfx-memory/src/allocator/general.rs:364

65 crashes from 3 installations. It looks like an OOM crash while running WebGPU code.

The crash reason is: Unexpected mapping failure: MappingFailed.

Severity: -- → S2
Priority: -- → P3

Lowering to S3 as to not confuse the release management.

Severity: S2 → S3

Closing because no crashes reported for 12 weeks.

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