Closed Bug 1142213 Opened 9 years ago Closed 9 years ago

[Windows Management] Sometimes alarms from the clock app do not go off when recording a video with the camera app.

Categories

(Firefox OS Graveyard :: Gaia::Clock, defect, P3)

ARM
Gonk (Firefox OS)
defect

Tracking

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

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

People

(Reporter: jmitchell, Unassigned)

Details

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

Attachments

(1 file)

Description:
 Alarms should always interrupt the Camera but the alarm notification is not always triggering when actively recording video with the camera.

Occurs with both Alarm and Timer alarms

Repro Steps:
1) Update a Flame to 20150311010231
2) launch the clock app and set a timer to go off in 1 min
3) Launch the Camera app and record a video for longer than the time remaining 

Actual:
Alarm does not go off

Expected:
Alarm will go off and interrupt video recording (causing it to pause)

Environmental Variables:
Device: Flame Master
Build ID: 20150311010231
Gaia: 943c8b4039f59b08ba100390e164a076a20c892e
Gecko: fd8e079d6335
Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429
Version: 39.0a1 (Master)
Firmware Version: v188-1
User Agent: Mozilla/5.0 (Mobile; rv:39.0) Gecko/39.0 Firefox/39.0

Repro frequency: 10/50

See attached:  logcat 
In this logcat I start a 1 min timer. After 30 seconds I switch over to camera and begin recording. The timer SHOULD have gone off after 30 more seconds but did not. After a minute I stopped the video, switched to the clock app and stopped the logcat.
This issue does NOT occur in 2.2

Actual Results: Alarm always goes off during video recording (50/50 attempts)

Device: Flame 2.2 (KK - Nightly - Full Flash - 319mem)
Build ID: 20150311002522
Gaia: 3f032238a52f08e4c2f68a47ad065a96eb22d470
Gecko: 004fa1cb1dd4
Gonk: ebad7da532429a6f5efadc00bf6ad8a41288a429
Version: 37.0 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
[Blocking Requested - why for this release]:
Functional regression of a core feature.

Although reproduction is low, requesting a window if possible due to the severity of missing an alarm.
blocking-b2g: --- → 3.0?
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
I'm finding the broken window.
QA Contact: jmercado
QA Contact: jmercado → pcheng
This issue reproduces on 2.2. Sometimes alarm does not go off when recording a video. Repro rate: 1/4.

Device: Flame 2.2 (shallow flash, 319MB)
BuildID: 20150312020121
Gaia: 572d60e0a440ee4af50bc6b6adad8876eadbdb4d
Gecko: 84655024fbe8
Version: 37.0 (2.2) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

--------

This issue does NOT reproduce on 2.1. Bug repro rate: 0/20.

Device: Flame 2.1 (shallow flash 319MB)
BuildID: 20150311172419
Gaia: db751d9c200dce41cd03a61665746d245739a175
Gecko: 28ffee0d5b0c
Version: 34.0 (2.1) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

---

Removing window-wanted because I feel the repro rate is not high enough to get an accurate window.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Per Comment 4,please ignore Comment 3.

Note:I can repro this bug on some past Flame v2.2 but rate is low.
Can Clock take a look? thanks.
Component: Gaia::System::Window Mgmt → Gaia::Clock
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Intermittent, too soon to call this resolved.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
blocking-b2g: 2.5? → 2.5+
Priority: -- → P3
Device: Aries
Build ID: 20151010112617
Repro: 0/5

I'm unable to reproduce this on a current build. Both timers and alarms stop the video recording and show the alert screen. When dismissed, I am returned to the camera and it is no longer recording.

QAwanted to see if anyone else is able to reproduce the original report.
Keywords: qawanted
This issue appears to have been fixed on central. This bug is a low memory issue where clock app was getting LMK'ed when recording. Now I think they have implemented something that prevents alarms getting killed whenever Clock gets low memory killed.

This issue no longer reproduces on (repro rate 0 out of 10 attempts):
Device: Flame 2.5 (319MB)
BuildID: 20151016030225
Gaia: 8ea9029190af2ffeb04dcd97b323738125e31a0e
Gecko: d374d16cbb251c9dac5af69f8e186e821ce82fe2
Gonk: c4779d6da0f85894b1f78f0351b43f2949e8decd
Version: 44.0a1 (2.5) 
Firmware Version: v18Dv4
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0

Also wasn't able to repro this on Flame 2.2 full flash 319MB (repro rate 0 out of 5):
Device: Flame 2.2 (319MB)
BuildID: 20151016032501
Gaia: 885647d92208fb67574ced44004ab2f29d23cb45
Gecko: 9b9aad4197d9
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 37.0 (2.2) 
Firmware Version: v18Dv4
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

I guess we can close this as works for me.
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage?]
Flags: needinfo?(jmercado)
Keywords: qawanted
With pleasure.
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → WORKSFORME
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmercado)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: