[Browser] Browser abruptly closes/crashes while loading parts of a long webpage/blog.

NEW
Unassigned

Status

Firefox OS
Gaia::Browser
3 years ago
3 years ago

People

(Reporter: NicholasN, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v2.0 affected, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)

Details

(Whiteboard: [3.0-Daily-Testing], URL)

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Created attachment 8621673 [details]
logcat_browsercrash.txt

Description:
The user visits the following page: http://gizmodo.com/9-misconceptions-about-drones-that-engineers-wish-youd-1709827612?utm_source=recirculation&utm_medium=recirculation&utm_campaign=fridayAM (or for a smaller url: http://tinyurl.com/oojahxx). When scrolling down, lower parts of the page take longer to load in, and appear low resolution or blank. If the user keeps scrolling to these low res or blank areas of the page, the browser will eventually crash or abruptly force quit.


Repro Steps:
1) Update a Flame to 20150612010203
2) Open the browser, and navigate to http://tinyurl.com/oojahxx
3) Scroll down the page, attempting to stay on low res or blank areas which are still loading in.


Actual:
Browser eventually crashes.


Expected:
The page loads appropriately.


Notes:

Environmental Variables:
Device: Flame 3.0
Build ID: 20150612010203
Gaia: 9f36b711af7597a6a32471c3305cf1e2d6947d39
Gecko: 0093691d3715
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 41.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0


Repro frequency: 5/5
See attached: video clip, logcat
(Reporter)

Updated

3 years ago
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-master: --- → affected
Flags: needinfo?(pbylenga)
Whiteboard: [3.0-Daily-Testing]
(Reporter)

Updated

3 years ago
qawanted to see if this is a regression.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
Keywords: qawanted
Unable to reproduce on Flame 3.0 (319 memory)

After several attempts (~15 with browser cache clearing between attempts) I was unable to reproduce the results seen in comment 0. Leaving QA Wanted to see if others can reproduce.

Device: Flame 3.0
Build ID: 20150612010203
Gaia: 9f36b711af7597a6a32471c3305cf1e2d6947d39
Gecko: 0093691d3715
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 41.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
I was unable to reproduce this issue on the original builds or builds from today without putting lots of memory pressure on the phone (multiple open apps/browser tabs) but using those methods it did not matter the size of the website I was on.

Environmental Variables:
Device: Flame 3.0
BuildID: 20150616071225
Gaia: c92e9d14022f0191f8ccdaadf1752352cde97be0
Gecko: abaec2f7ed2c
Gonk: Could not pull gonk.  Did you shallow Flash?
Version: 41.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0

Environmental Variables:
Device: Flame 3.0
BuildID: 20150612115045
Gaia: b387bcad9bf8389580a8ae133b071053cfc9c30f
Gecko: 0c3bca1b4935
Gonk: Could not pull gonk.  Did you shallow Flash?
Version: 41.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
This issue also occurs on the Flame 2.2, 2.1 and 2.0

The browser will force close when scrolling the Gizmodo page repeatedly. 2.0 is slightly different but the page still closes. The user is presented with the "Sad face" page.

Device: Flame 2.2
BuildID: 20150618002507
Gaia: 3414b07dc489976bf510fd8042c0af3b1192c160
Gecko: a2db74491088
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

Device: Flame 2.1
BuildID: 20150618001205
Gaia: f8b848c82d1ed589f7a1eb5cc099830c867ff1d4
Gecko: 0ebea88c344d
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 34.0 (2.1) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Device: Flame 2.0
BuildID: 20150618000208
Gaia: 5552bf529d3d6775a968942e9afa6c1d4037362c
Gecko: d78115b1ed80
Gonk: bd9cb3af2a0354577a6903917bc826489050b40d
Version: 32.0 (2.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

STR:

1. Go to www.gizmodo.com
2. Scroll down in a prompt manner as the webpage loads.
3. Let the page load for a little bit and scroll the page again.
4. Keep repeating steps 2 and 3.

The browser app will force close.
status-b2g-v2.0: --- → affected
status-b2g-v2.1: --- → affected
status-b2g-v2.2: --- → affected
Flags: needinfo?(pbylenga)
Keywords: qawanted
Then this might be part of the larger memory pressures we've seen instead of something unique with gizmodo.
QA Whiteboard: [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
You need to log in before you can comment on or make changes to this bug.