806287 - Crash trying to access second stream in video-only call

Status: RESOLVED WORKSFORME

(Core :: WebRTC: Signaling, defect, P1)

Description

[Randell Jesup [:jesup] (needinfo me)]

Attachment: callstack

I modified pc_test.html to offer only video, and got a crash trying to access a non-existent stream in the mRemoteSourceStreams array.  This is 100% repeatable.  I'll attach the callstack and testcase.

Comment 1

[Randell Jesup [:jesup] (needinfo me)]

Attachment: testcase

Comment 2

[Suhas]

I was trying to re-create this issue .. But when i load the modified pc_test.html with latest mc .. on clicking the start button, i get the following error

###!!! ERROR: Potential deadlock detected:
=== Cyclical dependency starts at
--- Mutex : mozilla::MediaManager (currently acquired)
 calling context
  [stack trace unavailable]

=== Cycle completed at
--- Mutex : mozilla::MediaManager (currently acquired)
 calling context
  [stack trace unavailable]

###!!! Deadlock may happen NOW!

###!!! ASSERTION: Potential deadlock detected:
Cyclical dependency starts at
Mutex : mozilla::MediaManager (currently acquired)
Cycle completed at
Mutex : mozilla::MediaManager (currently acquired)

###!!! Deadlock may happen NOW!

: 'Error', file /Users/ccg-cteo/HTML5/firefox-sources/mc/latest/obj-ff-dbg/xpcom/build/BlockingResourceBase.cpp, line 128

Is this issue still valid with the call-stack or is this a new issue

Comment 3

[Randell Jesup [:jesup] (needinfo me)]

I still get the exact same callstack, no deadlock, on linux

Comment 4

[Jason Smith [:jsmith]]

I'm guessing this is crashtest worthy, unless this bug is not reproducible with fake media streams.

Comment 5

[Randell Jesup [:jesup] (needinfo me)]

No longer repeatable