Bug 1808036 Comment 0 Edit History

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

Crash report: https://crash-stats.mozilla.org/report/index/0e4d8e35-26af-4ea8-8dd2-f84eb0221229

Reason: ```EXCEPTION_BREAKPOINT```

Top 10 frames of crashing thread:
```
0  KERNELBASE.dll  wil::details::DebugBreak  
1  xul.dll    third_party/libwebrtc/rtc_base/checks.cc:52
2  xul.dll  rtc::webrtc_checks_impl::FatalLog  third_party/libwebrtc/rtc_base/checks.cc:170
3  xul.dll  rtc::webrtc_checks_impl::LogStreamer<>::CallCheckOp  third_party/libwebrtc/rtc_base/checks.h:257
3  xul.dll  rtc::webrtc_checks_impl::LogStreamer<rtc::webrtc_checks_impl::Val<6, unsigned long long> >::CallCheckOp const  third_party/libwebrtc/rtc_base/checks.h:306
3  xul.dll  rtc::webrtc_checks_impl::LogStreamer<rtc::webrtc_checks_impl::Val<4, unsigned int>, rtc::webrtc_checks_impl::Val<6, unsigned long long> >::CallCheckOp const  third_party/libwebrtc/rtc_base/checks.h:306
3  xul.dll  rtc::webrtc_checks_impl::FatalLogCall<1>::operator&  third_party/libwebrtc/rtc_base/checks.h:335
3  xul.dll  webrtc::RtpPacketizerH264::PacketizeSingleNalu  third_party/libwebrtc/modules/rtp_rtcp/source/rtp_format_h264.cc:220
4  xul.dll  webrtc::RtpPacketizerH264::GeneratePackets  third_party/libwebrtc/modules/rtp_rtcp/source/rtp_format_h264.cc:84
5  xul.dll  webrtc::RtpPacketizerH264::RtpPacketizerH264  third_party/libwebrtc/modules/rtp_rtcp/source/rtp_format_h264.cc:62
```

Not super common. Line number (rtp_format_h264.cc:220
) is wrong; crash is actually [here](https://searchfox.org/mozilla-central/rev/20fc3d71e6a295984a645403249610ecc7b90c0c/third_party/libwebrtc/modules/rtp_rtcp/source/rtp_format_h264.cc#230). Seems to have the same root cause as bug 1808029.

Crashes start in early December, but that is because of the improved visibility we got in bug 1800132.
Crash report: https://crash-stats.mozilla.org/report/index/0e4d8e35-26af-4ea8-8dd2-f84eb0221229

Reason: ```EXCEPTION_BREAKPOINT```

Top 10 frames of crashing thread:
```
0  KERNELBASE.dll  wil::details::DebugBreak  
1  xul.dll    third_party/libwebrtc/rtc_base/checks.cc:52
2  xul.dll  rtc::webrtc_checks_impl::FatalLog  third_party/libwebrtc/rtc_base/checks.cc:170
3  xul.dll  rtc::webrtc_checks_impl::LogStreamer<>::CallCheckOp  third_party/libwebrtc/rtc_base/checks.h:257
3  xul.dll  rtc::webrtc_checks_impl::LogStreamer<rtc::webrtc_checks_impl::Val<6, unsigned long long> >::CallCheckOp const  third_party/libwebrtc/rtc_base/checks.h:306
3  xul.dll  rtc::webrtc_checks_impl::LogStreamer<rtc::webrtc_checks_impl::Val<4, unsigned int>, rtc::webrtc_checks_impl::Val<6, unsigned long long> >::CallCheckOp const  third_party/libwebrtc/rtc_base/checks.h:306
3  xul.dll  rtc::webrtc_checks_impl::FatalLogCall<1>::operator&  third_party/libwebrtc/rtc_base/checks.h:335
3  xul.dll  webrtc::RtpPacketizerH264::PacketizeSingleNalu  third_party/libwebrtc/modules/rtp_rtcp/source/rtp_format_h264.cc:220
4  xul.dll  webrtc::RtpPacketizerH264::GeneratePackets  third_party/libwebrtc/modules/rtp_rtcp/source/rtp_format_h264.cc:84
5  xul.dll  webrtc::RtpPacketizerH264::RtpPacketizerH264  third_party/libwebrtc/modules/rtp_rtcp/source/rtp_format_h264.cc:62
```

Not super common. Line number (rtp_format_h264.cc:220) is wrong; crash is actually [here](https://searchfox.org/mozilla-central/rev/20fc3d71e6a295984a645403249610ecc7b90c0c/third_party/libwebrtc/modules/rtp_rtcp/source/rtp_format_h264.cc#230). Seems to have the same root cause as bug 1808029.

Crashes start in early December, but that is because of the improved visibility we got in bug 1800132.

Back to Bug 1808036 Comment 0