Re: [webrtc-pc] Race condition in enqueue an operation

In fact the very last test shows why no-one should rely on the queue. `addTransceiver` here is effectively called *before* the enqueued part of `createOffer`, even before the enqueued part of `setLocalDescription`! We found no easy way to keep it out of createOffer, short of tracking parallel state around, nor is it intuitive that it should be kept out. So we didn't, instead changing `createOffer`/`createAnswer` to pick up on changes.

The queue is a mess, and I'm not sure why we're digging this up again.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1218#issuecomment-310716617 using your GitHub account

Received on Friday, 23 June 2017 16:48:28 UTC