[B2G][FTE] The user will encounter a white screen that they cannot get out of when tapping on links during the FTE

NEW
Unassigned

Status

Firefox OS
Gaia::First Time Experience
3 years ago
3 years ago

People

(Reporter: KTucker, Unassigned)

Tracking

({regression})

unspecified
ARM
Gonk (Firefox OS)
regression

Firefox Tracking Flags

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

Details

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

Attachments

(1 attachment)

Created attachment 8457462 [details]
FTEWhiteScreenofDeath.txt

Description:
The user will encounter a white screen that they cannot get out of when tapping on links during the FTE. The user will have to pull their battery and re-power on the device.

Repro Steps:
1) Updated Flame to Build ID: 20140716000201
2) After a fresh flash, tap "next" on the language selection screen.
3) Enable data and then keep tapping next until reaching the "Geolocation" screen.
4) Tap on "More about your privacy".
5) Tap on Firefox OS.
6) Tap on multiple links to open new pages. (The text that is highlighted blue).
7) Tap the "X" button to close the page. 
8) Tap on "Marketplace".
9) If the issue did not occur repeat steps 6,7 and 8.

Actual:
The user will encounter a white screen. They cannot exit the white screen and will have to pull out their battery and re-power on their device to recover.

Expected:
The user can navigate through different links in the FTE without issue. 

"Environmental Variables:
Device: Flame 2.0 (273mb)
BuildID: 20140716000201
Gaia: 5f8b1b8a2da9e3b531eee817a669f57fa4d9b9c6
Gecko: 913827496f65
Version: 32.0a2 (2.0) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Notes:
Repro frequency: 100%
See attached: Logcat, video
(Reporter)

Updated

3 years ago
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Issue does not occur on Flame 2.1, Buri 2.1, Open C 2.1, Flame 2.0 (512mb), Buri 2.0, Open C 2.0, Flame 1.4, Buri 1.4, or Open C 1.4.

The user does not encounter a white screen when navigating between pages in "More about your privacy".

Flame 2.1(273mb) 

Environmental Variables:
Device: Flame Master (273mb)
Build ID: 20140716040207
Gaia: d29773d2a011825fd77d1c0915a96eb0911417b6
Gecko: 691ffea49efb
Version: 33.0a1 (Master)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Buri 2.1

Environmental Variables:
Device: Buri Master
Build ID: 20140716040207
Gaia: d29773d2a011825fd77d1c0915a96eb0911417b6
Gecko: 691ffea49efb
Version: 33.0a1 (Master)
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Open C 2.1

Environmental Variables:
Device: Open_C Master
Build ID: 20140716040207
Gaia: d29773d2a011825fd77d1c0915a96eb0911417b6
Gecko: 691ffea49efb
Version: 33.0a1 (Master)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Flame 2.0(512mb)

Environmental Variables:
Device: Flame 2.0 (512mb)
BuildID: 20140716000201
Gaia: 5f8b1b8a2da9e3b531eee817a669f57fa4d9b9c6
Gecko: 913827496f65
Version: 32.0a2 (2.0) 
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Buri 2.0

Environmental Variables:
Device: Buri 2.0
Build ID: 20140716000201
Gaia: 5f8b1b8a2da9e3b531eee817a669f57fa4d9b9c6
Gecko: 913827496f65
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

Open C 2.0

Environmental Variables:
Device: Open_C 2.0
BuildID: 20140716000201
Gaia: 5f8b1b8a2da9e3b531eee817a669f57fa4d9b9c6
Gecko: 913827496f65
Version: 32.0a2 (2.0) 
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Flame 1.4(273mb)

Environmental Variables:
Device: Flame 1.4 (273mb)
Build ID: 20140716000202
Gaia: 393d72937727ad20e82b2ff7b13e3d7ff077a9f0
Gecko: 932c37978d37
Version: 30.0 (1.4)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Buri 1.4 

Environmental Variables:
Device: Buri v1.4 MOZ ril
BuildID: 20140716000202
Gaia: 393d72937727ad20e82b2ff7b13e3d7ff077a9f0
Gecko: 932c37978d37
Version: 30.0
Firmware Version: v1.2-device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Open C 1.4

Environmental Variables:
Device: Open_C 1.4
Build ID: 20140716000202
Gaia: 393d72937727ad20e82b2ff7b13e3d7ff077a9f0
Gecko: 932c37978d37
Version: 30.0 (1.4)
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
(Reporter)

Updated

3 years ago
Keywords: regression
nomming, user can get into an unrecoverable situation
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
Attaching a video link for this bug: http://youtu.be/o9sc1s6U6ZE
QA Wanted for a retest and triage against 319 MB Flame.
QA Whiteboard: [QAnalyst-Triage+]
Keywords: qawanted
With Flame throttled to 319mb:
This bug does NOT repro on: Flame 2.1, Flame 2.0, Flame 1.4

Actual Result: No white screen is seen on 319mb when following the STR.

Environmental Variables:
Device: Flame Master
Build ID: 20140728065013
Gaia: 295967a0b824a355ae9d57fb08f3632ed2ad18dd
Gecko: d77f6a96ff96
Version: 34.0a1 (Master)
Firmware Version: v122
-----------------------------------------------
Environmental Variables:
Device: Flame 2.0
Build ID: 20140728065913
Gaia: b56f023ff247312a344e8f233898e803459788b9
Gecko: e11d0b232ced
Version: 32.0 (2.0)
Firmware Version: v122
-----------------------------------------------
Environmental Variables:
Device: Flame 1.4
Build ID: 20140728061215
Gaia: eb3b185325901d4c04e2d43eb58d90835213bea9
Gecko: aae9112f1fc6
Version: 30.0 (1.4)
Firmware Version: v122
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Contact: croesch
No repro in 319 mem, leaving open for perf investigation
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)

Updated

3 years ago
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
You need to log in before you can comment on or make changes to this bug.