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/lib.rs:89
2 XUL core::ops::function::Fn::call src/libcore/ops/function.rs:72
3 XUL std::panicking::rust_panic_with_hook src/libstd/panicking.rs:474
4 XUL rust_begin_unwind src/libstd/panicking.rs:378
5 XUL core::panicking::panic_fmt src/libcore/panicking.rs:85
6 XUL core::option::expect_failed src/libcore/option.rs:1203
7 XUL webrender::glyph_cache::GlyphCache::get_glyph_key_cache_for_font gfx/wr/webrender/src/glyph_cache.rs:174
8 XUL webrender::batch::BatchBuilder::add_prim_to_batch gfx/wr/webrender/src/resource_cache.rs:1014
9 XUL webrender::batch::BatchBuilder::add_pic_to_batch gfx/wr/webrender/src/batch.rs:775

Since 20200204214324

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

Lee, do you have any suggestions?

No idea offhand. Hard to diagnose without a testcase.

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

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)