Closed Bug 1045889 Opened 11 years ago Closed 9 years ago

[B2G][RTSP] When the user get interrupted by an alarm, the video will not resume

Categories

(Firefox OS Graveyard :: RTSP, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog, b2g-v2.0 affected, b2g-v2.1 affected)

RESOLVED WONTFIX
tracking-b2g backlog
Tracking Status
b2g-v2.0 --- affected
b2g-v2.1 --- affected

People

(Reporter: psiphantong, Assigned: ethan)

References

()

Details

(Whiteboard: [2.0-flame-test-run-3])

Attachments

(1 file)

Description: When the user get interrupted by an alarm, the video will not resume Setup Steps: 1) Flame device is set to 319mb Repro Steps: 1) Update a Flame device to BuildID: 20140728000238 2) Set a alarm. The alarm will ring after 2 minutes 3) Go to http://goo.gl/BhJd77 4) Tap Video test page Actual: the video does not resume Expected: the video does resume Environmental Variables: Device: Flame 2.0 Build ID: 20140728000238 Gaia: 0a864988f5dce7f9f3dea9609e8ef054679c30ff Gecko: 2da96d621030 Version: 32.0 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Repro frequency: 80% Link to failed test case: https://moztrap.mozilla.org/manage/case/8107/ See attached: video, logcat, https://www.youtube.com/watch?v=kzs2jlHsNy0
This issue also reproduces on the Flame 2.1 (319mb), Open_C 2.1, Flame 2.0(512mb), Open_C 2.0. The video does not resume Flame 2.1 (319mb) Environmental Variables: Device: Flame Master Build ID: 20140728040209 Gaia: 295967a0b824a355ae9d57fb08f3632ed2ad18dd Gecko: a4dcfbebcb58 Version: 34.0a1 (Master) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Open_C 2.1 Environmental Variables: Device: Open_C Master Build ID: 20140728040209 Gaia: 295967a0b824a355ae9d57fb08f3632ed2ad18dd Gecko: a4dcfbebcb58 Version: 34.0a1 (Master) Firmware Version: P821A10V1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Flame 2.0(512mb) Environmental Variables: Device: Flame 2.0 Build ID: 20140728000238 Gaia: 0a864988f5dce7f9f3dea9609e8ef054679c30ff Gecko: 2da96d621030 Version: 32.0 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Open_C 2.0 Environmental Variables: Device: Open_C 2.0 Build ID: 20140728000238 Gaia: 0a864988f5dce7f9f3dea9609e8ef054679c30ff Gecko: 2da96d621030 Version: 32.0 (2.0) Firmware Version: P821A10V1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 _______________________________________________________________________________________________________________________ The issue does not reproduce on the Buri 2.1, Buri 2.0, Flame 1.4(319mb), Buri 1.4, Open_C v1.4, Base Image v122, and the Base Image v121-2 because the format is not supported. Buri 2.1 Environmental Variables: Device: Buri Master Build ID: 20140728073003 Gaia: 295967a0b824a355ae9d57fb08f3632ed2ad18dd Gecko: d77f6a96ff96 Version: 34.0a1 (Master) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Buri 2.0 Environmental Variables: Device: Buri 2.0 Build ID: 20140726063007 Gaia: 0a864988f5dce7f9f3dea9609e8ef054679c30ff Gecko: 2da96d621030 Version: 32.0 (2.0) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Flame 1.4(319MB) Environmental Variables: Device: Flame 1.4 Build ID: 20140728063001 Gaia: eb3b185325901d4c04e2d43eb58d90835213bea9 Gecko: aae9112f1fc6 Version: 30.0 (1.4) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Buri 1.4 Environmental Variables: Device: Buri 1.4 Build ID: 20140728063001 Gaia: eb3b185325901d4c04e2d43eb58d90835213bea9 Gecko: aae9112f1fc6 Version: 30.0 (1.4) MOZ Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Open_C v1.4 v1.4 Environmental Variables: Device: Open_C v1.4 MOZ BuildID: 20140728000238 Gaia: 0a864988f5dce7f9f3dea9609e8ef054679c30ff Gecko: 2da96d621030 Version: 32.0 Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Base Image v122 Environmental Variables: Device: Flame 1.3 Build ID: 20140616171114 Gaia: e1b7152715072d27e0880cdc6b637f82fa42bf4e Gecko: e181a36ebafaa24e5390db9f597313406edfc794 Version: 28.0 (1.3) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0 Base Image v121-2 Environmental Variables: Device: Flame 1.3 Build ID: 20140610200025 Gaia: e106a3f4a14eb8d4e10348efac7ae6dea2c24657 Gecko: b637b0677e15318dcce703f0358b397e09b018af Version: 28.0 (1.3) Firmware Version: v121-2 User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Please clarify the actual results for the branches the issue did not reproduce on.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(psiphantong)
Correct branch results, the issue does not reproduce on the Buri 2.1 and the Buri 2.0. The video does resume The issue does not reproduce on the Flame 1.4(319mb), Buri 1.4, Open_C v1.4, Base Image v122, and the Base Image v121-2 because the format is not supported.
Flags: needinfo?(psiphantong) → needinfo?(ktucker)
Please attach a logcat.
Flags: needinfo?(ktucker) → needinfo?(psiphantong)
Attached file aa.txt
Flags: needinfo?(psiphantong) → needinfo?(ktucker)
Edward, could your please take a look at this and weigh in on whether we should block on this?
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(edchen)
See Also: → 1045351
[Blocking Requested - why for this release]: [Blocking Requested - why for this release]: I suggest it as blocker because this is impacted to RTSP feature.
blocking-b2g: --- → 2.1?
Flags: needinfo?(edchen)
Edward - Wouldn't we want to nominate this for 2.0 here since this reproduces on 2.0 if we were to triage this?
Flags: needinfo?(edchen)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
I will look into this issue.
Assignee: nobody → ettseng
(In reply to Ethan Tseng [:ethan] from comment #9) > I will look into this issue. I guess it is a duplication to bug 1045351
HI Jason, I agree to fix on 2.0 and 2.1.
Flags: needinfo?(edchen)
(In reply to Benjamin Chen [:bechen] from comment #10) > (In reply to Ethan Tseng [:ethan] from comment #9) > > I will look into this issue. > > I guess it is a duplication to bug 1045351 Okay. Then I'll try to reproduce this bug and see if the patch of bug 1045351 could fix it. Benjamin, Thanks for your information. :)
(In reply to Edward Chen[:edchen] from comment #11) > HI Jason, > > I agree to fix on 2.0 and 2.1. Okay, then can you set the blocking nomination flag here to 2.0?
Flags: needinfo?(edchen)
(In reply to Jason Smith [:jsmith] from comment #13) > (In reply to Edward Chen[:edchen] from comment #11) > > HI Jason, > > > > I agree to fix on 2.0 and 2.1. > > Okay, then can you set the blocking nomination flag here to 2.0? [Edward] Set blocking flag to 2.0.
blocking-b2g: 2.1? → 2.0?
Flags: needinfo?(edchen)
Hi Pete, Actually I can hardly reproduce this bug on my Flame. However, according to Benjamin's judge, this bug is possibly a duplicate of bug 1045351. If it is, then the reproduction rate would be random since it's a kind of timing/deadlock issue. Could you please apply the patch in bug 1045351 to verify it fix this issue? https://bugzilla.mozilla.org/attachment.cgi?id=8465294 p.s. The code change is in framework. So you have to build/flash the base image.
Flags: needinfo?(psiphantong)
Backlog - the impact of this bug isn't too bad, since the user could resume the video manually after the alarm goes off. I'm pretty sure that this problem is present on video content on the web in general too, so I don't think the general video content on the web issue is a regression.
blocking-b2g: 2.0? → backlog
(In reply to Jason Smith [:jsmith] from comment #16) > Backlog - the impact of this bug isn't too bad, since the user could resume > the video manually after the alarm goes off. Hi Jason, AFAIK, if the root cause of this bug is really the same as bug 1045351, the user could not resume the video manually. Although the reproduction rate is not 100%, once happened, the video could no longer be resumed due to a logic error in HW decoder. The only thing the user can do in such situation is to terminate the browser app and re-launch it.
(In reply to Ethan Tseng [:ethan] from comment #15) > Hi Pete, > Could you please apply the patch in bug 1045351 to verify it fix this issue? > https://bugzilla.mozilla.org/attachment.cgi?id=8465294 > > p.s. The code change is in framework. So you have to build/flash the base > image. Hi Ethan - unfortunately on our end here we currently only have the ability to apply patches that have been uploaded to github. Our current options are to get you to do that - or we can also wait until the patch in bug 1045351 lands, and then re-test this bug in a central build with that patch in it. QA-Wanted to test this when one of those two things occur.
Flags: needinfo?(psiphantong)
Keywords: qawanted
https://bugzilla.mozilla.org/show_bug.cgi?id=1045351#c16 states: "I dont think there are any plans for CAF to support v2.0 with JB. No action for CAF on this bug anymore" meaning that that patch is not going to land
Keywords: qawanted
blocking-b2g: backlog → ---
No one is actually working on RTSP for FxOS right now.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: