Closed Bug 976628 Opened 7 years ago Closed 7 years ago

[B2G][Camera]Videos recorded after quickly pressing stop then record do not play when viewing them from the filmstrip


(Firefox OS Graveyard :: Gaia::Camera, defect)

Gonk (Firefox OS)
Not set


(blocking-b2g:1.4+, b2g-v1.3 unaffected, b2g-v1.4 fixed)

1.4 S2 (28feb)
blocking-b2g 1.4+
Tracking Status
b2g-v1.3 --- unaffected
b2g-v1.4 --- fixed


(Reporter: astole, Assigned: wilsonpage)




(Keywords: regression)

Every video recorded after quickly pressing stop then record does not play when viewing it through the filmstrip in the camera app.  Closing and reopening the app by long pressing home fixes the issue. The videos are playable in the videos app.

Repro Steps:
1) Updated Buri to BuildID: 20140224040201
2) Open the Camera app
3) Switch to Video mode
4) Once the recording has started, quickly press stop then record again
5) Press stop again then record a video like normal
6) After stopping the recording, attempt to view the video recorded by selecting it from the filmstrip

The videos recorded after step 4 do not play when selecting them from the filmstrip.

All videos selected from the filmstrip are able to be played.

Environmental Variables:
Device: Buri v1.4 M/C Mozilla RIL
BuildID: 20140225040205
Gaia: e0f39c7179c8b297326c0e2313950610be1f5c52
Gecko: e3daaa4c73dd
Version: 30.0a1
Firmware Version: V1.2-device.cfg

Repro frequency: 100%
See attached: Video
Does this reproduce on 1.3?
Keywords: qawanted
This issue does not occur on the latest 1.3.

Environmental Variables:
Device: Buri v1.3 Mozilla RIL
BuildID: 20140225004004
Gaia: 6e883bde818d4d53aef7b5b075b4b34267918360
Gecko: e597280f9300
Version: 28.0
Firmware Version: V1.2-device.cfg
What's bad here is the fact that doing a single quick start & stop recording of a video & then recording videos with normal lengths will always not allow the user to view the video from the filmstrip. The includes videos that were recorded with normal lengths after the quick start & stop occurred.

I've confirmed this as well on 1.4 Buri 2/24/2014.
blocking-b2g: --- → 1.4?
QA Contact: bzumwalt
Last working build (issue does NOT occur):
Device: Buri v1.4 Master Mozilla RIL
BuildID: 20140116040206
Gaia: 82878ba16172213cd00ba3e8b377564b290e59c1
Gecko: 324e2cba1029
Version: 29.0a1
Firmware Version: V1.2-device.cfg

First build where issue does occur:
Device: Buri v1.4 Master Mozilla RIL
BuildID: 20140117041037
Gaia: ef8bb31b462f364b57432a0724c78034d3f4f303
Gecko: b53589696cf8
Version: 29.0a1
Firmware Version: V1.2-device.cfg

Note: Unable to narrow window further as Tinderbox builds not available for this range
This needs a last working gaia/first broken gecko & vice versa analysis in the regression range.
Keywords: qawanted
Last Working Gecko/First Broken Gaia: Issue DOES reproduce
Gaia: ef8bb31b462f364b57432a0724c78034d3f4f303
Gecko: 324e2cba1029

First Broken Gecko/Last Working Gaia: Issue does not reproduce
Gaia: 82878ba16172213cd00ba3e8b377564b290e59c1
Gecko: b53589696cf8

gaia Pushlog:
Keywords: qawanted
blocking-b2g: 1.4? → 1.4+
Flags: needinfo?(wilsonpage)
Flags: needinfo?(dmarcos)
This will be fixed when bug 973616 lands. Currently awaiting Travis sign-off.
Flags: needinfo?(wilsonpage)
Depends on: 973616
Assignee: nobody → wilsonpage
Flags: needinfo?(dmarcos)
Fix landed on master as part of bug 973616
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.4 S2 (28feb)
You need to log in before you can comment on or make changes to this bug.