Maybe Fission related. (DOMFissionEnabled=1)

Crash report: https://crash-stats.mozilla.org/report/index/c4b0cb6c-61b8-4e96-9d45-17fe10220221

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  ../02072b482a8b5357f7fb5e5637444ae30e423c40/library/core/src/ops/function.rs:227
3 xul.dll std::panicking::rust_panic_with_hook ../02072b482a8b5357f7fb5e5637444ae30e423c40//library/std/src/panicking.rs:610
4 xul.dll std::panicking::begin_panic_handler::closure$0 ../02072b482a8b5357f7fb5e5637444ae30e423c40//library/std/src/panicking.rs:502
5 xul.dll std::sys_common::backtrace::__rust_end_short_backtrace<std::panicking::begin_panic_handler::closure$0, never$> ../02072b482a8b5357f7fb5e5637444ae30e423c40//library/std/src/sys_common/backtrace.rs:139
6 xul.dll std::panicking::begin_panic_handler ../02072b482a8b5357f7fb5e5637444ae30e423c40//library/std/src/panicking.rs:498
7 xul.dll core::panicking::panic_fmt ../02072b482a8b5357f7fb5e5637444ae30e423c40//library/core/src/panicking.rs:107
8 xul.dll core::panicking::panic_display<str> ../02072b482a8b5357f7fb5e5637444ae30e423c40//library/core/src/panicking.rs:63
9 xul.dll core::option::expect_failed ../02072b482a8b5357f7fb5e5637444ae30e423c40//library/core/src/option.rs:1637

There are 126 crashes (from 20 installations) in nightly 99 with buildid 20220220215821. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1749380.

[1] https://hg.mozilla.org/mozilla-central/rev?node=9fa6f71111d0

Fixed by backout of bug 1749380.

I was able to reproduce this locally - there is a path that was able to create a zero-sized render task, which asserts during the texture allocation code. Working on a fix for this today.

Was fixed by backout but should be handled correctly when the updated patch re-lands.