Closed Bug 1548581 Opened 6 years ago Closed 5 years ago

Crash in [@ OOM | large | mozalloc_abort | mozalloc_handle_oom | gkrust_shared::oom_hook::hook | std::alloc::rust_oom | webrender::scene_builder::SceneBuilder::run]

Categories

(Core :: Graphics: WebRender, defect, P2)

Unspecified
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox67 --- wontfix
firefox68 --- wontfix
firefox69 --- wontfix
firefox70 --- fix-optional

People

(Reporter: marcia, Unassigned)

References

(Blocks 2 open bugs)

Details

(Keywords: crash, regression)

Crash Data

This bug is for crash report bp-4b5be714-5f9d-4704-a5e7-18c1e0190502.

Seen during nightly crash triage: https://bit.ly/2GVOvX0. 8 crashes/8 installs in the last 7 days. Crashes started in 68 using 20190413095252, but there are also crashes in nightly 67 if you go back 3-6 months.

Top 10 frames of crashing thread:

0 mozglue.dll mozalloc_abort memory/mozalloc/mozalloc_abort.cpp:33
1 mozglue.dll mozalloc_handle_oom memory/mozalloc/mozalloc_oom.cpp:51
2 xul.dll void gkrust_shared::oom_hook::hook toolkit/library/rust/shared/lib.rs:262
3 xul.dll void std::alloc::rust_oom src/libstd/alloc.rs:210
4 xul.dll void alloc::alloc::handle_alloc_error src/liballoc/alloc.rs:227
5 xul.dll static void webrender::scene_builder::SceneBuilder::run gfx/wr/webrender/src/scene_builder.rs:326
6 xul.dll static void std::sys_common::backtrace::__rust_begin_short_backtrace<closure,  src/libstd/sys_common/backtrace.rs:135
7 xul.dll static void alloc::boxed::{{impl}}::call_box< src/liballoc/boxed.rs:749
8 xul.dll static void std::sys::windows::thread::{{impl}}::new::thread_start src/libstd/sys/windows/thread.rs:47
9 kernel32.dll kernel32.dll@0x5bb3 

Blocks: wr-stability

Not particularl

Blocks: wr-oom
Priority: -- → P2

No crashes showing up in 69, but there is one in 70 recently. Based on small volume, I think maybe we should close this one out.

Closing because no crashes reported for 12 weeks.

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