Self-image frozen, other party unable to see or hear me.

NEW
Unassigned

Status

()

Core
WebRTC
P2
normal
Rank:
15
10 months ago
7 months ago

People

(Reporter: mossop, Unassigned)

Tracking

({stale-bug})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

10 months ago
Created attachment 8879710 [details]
aboutWebrtc.html

I was using appear.in to try to talk to someone. When I connected my self-image was completely frozen. The other party could neither hear nor see me, I could see them, I couldn't hear them but that might have been because their mic was muted.

This happened across multiple reconnects. Attached is about:webrtc from the calls.

Updated

10 months ago
Rank: 15
Priority: -- → P1

Comment 1

10 months ago
The logs show clearly that this was not a networking issue. Dave's Fx received plently of media. But almost nothing got send out - the little bit is ICE/STUN traffic and not actually media.
So most likely this is/was more of a local media access problem, which would also match with the local preview being frozen.

Unfortunately we still don't have very good logs for the media side which can get collected after the fact.

@jib: any idea what if/what we could do here?
Flags: needinfo?(jib)

Comment 2

10 months ago
I was just chatting with Alex about this issue and he pointed out that this sounds like it might have been a lockup in the OSX audio subsystem.

@Dave: if you should encounter this again, can you check if you are still able to play lets say a YouTube video?

Comment 3

10 months ago
@Dave: what OS was this on?
Flags: needinfo?(dtownsend)
(Reporter)

Comment 4

10 months ago
(In reply to Nils Ohlmeier [:drno] from comment #3)
> @Dave: what OS was this on?

This was on Windows 10
Flags: needinfo?(dtownsend)
Without reproduce steps there's not much to go on here.

You can get media logs by setting:

  NSPR_LOG_MODULES=timestamp:1,MediaManager:5
  NSPR_LOG_FILE=/tmp/log.txt
Flags: needinfo?(jib)
This is a P1 bug without an assignee. 

P1 are bugs which are being worked on for the current release cycle/iteration/sprint. 

If the bug is not assigned by Monday, 28 August, the bug's priority will be reset to '--'.
Keywords: stale-bug
Mass change P1->P2 to align with new Mozilla triage process
Priority: P1 → P2
You need to log in before you can comment on or make changes to this bug.