Looks like a nullptr crash. The stack is incomplete, unfortunately. nr_stun_client_process_response seems to be here: https://searchfox.org/mozilla-central/rev/202a285024f174c2d2bf2152d9cba90a03723eab/media/mtransport/third_party/nICEr/src/stun/stun_client_ctx.c#822 nr_stun_client_fire_finished_cb is defined here: https://searchfox.org/mozilla-central/rev/202a285024f174c2d2bf2152d9cba90a03723eab/media/mtransport/third_party/nICEr/src/stun/stun_client_ctx.c#115 We are calling back to gecko here, but the stack is somehow ending up back in nICEr. This seems like a reentrancy bug.
Bug 1624405 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Looks like a nullptr crash. The stack is incomplete, unfortunately. nr_stun_client_process_response seems to be here: https://searchfox.org/mozilla-central/rev/202a285024f174c2d2bf2152d9cba90a03723eab/media/mtransport/third_party/nICEr/src/stun/stun_client_ctx.c#822 nr_stun_client_fire_finished_cb is defined here: https://searchfox.org/mozilla-central/rev/202a285024f174c2d2bf2152d9cba90a03723eab/media/mtransport/third_party/nICEr/src/stun/stun_client_ctx.c#115 That is how we're ending up in nr_ice_candidate_pair_stun_cb.