Jan-Ivar, is there some subtlety that could explain what is happening here? JS is calling getStats inside pc.onicecandidate, then adapter.js calls the "real" getStats, then JS closes the PC in pc.onicegatheringstatechange, then on the c++ side we're resolving both the MozPromise and then the dom::Promise (and making it all the way to enqueuing runnables in CycleCollectedJSContext::DispatchToMicroTask), but the getStats call that adapter.js made never resolves?
Bug 1891503 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Jan-Ivar, is there some subtlety that could explain what is happening here? JS is calling getStats inside pc.onicecandidate, then adapter.js calls the "real" getStats, then JS closes the PC in pc.onicegatheringstatechange, then on the c++ side we're resolving both the MozPromise and then the dom::Promise (and making it all the way to enqueuing runnables in CycleCollectedJSContext::DispatchToMicroTask), but the getStats call that adapter.js made never resolves (runs its .then function)?