Closed
Bug 1212081
Opened 10 years ago
Closed 10 years ago
getUserMedia doesn't work for audio
Categories
(Core :: WebRTC, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: matthias.schertler, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0
Build ID: 20150929144111
Steps to reproduce:
I was using getUserMedia with options { audio: true } in Firefox 41.0.1. See attached test.html for my example code.
Actual results:
The browser didn't ask for permission. No success callback, no error callback.
When I close the browser and open it again it says that firefox is already running.
I have the same effect on all pages that use getUserMedia using audio. Video works.
Expected results:
The browser should ask for permission to allocate the microphone. Afterwards the success or the error callback should be called.
| Reporter | ||
Updated•10 years ago
|
OS: Unspecified → Windows 10
Hardware: Unspecified → x86
| Reporter | ||
Comment 1•10 years ago
|
||
Also attached the entry from the windows event log that is created when i try to restart Firefox after the problem.
WFM with FF41 on Win 7:
start
finished
navigator.mozGetUserMedia has been replaced by navigator.mediaDevices.getUserMedia
success
Comment 3•10 years ago
|
||
Works for me in FF 44 Nightly Linux, and in FF 39, 39.0.3, and 41.0.1 on Windows 7 (with USB headset).
Can someone in QA or elsewhere try this on a Win10 machine? This may well be a problem with a specific audio device driver under win10 (i.e. not really our bug, though we might be able to work around it).
You could capture logs using NSPR_LOG_MODULES=getusermedia:4,mediamanager:4 (see https://wiki.mozilla.org/Media/WebRTC/Logging) and upload them here.
Reporter, can you indicate what the HW and driver is? And if possible, get the NSPR logs per above.
Flags: needinfo?(matthias.schertler)
Comment 4•10 years ago
|
||
I just tried on Windows 10 with Fx 42.0b8 and I get the permission prompt which asks for the microphone access. It worked with the attached test page as well as with our webrtc-landing pages. So seems to be a machine specific problem.
Comment 5•10 years ago
|
||
Resolving incomplete; please reopen or refile if this still is an issue with the data requested in comment 3. Thanks
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
| Reporter | ||
Comment 6•10 years ago
|
||
Sorry, I can't reproduce any more. No more support needed. Thank you, guys!
Flags: needinfo?(matthias.schertler)
Comment 7•10 years ago
|
||
@matthias.schertler@gmx.net - Thanks for retesting.
Resolution: INCOMPLETE → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•