Crash in [@ mozilla::dom::ToJSValue | mozilla::dom::PeerConnectionImpl_Binding::getStats_promiseWrapper]
Categories
(Core :: WebRTC: Signaling, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox99 | --- | unaffected |
firefox100 | --- | unaffected |
firefox101 | --- | verified |
People
(Reporter: calixte, Assigned: bwc)
References
(Regression)
Details
(Keywords: crash, regression)
Crash Data
Attachments
(1 file)
Maybe Fission related. (DOMFissionEnabled=1)
Crash report: https://crash-stats.mozilla.org/report/index/5fe807e2-918e-4fc4-adb2-368a30220406
Reason: EXCEPTION_ACCESS_VIOLATION_READ
Top 4 frames of crashing thread:
0 xul.dll mozilla::dom::ToJSValue dom/bindings/ToJSValue.cpp:64
1 xul.dll mozilla::dom::PeerConnectionImpl_Binding::getStats_promiseWrapper dom/bindings/PeerConnectionImplBinding.cpp:398
2 xul.dll mozilla::dom::binding_detail::GenericMethod<mozilla::dom::binding_detail::NormalThisPolicy, mozilla::dom::binding_detail::ConvertExceptionsToPromises> dom/bindings/BindingUtils.cpp:3270
3 None @0x000000cc9b8f18c9
There are 10 crashes (from 9 installations) in nightly 101 starting with buildid 20220406093646. In looking at the pushlog for this build, it could be related to bug 1624989.
Reporter | ||
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
This has been happening since before 20220406093646, although the frequency has increased substantially:
Assignee | ||
Comment 2•3 years ago
|
||
I'm thinking that we're running into a situation where PeerConnectionImpl::GetStats returns a nullptr.
![]() |
||
Comment 3•3 years ago
•
|
||
Here's an old test case from another bug that reproduced this for me on Windows -
https://nils-ohlmeier.github.io/webrtc-landing/pc_test_loop_h264.html
https://crash-stats.mozilla.org/report/index/d79b2d14-7173-4ce3-97dd-7748a0220407#tab-details
Assignee | ||
Updated•3 years ago
|
![]() |
||
Comment 5•3 years ago
|
||
FYI, Just got this again on whereby when in a meeting the other person reloaded their session and my tab crashed as a result. This was on a different system running Windows 11.
https://crash-stats.mozilla.org/report/index/5b5d8b2d-d4b8-4e54-ae2e-ddd7e0220407#tab-bugzilla
Assignee | ||
Comment 6•3 years ago
|
||
Not having any luck reproducing on OS X. Going to try windows next.
Assignee | ||
Comment 7•3 years ago
|
||
No luck reproducing on windows either, although I do not have access to a Windows 11 system currently. crash-stats has crashes from both 10 and 11, so it does not look specific to 11, so maybe that does not matter.
Here's a try run, which fixes one possibility for the crash, and that converts a couple of other possibilities into easier to diagnose crashes:
https://treeherder.mozilla.org/jobs?repo=try&revision=e674bf7b721539e6fb2d9c87c89205fdeac5ec72
Assignee | ||
Comment 8•3 years ago
|
||
Assignee | ||
Comment 9•3 years ago
|
||
Returning nullptr still release crashes, but is harder to tell what happened.
Assignee | ||
Comment 10•3 years ago
|
||
Try looks fine.
Comment 11•3 years ago
|
||
STR, in case you need them:
- Install the DevTools Media Panel extension.
- Visit https://www.tiktok.com/.
Updated•3 years ago
|
Assignee | ||
Updated•3 years ago
|
Comment 12•3 years ago
|
||
Comment 13•3 years ago
|
||
I think bug 1764216 may be a duplicate. It has a test case and will have a Pernosco session shortly.
Comment 14•3 years ago
|
||
bugherder |
Assignee | ||
Comment 15•3 years ago
|
||
From the pernoso session mentioned in comment 13:
Looks like the nullptr was being returned due to the PC being closed. The patches landed here should solve that particular issue. I'll check back on crash-stats in a few days to see if the bug has been resolved.
Comment 17•3 years ago
|
||
Byron, fwiw I can repro this by attempting to join a call on Zoom Web. 100% repro on my M1 Max here.
Assignee | ||
Comment 18•3 years ago
|
||
Does it happen with the patch from this bug? If so, what's the signature like?
Comment 19•3 years ago
|
||
(In reply to Byron Campen [:bwc] from comment #18)
Does it happen with the patch from this bug? If so, what's the signature like?
I think so it was recent enough but I'm not sure: https://crash-stats.mozilla.org/report/index/0142bd76-0160-4fc8-a3e9-11f1b0220413
Comment 20•3 years ago
|
||
I can't repro now with a nightly I just updated though, but I don't know if I was lucky before, reproducing a couple times in a row.
Assignee | ||
Comment 21•3 years ago
•
|
||
So that's the build from the 11th, which was before this patch. If you have any time to pull down the latest nightly, and try, that would be useful. Otherwise, we can keep an eye on crash-stats and see if this signature, or any signatures from PeerConnectionImpl::GetStats, continue to show up.
Edit: Mid-air collision, it seems like it is fixed for you now.
Assignee | ||
Comment 22•3 years ago
|
||
ni self to check back on crash-stats, maybe on Friday.
Assignee | ||
Comment 23•3 years ago
|
||
Not seeing any crashes that match on crash-stats, nor do I see any crashes in PeerConnectionImpl::GetStats. I think this is fixed.
Updated•3 years ago
|
Updated•3 years ago
|
I managed to reproduce the crash on a 2022-04-06 Nightly build on Win10, Ubuntu 20.04 and macOS 11. Verified as fixed on Nightly 102.0a1(20220516215740) and Firefox 101.0b7(20220515185854) on Win10, Ubuntu 20.04, macOS 11.
Description
•