Open Bug 966602 Opened 10 years ago Updated 2 years ago

if reading a blob fails, DataChannel::Send() will fail to inform the caller via onError

Categories

(Core :: WebRTC: Networking, defect, P4)

Product:
Core
Component:
WebRTC: Networking
Type:
defect

Tracking

()

Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: jesup, Unassigned)

References

Details

Bug 952220 moved blob reading off mainthread, but didn't handle error conditions (former synchronous code would return an error on failure, but now exits out (NS_ENSURE_SUCCESS) not messaging back to the caller that an error happened (and SendBlob() doesn't stall waiting for the off-main-thread read to occur).

I'm don't think we can avoid a MainThread stall if we're going to return a synchronous error; we'd have to report errors via onError.
backlog: --- → webRTC+
Rank: 35
Priority: -- → P3
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.