Bug 1791273 Comment 5 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(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](https://crash-stats.mozilla.org/report/index/8b891e39-cc9a-455a-9f05-951330221103), it leads to this bug, but yeah, it looks related to bug1761233 (and it no longer reproduces in Nightly, only in release):

```
(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
```
Revision 1 by
on 
(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](https://crash-stats.mozilla.org/report/index/8b891e39-cc9a-455a-9f05-951330221103), 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
```

Back to Bug 1791273 Comment 5