Open Bug 1654297 Opened 1 year ago Updated 1 day ago

Crash in [@ core::option::expect_failed | webrender::glyph_cache::GlyphCache::get_glyph_key_cache_for_font]


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




Tracking Status
firefox80 --- affected


(Reporter: achronop, Unassigned)


(Blocks 1 open bug)


(Keywords: crash, steps-wanted, testcase-wanted)

Crash Data

This bug is for crash report bp-aba168c8-c122-4b52-9bce-146d90200721.

Top 10 frames of crashing thread:

0 XUL RustMozCrash mozglue/static/rust/wrappers.cpp:17
1 XUL mozglue_static::panic_hook mozglue/static/rust/
2 XUL core::ops::function::Fn::call src/libcore/ops/
3 XUL std::panicking::rust_panic_with_hook src/libstd/
4 XUL rust_begin_unwind src/libstd/
5 XUL core::panicking::panic_fmt src/libcore/
6 XUL core::option::expect_failed src/libcore/
7 XUL webrender::glyph_cache::GlyphCache::get_glyph_key_cache_for_font gfx/wr/webrender/src/
8 XUL webrender::batch::BatchBuilder::add_prim_to_batch gfx/wr/webrender/src/
9 XUL webrender::batch::BatchBuilder::add_pic_to_batch gfx/wr/webrender/src/

Since 20200204214324

MOZ_CRASH Reason (Sanitized) BUG: Unable to find glyph key cache!

Blocks: wr-stability
OS: Unspecified → All

Lee, do you have any suggestions?

Flags: needinfo?(lsalzman)

No idea offhand. Hard to diagnose without a testcase.

Flags: needinfo?(lsalzman)

Jamie, the spike in the reports looks somewhat suspiciously timed to your text run bounds changes maybe?

Flags: needinfo?(jnicol)
Blocks: wr-80
Severity: -- → S3
Priority: -- → P3

I don't think that could have caused this: it didn't change anything outside of the callback which is called by fetch_gylphs() (after the point of the crash)

Flags: needinfo?(jnicol)
No longer blocks: wr-80
No longer blocks: wr-81
No longer blocks: gfx-82
See Also: → 1729829
You need to log in before you can comment on or make changes to this bug.