Closed
Bug 1264333
Opened 9 years ago
Closed 6 months ago
test_getUserMedia_audioCapture times out on Android
Categories
(Core :: WebRTC: Audio/Video, defect, P3)
Tracking
()
RESOLVED
FIXED
128 Branch
Tracking | Status | |
---|---|---|
firefox128 | --- | fixed |
People
(Reporter: dminor, Assigned: karlt)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
This test times out consistently on the emulator and on autophone and on my Nexus 6. When running locally the test appears to be running normally: I hear audio and the analyser debug canvas moves, but the test never completes.
Updated•9 years ago
|
Rank: 23
Priority: -- → P2
I can consistently repoduce the issue on my Nexus 5 (6.0.1).
It is because gUM stream output flat white noise, and analyser.waitForAnalysisSuccess never succeeds.
If I disable the two oscillators oscThroughMediaElement and oscThroughAudioDestinationNode, gUM will return the stream without noise.
Blocks: 1156472
Comment 2•8 years ago
|
||
Just note that this test make use of MediaRecorder. All media recorder tests are disabled either for every Android versions or for Android version 17 behind the general purpose bug 1232305.
Comment 3•7 years ago
|
||
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Blocks: audio-sharing
Assignee | ||
Comment 4•6 months ago
|
||
In the past Android preferred AUDIO_FORMAT_S16 and AudioSegment::Mix() did not support this. Android now prefers AUDIO_FORMAT_FLOAT32 and Mix() supports AUDIO_FORMAT_S16.
Assignee | ||
Comment 5•6 months ago
|
||
Depends on D211690
Updated•6 months ago
|
Assignee: nobody → karlt
Status: NEW → ASSIGNED
Pushed by ktomlinson@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/af8627946858
enable test_getUserMedia_audioCapture.html on Android r=padenot
Comment 7•6 months ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 6 months ago
status-firefox128:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 128 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•