Closed Bug 1167399 Opened 9 years ago Closed 9 years ago

[Camera][Video] After recording, preview displays in a corner offscreen

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(blocking-b2g:2.5+, b2g-v2.2 unaffected, b2g-master affected)

RESOLVED WORKSFORME
blocking-b2g 2.5+
Tracking Status
b2g-v2.2 --- unaffected
b2g-master --- affected

People

(Reporter: onelson, Assigned: djf)

References

Details

(Keywords: regression, Whiteboard: [3.0-Daily-Testing])

Attachments

(2 files)

Description:
When user records a video in the camera app, they will observe a preview within the camera app. If this is accessed by the user and attempted to preview, they will observe that the preview is displayed offscreen and in the bottom left corner. Watching the preview will play the video in proper view. This condition is not observed in the 'Video' app, only preview in camera.


Repro Steps:
1) Update a Flame to 20150521184655
2) Open the Camera app.
3) Record a video
4) Tap preview to open preview UI.
5) Observe UI of preview before video is played

Actual:
Preview is cutoff in the corner offscreen until being played.

Expected:
Preview displays in full view of stilled image


Environmental Variables:
------------------------------

Device: Flame 3.0
Build ID: 20150521184655
Gaia: 208ec11c33c9bd2fab7fcf8647bc162c9f3d484f
Gecko: cb33535b93f2
Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67
Version: 41.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
*************************

Issue DOES NOT REPRO on 2.2 for flame devices
Results: Preview displays in full view of stilled image
Device: Flame 2.2
BuildID: 20150521002508
Gaia: bc42fbc12d622bffd7e8afcb8d56f8a1d9773c60
Gecko: 6e4eaf59efda
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
------------------------------

Repro frequency: 5/5
See attached: 
screenshot
logcat
QA Whiteboard: [QAnalyst-Triage?]
Keywords: regression
Attached image 2015-05-21-13-58-51.png
Flags: needinfo?(pbylenga)
[Blocking Requested - why for this release]:

Visible functional Regression. Poor UX. Nominating to block 3.0. Requesting a window
blocking-b2g: --- → 3.0?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
QA Contact: pcheng
mozilla-inbound regression window:

Last Working
Device: Flame
BuildID: 20150520183146
Gaia: 5a7f87b1505ba89b586372cbbbe9507d1016c40c
Gecko: 1f6a0d225927
Version: 41.0a1 (3.0 Master)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

First Broken
Device: Flame
BuildID: 20150520185539
Gaia: 5a7f87b1505ba89b586372cbbbe9507d1016c40c
Gecko: edddd285c20c
Version: 41.0a1 (3.0 Master)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Gaia is the same so it's a Gecko issue.

Gecko pushlog:
http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=1f6a0d225927&tochange=edddd285c20c

Possibly caused by Bug 1154974.
Blocks: 1154974
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Seth, can you take a look at this please? Looks like the landing for bug 1154974 might be the cause here.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker) → needinfo?(seth)
Wow, that is very strange. I can't really see how bug 1154974 could've caused this regression. I'll investigate. (Though since this doesn't affect 2.2, I can't investigate immediately.)
blocking-b2g: 3.0? → 3.0+
Oliver: the issue caused by bug 1154974 has been fixed (but I don't remember the bug number) and I suspect it has resolved this bug. Could you check whether this bug still reproduces?

I'm taking the bug so it doesn't get lost if it is still an issue. Please go ahead and close it if it does not reproduce anymore.
Assignee: nobody → dflanagan
Flags: needinfo?(onelson)
This is easy to reproduce on a build from may 22, and is not memory related (i.e. it reproduces on a 1024mb flame as well as a 319mb).  It does not reproduce on current master. The underlying gecko bug has been fixed. Clearing the needinfo requests and resolving the bug.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(seth)
Flags: needinfo?(onelson)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: