Closed Bug 952251 Opened 11 years ago Closed 11 years ago

gUM audio consistently fails to capture mic input after one or two uses on FxOS

Categories

(Core :: WebRTC: Audio/Video, defect)

29 Branch
ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: jsmith, Unassigned)

Details

(Keywords: regression)

Build - Leo 1.4 12/19/2013

During audio P2P call testing, I noticed that after successfully having a 2 1/2 audio call talking from B2G --> Desktop on the same wifi network, I was never able to get mic input to be captured on followup gUM audio uses after about 15 - 20 seconds. A restart of the phone doesn't work around the problem - it persists after a restart. It even persists upon flashing new gaia/gecko builds on top of a base image.

STR looks something like the following:

1. Request & grant gUM audio access in a browser tab
2. Talk for about a minute or two
3. Kill the browser process
4. Request gUM audio again
5. Talk for a minute

Result - You'll notice in about 15 seconds, the sound you make will no longer be heard.

Note - this is a blocker for testing audio P2P calls, as I can only successfully get one audio P2P call to work on a single device before I hit this bug.

I'll try to nail down clearer STR with a different phone.
Steps wanted - can someone dig into this to see if they can reproduce this with consistent STR on 1.4 using http://mozilla.github.io/webrtc-landing/gum_test.html as a test page?
blocking-b2g: --- → 1.4?
QA Contact: gbennett
I think this is vendor image problem - it's only happening on the leo 1.1 base image with gaia/gecko on top, doesn't happen on Buri. Likely fixed when we get a new Leo base image.
No longer blocks: b2g-getusermedia, 945256
Status: NEW → RESOLVED
blocking-b2g: 1.4? → ---
Closed: 11 years ago
Keywords: steps-wanted
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.