Closed Bug 1041003 Opened 11 years ago Closed 11 years ago

[B2G][Flame][Poppit] OOM close if the screen is locked during gameplay

Categories

(Firefox OS Graveyard :: Performance, defect, P1)

Product:
Firefox OS Graveyard
Component:
Performance
Platform:
ARM
Gonk (Firefox OS)
Type:
defect

Tracking

(b2g-v1.4 unaffected, b2g-v2.0 affected, b2g-v2.1 affected)

Status:
RESOLVED WONTFIX
Tracking Flags:
Tracking Status
b2g-v1.4 --- unaffected
b2g-v2.0 --- affected
b2g-v2.1 --- affected

People

(Reporter: rpribble, Unassigned)

References

(
URL
)

Details

(Keywords: regression, Whiteboard: [273MB-Flame-Support], [2.0-exploratory])

Attachments

(1 file)

Logcat.txt
362.22 KB, text/plain
Details
Attached file Logcat.txt —
Description: If the user locks the device during gameplay, the app will OOM close and Poppit will no longer be open when the user unlocks the device. This causes a loss of information and the user has to start at the beginning again. Repro Steps: 1) Update a Flame to BuildID: 20140717000201 2) Install and launch Poppit from the Marketplace 3) Begin playing a game 4) Lock the device 5) Unlock the device Actual: The app will OOM close and will be gone when the user unlocks the device causing a loss of information, and the user will have to begin at the beginning again. Expected: No loss of information ever occurs and user is able to lock and unlock the device without causing apps to OOM close. Environmental Variables: Device: Flame 2.0 MOZ ril (273MB) Build ID: 20140717000201 Gaia: aa4f795b81c6147d67c4f06009e166debcf8856e Gecko: 0ec0b9ac39f0 Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozila/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32. Notes: Is a separate bug needed for the Buri v2.1 results? Repro frequency: 100% See attached: Video (http://youtu.be/TtS6vy-wYrE), logcat -------------------------------------------------- This issue also occurs on the Flame v2.1. Environmental Variables: Device: Flame Master (273MB) Build ID: 20140718040202 Gaia: Unknown Gecko: e6e8c93a1b6e Version: 33.0a1 (Master) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0 The app will OOM close and will be gone when the user unlocks the device causing a loss of information, and the user will have to begin at the beginning again. -------------------------------------------------- This issue does not occur on the Buri v2.1 (the app rotates to the wrong orientation when the device is unlocked), Flame v2.0, Buri v2.0, Flame v1.4, Buri v1.4, and Open_C v1.4. v2.1 Environmental Variables: Device: Buri Master BuildID: 20140718040202 Gaia: Gecko: e6e8c93a1b6e Version: 33.0a1 Firmware Version: v1.2-device.cfg User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0 Environmental Variables: Device: Flame 2.0 MOZ ril Build ID: 20140718000232 Gaia: 34c24749e78496ac1317f4ddb573281c0ef2995e Gecko: 76309f978531 Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Environmental Variables: Device: Buri 2.0 MOZ ril Build ID: 20140718000232 Gaia: 34c24749e78496ac1317f4ddb573281c0ef2995e Gecko: 76309f978531 Version: 32.0a2 (2.0) Firmware Version: v1.2device.cfg User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 v1.4 Environmental Variables: Device: Flame v1.4 MOZ ril (273MB) BuildID: 20140718000231 Gaia: e0a732cf172d125eadfad59f0faf8f73b62012b8 Gecko: 074223c547af Version: 30.0 Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 v1.4 Environmental Variables: Device: Buri v1.4 MOZ ril BuildID: 20140718000231 Gaia: e0a732cf172d125eadfad59f0faf8f73b62012b8 Gecko: 074223c547af Version: 30.0 Firmware Version: v1.2-device.cfg User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 v1.4 Environmental Variables: Device: Open_C v1.4 MOZ ril BuildID: 20140718000231 Gaia: e0a732cf172d125eadfad59f0faf8f73b62012b8 Gecko: 074223c547af Version: 30.0 Firmware Version: P821A10V1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 No loss of information ever occurs and user is able to lock and unlock the device without causing apps to OOM close.
This issue DOES occur on the Open_C v2.1. v2.1 Environmental Variables: Device: Open_C v2.1 MOZ ril BuildID: 20140718040202 Gaia: Gecko: e6e8c93a1b6e Version: 33.0a1 Firmware Version: P821A10V1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0 The app will OOM close and will be gone when the user unlocks the device causing a loss of information, and the user will have to begin at the beginning again. --------------------------------------------- This issue does not occur on the Open_C v2.0. v2.0 Environmental Variables: Device: Open_C v2.0 MOZ ril BuildID: 20140718000232 Gaia: 34c24749e78496ac1317f4ddb573281c0ef2995e Gecko: 76309f978531 Version: 32.0a2 Firmware Version: P821A10V1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 No loss of information ever occurs and user is able to lock and unlock the device without causing apps to OOM close.
Component: General → Preinstalled B2G Apps
Product: Marketplace → Tech Evangelism
Summary: [B2G][Flame][Marketplace][Poppit] OOM close if the screen is locked during gameplay → [B2G][Flame][Poppit] OOM close if the screen is locked during gameplay
Version: Avenir → unspecified
Rachel - Can you include the QAnalyst-Triage flag here?
Flags: needinfo?(rpribble)
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(rpribble) → needinfo?(ktucker)
Rachel, can you please update the appropriate tracking flags here? Also, if this is a regression please add the keyword.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(rpribble)
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
status-b2g-v1.4: --- → unaffected
status-b2g-v2.0: --- → affected
status-b2g-v2.1: --- → affected
Flags: needinfo?(rpribble) → needinfo?(ktucker)
Keywords: regression
[Blocking Requested - why for this release]: This is a regression from 1.4 and this issue could frustrate the end user since their current progress will be lost in the game because they locked their device. Nominating this 2.0?
blocking-b2g: --- → 2.0?
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+]
Component: Preinstalled B2G Apps → Performance
Keywords: regressionwindow-wanted
Product: Tech Evangelism → Firefox OS
QA Wanted to retest on 319 MB Flame.
Keywords: regressionwindow-wanted → qawanted
Bug does not repro on Flame 2.1 and Flame 2.0, both on 319 MB. Flame 2.1 Build ID: 20140724040205 Gaia: c72257b2d27135bfcd68e89dd584182797784016 Gecko: 06ac51c2b8a8 Platform Version: 34.0a1 Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Flame 2.0 Build ID: 20140724000201 Gaia: 29266e18c35f4e72e35f1bba0e34f2fb6b995cc3 Gecko: 178fe2efc41d Platform Version: 32.0 Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Actual result: After locking and unlocking the device, the Poppit app will still be open and active.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Contact: ckreinbring
No Repro in 319 mem, removing blocking and leaving open for perf investigation
blocking-b2g: 2.0? → ---
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
I cannot reproduce this on a 319mb flame running build id: 20140721000201. I'm closing this as won't fix.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: