Closed Bug 998148 Opened 6 years ago Closed 6 years ago

[Tarako] Timer will never ring if it gets OOM killed in the background

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: nhirata, Unassigned)

Details

(Whiteboard: [tarako-bug-bash-1.3T])

1. launch Clock app
2. go to timer
3. set for 1 minute w/ sound
4. hit home
5. launch gallery app
6. edit some picture for a minute

Expected : timer will sound
Actual: clock is OOM killed and timer never sounds

Gaia      a8d2d399f2939f4845abaa0df57abab241a2c782
Gecko     https://hg.mozilla.org/releases/mozilla-b2g28_v1_3t/rev/d97dad54cb61
BuildID   20140417004002
Version   28.1
ro.build.version.incremental=eng.cltbld.20140417.115200
ro.build.date=Thu Apr 17 11:52:06 EDT 2014
Tarako
blocking-b2g: --- → 1.3T?
Whiteboard: [tarako-bug-bash-1.3T]
triage: this is a broken feature on the timer. 1.3T+
ni? Ian to check this initially. thanks
blocking-b2g: 1.3T? → 1.3T+
Flags: needinfo?(iliu)
Joe, I check the build v1.3 on Inari. If we set a timer and close clock app in recent app, the timer won't notify user in time. Even if I launch clock app, there is no any message for overdue timer. I guess it's an expected result.

Hi Marcus, is it an expected behaviour for build v1.3? Thanks.
Flags: needinfo?(iliu)
Flags: needinfo?(m)
Leaving qawanted to see behavior on 1.3 Buri for comparison.
Keywords: qawanted
This is expected behavior in 1.3. Bug 898354 tracked an overhaul of the Timer feature which enabled background notification and all sorts of other features which make the Timer actually useful, however it did not land in time for 1.3.
Status: NEW → RESOLVED
blocking-b2g: 1.3T+ → ---
Closed: 6 years ago
Flags: needinfo?(m)
Resolution: --- → WONTFIX
Keywords: qawanted
Marcus, thanks for your confirmation in detail.:)
You need to log in before you can comment on or make changes to this bug.