Closed
Bug 1031178
Opened 10 years ago
Closed 10 years ago
HTTP/RTSP streaming cannot be played more than once in B2G browser
Categories
(Core :: Audio/Video, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1024405
People
(Reporter: ethan, Assigned: ethan)
References
Details
Environment:
- Device : Flame
- OS : B2G 2.1
- Platform: Gecko 33.0a1
- Build ID: 20140625153547
Reproduction Steps:
1. Open B2G browser.
2. Click an MP4 video through either HTTP or RTSP protocol.
3. When the video is being played, click the back button to leave the page.
4. Click the same or another MP4 video through either HTTP or RTSP.
Expected Result:
The video can be played successfully.
Bug:
The media player hangs there. We cannot play any video through HTTP or RTSP from now on.
What the user can do is to terminate the browser app and launch it again.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → ettseng
Assignee | ||
Comment 1•10 years ago
|
||
BTW, the reproduction rate is 100%.
Assignee | ||
Comment 2•10 years ago
|
||
This is not an RTSP-specific issue.
It seems the HTMLDocument was not released and neither does the hardware decoder or any relevant resources.
I think the symptom is so critical that it could be a blocker.
blocking-b2g: --- → 2.0?
Comment 3•10 years ago
|
||
Chris - Is this a dupe of bug 1024405?
Component: General → Video/Audio
Flags: needinfo?(cpearce)
Product: Firefox OS → Core
Version: unspecified → Trunk
Comment 4•10 years ago
|
||
I expect the patch in Bug 1024405 would fix this.
Comment 5•10 years ago
|
||
Bumping to 2.1? since this applies to 2.1, not 2.0.
blocking-b2g: 2.0? → 2.1?
Assignee | ||
Comment 6•10 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #5)
> Bumping to 2.1? since this applies to 2.1, not 2.0.
Oh, I did produce this bug on 2.1, and was not aware 2.0 is not affected.
Thanks for correcting this.
Comment 7•10 years ago
|
||
(In reply to Ethan Tseng [:ethan] from comment #6)
> (In reply to Jason Smith [:jsmith] from comment #5)
> > Bumping to 2.1? since this applies to 2.1, not 2.0.
>
> Oh, I did produce this bug on 2.1, and was not aware 2.0 is not affected.
> Thanks for correcting this.
Yeah - the regressing patch that caused this is only present on 2.1.
Comment 8•10 years ago
|
||
QA Wanted to verify that this works post landing of bug 1024405 (test on Tuesday build or later).
Keywords: qawanted
Assignee | ||
Comment 9•10 years ago
|
||
(In reply to Chris Pearce (:cpearce) from comment #4)
> I expect the patch in Bug 1024405 would fix this.
By updating m-c to bring in the patch of bug 1024405, I verified this bug is resolved on 2.1.
Thanks Chris!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•