Closed
Bug 886050
Opened 11 years ago
Closed 11 years ago
nightly Firefox for android stops browser after sharing video and camera in gUM test
Categories
(Core :: WebRTC, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: edwardb, Unassigned)
Details
(Whiteboard: [getUserMedia][android-gum-])
Attachments
(1 file)
User Agent: Mozilla/5.0 (Android; Mobile; rv:24.0) Gecko/24.0 Firefox/24.0 (Nightly/Aurora)
Build ID: 20130622031042
Steps to reproduce:
visited gum_test.HTML webpage
gave permission.
Actual results:
permission was granted.
video and audio was broadcasting for 15-30sec.
Then the nightly browser disappeared restarting the android home app.
The camcorder with microphone icon remained in the android notification bar.
Expected results:
the video and audio should continue to broadcast.
shows when the nightly firefox for android was run...
...during the browser disappearing after sharing permission was granted
... and when browser "restarts" after clicking on the camcorder with microphone icon in the android notification bar.
Attachment #766349 -
Flags: review+
please disregard bug #885858 unless this browser did "crash" under linux 64-bit OS
Comment 3•11 years ago
|
||
Comment on attachment 766349 [details]
alogcat file before, during, and after running the nightly browser and the gUM_test
This isn't a patch.
Attachment #766349 -
Flags: review+
Comment 4•11 years ago
|
||
Is someone else able to reproduce this?
Comment 5•11 years ago
|
||
Works for me, we need better steps to reproduce, device, OS and stack if this is a crash.
Keywords: steps-wanted
Updated•11 years ago
|
Keywords: qawanted
Whiteboard: [getUserMedia][android-gum?] → [getUserMedia][android-gum-][closeme 7/1/2013]
Comment 6•11 years ago
|
||
Nothing to go off of here and closeme timer is hit. Closing as incomplete.
No longer blocks: android-webrtc
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Keywords: steps-wanted
Resolution: --- → INCOMPLETE
Whiteboard: [getUserMedia][android-gum-][closeme 7/1/2013] → [getUserMedia][android-gum-]
You need to log in
before you can comment on or make changes to this bug.
Description
•