Closed
Bug 1304978
Opened 8 years ago
Closed 8 years ago
[Presentation API] Failed to re-launch presentation
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 1313404
People
(Reporter: cynthiatang, Assigned: kuoe0.tw)
References
Details
(Whiteboard: [ft:conndevices])
Test case: https://moztrap.mozilla.org/manage/case/18153/ Install Fennec on phone Use sample web page: https://people.mozilla.org/~schien/test-presentation.html 1. Launch presentation 2. Terminate connection 3. Launch presentation again Expected: - Successful connection Actual: - Fennec would be closed - Failed to re-launch presentation Device: Nexus 5 and Nexus Player
Blocks: 1-UA_Presentation_API
Reproduced this issue, actually Firefox crashes when starting the new presentation from the second device https://pastebin.mozilla.org/8924104
Comment 3•8 years ago
|
||
(In reply to Mihai Pop from comment #2) > Reproduced this issue, actually Firefox crashes when starting the new > presentation from the second device > https://pastebin.mozilla.org/8924104 From the log, it should be the same issue as bug 1313404.
Reproduced this on Nexus 4(Android 5.1.1) and Nexus 6(Android 6.0.1), the reproduce rate is about 1 out of 2 tries.
Comment 5•8 years ago
|
||
based on the information in comment #3, this should a duplicate bug to bug 1313404.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
I wasn't able to reproduce this issue anymore on this build https://people-mozilla.org/~schien/presentation-api/fennec-52.0a1.en-US.android-arm.apk
Comment 7•8 years ago
|
||
(In reply to Mihai Pop from comment #6) > I wasn't able to reproduce this issue anymore on this build > https://people-mozilla.org/~schien/presentation-api/fennec-52.0a1.en-US. > android-arm.apk The crash you encountered is an assertion and it'll only happen on debug build. The build you pointed here is a release build so this crash should never happen.
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•