startup Crash in [@ webrender::api_resources::ApiResources::update] assertion failed: self.fonts.templates.has_font(&shared_font_key)
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox105 | --- | unaffected |
firefox106 | --- | affected |
firefox107 | --- | affected |
People
(Reporter: aryx, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
661 crashes from 13+ installations of Firefox 106.0a1 on multiple operating systems. Crash reports for build ID 20220913213020 and 20220915+ but not 20220914.
Crash report: https://crash-stats.mozilla.org/report/index/56cdbc8c-c8f6-430d-a6f2-9a4b70220917
Reason: EXCEPTION_BREAKPOINT
Top 10 frames of crashing thread:
0 xul.dll RustMozCrash mozglue/static/rust/wrappers.cpp:17
1 xul.dll mozglue_static::panic_hook mozglue/static/rust/lib.rs:91
2 xul.dll core::ops::function::Fn::call<void ../4b91a6ea7258a947e59c6522cd5898e7c0a6a88f/library/core/src/ops/function.rs:248
3 xul.dll std::panicking::rust_panic_with_hook library/std/src/panicking.rs:702
4 xul.dll std::panicking::begin_panic_handler::closure$0 library/std/src/panicking.rs:586
5 xul.dll std::sys_common::backtrace::__rust_end_short_backtrace<std::panicking::begin_panic_handler::closure_env$0, never$> library/std/src/sys_common/backtrace.rs:138
6 xul.dll std::panicking::begin_panic_handler library/std/src/panicking.rs:584
7 xul.dll core::panicking::panic_fmt library/core/src/panicking.rs:142
8 xul.dll core::panicking::panic library/core/src/panicking.rs:48
9 xul.dll webrender::render_api::RenderApi::send_transaction gfx/wr/webrender/src/render_api.rs:1266
Comment 1•2 years ago
|
||
Note that the first frame in the signature is inlined, and the raw crash reason is the same as many crashes in bug 1761233 so this might just be a new signature for that bug.
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Comment 5•2 years ago
•
|
||
(In reply to Gabriele Svelto [:gsvelto] from comment #1)
Note that the first frame in the signature is inlined, and the raw crash reason is the same as many crashes in bug 1761233 so this might just be a new signature for that bug.
We've received a report in https://github.com/webcompat/web-bugs/issues/110910 about a crash when visiting https://maruyama.neocities.org/home.html and after submitting crash report, it leads to this bug, but yeah, it looks related to bug1761233 (and it no longer reproduces in Nightly v108, only in release v106):
(88.24% in signature vs 00.07% overall) moz_crash_reason = assertion failed: self.fonts.templates.has_font(&shared_font_key)
(35.29% in signature vs 01.90% overall) GFX_ERROR "Failed as lost WebRenderBridgeChild." = true [54.55% vs 01.96% if adapter_vendor_id = 0x8086]
(47.06% in signature vs 00.03% overall) GFX_ERROR "Failed sanitizing font " = true [40.00% vs 00.02% if platform = Windows NT]
(27.45% in signature vs 01.13% overall) "D3D11 Layers-" in app_notes = true [34.29% vs 01.43% if platform_pretty_version = Windows 10]
(29.41% in signature vs 02.07% overall) "D3D11 Layers?" in app_notes = true
(23.53% in signature vs 01.54% overall) GFX_ERROR "[D3D11] " = true
(21.57% in signature vs 01.16% overall) GFX_ERROR "[D3D11] failed to get compositor device." = true
(21.57% in signature vs 01.33% overall) GFX_ERROR "Failed to initialize CompositorD3D11 for SWGL: " = true
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Updated•2 years ago
|
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Comment hidden (obsolete) |
Comment 15•1 year ago
|
||
Sorry for removing the keyword earlier but there is a recent change in the ranking, so the bug is again linked to a topcrash signature, which matches the following criterion:
- Top 5 GPU process crashes on release
For more information, please visit BugBot documentation.
Comment 16•1 year ago
|
||
Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.
For more information, please visit BugBot documentation.
Comment 17•1 year ago
|
||
Sorry for removing the keyword earlier but there is a recent change in the ranking, so the bug is again linked to a topcrash signature, which matches the following criterion:
- Top 10 desktop browser crashes on nightly
For more information, please visit BugBot documentation.
Comment 18•11 months ago
|
||
Based on the topcrash criteria, the crash signature linked to this bug is not a topcrash signature anymore.
For more information, please visit BugBot documentation.
![]() |
||
Updated•10 months ago
|
Comment 19•6 months ago
|
||
Somehow this has been spiking on nightly, with a handful of installations sending a lot of crashes each.
Updated•3 months ago
|
Description
•