Closed
Bug 1076841
Opened 9 years ago
Closed 9 years ago
getUserMedia Video broken due to delayed init of MediaPlayers
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(firefox35 verified, fennec35+)
VERIFIED
FIXED
People
(Reporter: TeoVermesan, Assigned: gcp)
References
Details
(Keywords: regression, reproducible)
Attachments
(1 file)
6.75 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
Tested with: Device: Samsung Galaxy S5 (Android 4.4) Build: Firefox for Android 35.0a1 (02-10-2014) Steps to reproduce: 1. Go to: http://mozilla.github.io/webrtc-landing/gum_test.html 2. Choose Video 3. Choose share from the doorhanger notification Expected result: - A video should appear with the built-in camera active showing the content from my camera. Actual result: - "Starting video failed" is displayed May be bug 1074202 the cause?
Updated•9 years ago
|
Flags: needinfo?(teodora.vermesan)
Keywords: regression,
regressionwindow-wanted
Updated•9 years ago
|
tracking-fennec: --- → ?
Comment 1•9 years ago
|
||
I see W/GeckoEventDispatcher( 6810): No listeners for MediaPlayer:Get
Keywords: reproducible
Comment 2•9 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #1) > I see W/GeckoEventDispatcher( 6810): No listeners for MediaPlayer:Get That is Chromecast related and should not be related to this issue. This is probably happening because we are delaying the MediaPlayerManager loading for performance reasons. Again, should not be related to this bug.
Comment 3•9 years ago
|
||
Last good revision: 124797ab4a5c First bad revision: a1d7b16101c7 Pushlog: https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=124797ab4a5c&tochange=a1d7b16101c7 wjohnston@mozilla.com Wed Oct 01 16:43:41 2014 +0000 a1d7b16101c7 Wes Johnston — Bug 1064669 - Initialize MediaPlayers in delayed startup. r=mfinkle
Blocks: 1064669
Flags: needinfo?(teodora.vermesan)
Keywords: regressionwindow-wanted
Summary: Video / getUserMedia is broken → Regression: getUserMedia Video broken due to delayed init of MediaPlayers
Assignee | ||
Comment 4•9 years ago
|
||
I'll investigate closer what's really up here.
Assignee: nobody → gpascutto
Assignee | ||
Comment 5•9 years ago
|
||
E/WEBRTC-JC(13864): startCapture failed E/WEBRTC-JC(13864): java.lang.IllegalThreadStateException: Expected thread 1 ("main"), but running on thread 483 ("Thread-483") E/WEBRTC-JC(13864): at org.mozilla.gecko.util.ThreadUtils.assertOnThreadComparison(ThreadUtils.java:171) E/WEBRTC-JC(13864): at org.mozilla.gecko.util.ThreadUtils.assertOnUiThread(ThreadUtils.java:116) E/WEBRTC-JC(13864): at org.mozilla.gecko.GeckoApp.addAppStateListener(GeckoApp.java:250) E/WEBRTC-JC(13864): at org.webrtc.videoengine.VideoCaptureAndroid.startCapture(VideoCaptureAndroid.java:210) E/WEBRTC-JC(13864): at dalvik.system.NativeStart.run(Native Method) D/WEBRTC-JC(13864): stopCapture
Assignee | ||
Comment 6•9 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #3) > Wed Oct 01 16:43:41 2014 +0000 a1d7b16101c7 Wes Johnston — Bug 1064669 - > Initialize MediaPlayers in delayed startup. r=mfinkle This is indeed the bug that caused it, the patch for it is simply completely broken.
Assignee | ||
Comment 7•9 years ago
|
||
Attachment #8499491 -
Flags: review?(mark.finkle)
Updated•9 years ago
|
Attachment #8499491 -
Flags: review?(mark.finkle) → review+
Assignee | ||
Comment 8•9 years ago
|
||
Backed out, see 1064669.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Updated•9 years ago
|
tracking-fennec: ? → 35+
status-firefox35:
--- → fixed
Flags: qe-verify+
Flags: in-testsuite?
Summary: Regression: getUserMedia Video broken due to delayed init of MediaPlayers → getUserMedia Video broken due to delayed init of MediaPlayers
Comment 9•9 years ago
|
||
Verified as fixed in Firefox for Android 35 Beta 1 with Nexus 4 (Android 4.4.4).
Status: RESOLVED → VERIFIED
Comment 10•5 years ago
|
||
Based on comment 9, I will remove the qe-verify flag, thanks.
Flags: qe-verify+
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•