Crash: MOZ_DIAGNOSTIC_ASSERT(wl_container->surface) (Should have surface if we're ready to draw)
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: dannyfritz, Unassigned)
Details
Crash Data
Maybe Fission related. (DOMFissionEnabled=1)
Crash report: https://crash-stats.mozilla.org/report/index/67bc96ad-aae1-4458-8fdb-965580220313
MOZ_CRASH Reason: MOZ_DIAGNOSTIC_ASSERT(wl_container->surface) (Should have surface if we're ready to draw)
Top 10 frames of crashing thread:
0 libxul.so libxul.so@0x0000000003569103
1 libxul.so libxul.so@0x000000000356913a
2 libxul.so libxul.so@0x0000000000c642d5
3 libxul.so libxul.so@0x0000000000c4dfa7
4 libxul.so libxul.so@0x0000000000c4d318
5 libxul.so libxul.so@0x0000000000c4d50e
6 libxul.so libxul.so@0x0000000000c65d51
7 libxul.so libxul.so@0x0000000000c5988c
8 libxul.so libxul.so@0x0000000000c5ddd7
9 libxul.so libxul.so@0x00000000012bd4d7
Reporter | ||
Comment 1•3 years ago
|
||
I am on Ubuntu 21.10 using Firefox Beta via Snap. https://snapcraft.io/firefox
Comment 2•3 years ago
|
||
The severity field is not set for this bug.
:bhood, could you have a look please?
For more information, please visit auto_nag documentation.
Updated•3 years ago
|
Comment 3•3 years ago
|
||
The bug has a crash signature, thus the bug will be considered confirmed.
Comment 4•3 years ago
|
||
Glenn, could you please evaluate the severity on this when you get a chance? Let's be sure it's not more severe than S3.
Reporter | ||
Comment 5•3 years ago
|
||
I am also available to answer questions or investigate things. I am reasonably technical (as a web developer mostly). This crash I believe has only happened once for me though.
Comment 6•3 years ago
|
||
I can't actually find this assert anywhere in the current m-c codebase? Perhaps stransky knows if this assert has been removed?
Updated•3 years ago
|
Description
•