1039066 - [B2G][Browser] Panning and zooming on the Outlook website causes an OOM to occur

Status: RESOLVED WONTFIX

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

Description

[KTucker [:KTucker][Inactive 3/4/2016]]

Attachment: OutlookLogcat.txt

Description:
Panning and zooming in on the Outlook website causes an OOM to occur which leads to non functional buttons. The "Close tab" and "Reload" will not respond when tapped on and if the user locks their device, the user cannot unlock the phone. The user will have to pull out the battery and re-power on their device. 

Repro Steps:
1) Updated Flame to Build ID: 20140715000201
2) Open the browser and go to www.outlook.com
3) Keep panning and zooming in on the page until the browser encounters an OOM error. 
4) Tap on the "Close tab" and "Reload" buttons.
5) Lock the device by tapping the "Power/Lock" button.
6) Wake the phone back up and try to slide to unlock the phone on the lockscreen. 

Actual:
An OOM occurs if the user keeps zooming in on the Outlook page which leads to non functioning buttons. The user will have to pull out their battery and re-power on their device. 

Expected:
The user can zoom in on the Outlook page without issue and buttons always respond to user's touch. 

Environmental Variables
Device: Flame v 2.0(273mb)
Build ID: 20140715000201
Gecko: https://hg.mozilla.org/releases/mozilla-aurora/rev/d32649a24965
Gaia: 2c6c413ed729d465c52d6c2d5d458e2eee79e956
Platform Version: 32.0a2
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Notes:
Repro frequency: 100%
See attached: Video clip, logcat

Comment 1

[KTucker [:KTucker][Inactive 3/4/2016]]

I could reproduce the OOM issue on the Flame 1.4(273mb) but not the non functioning buttons. 

The user will encounter an OOM when zooming in on the Outlook page but the user can tap on the "Close tab" and "Reload" buttons without issue.

Flame 1.4(273mb)

Environmental Variables:
Device: Flame 1.4(273mb)
Build ID: 20140715000202
Gaia: b7d36622c7df92c976c37520ccab25199c7ada91
Gecko: de7ecfb00955
Version: 30.0 (1.4)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

-------------------------------------------------------------------------------------------

This issue does not reproduce on the Buri 2.1, Open C 2.1, Buri 2.0, Flame 2.0(512mb), Open C 2.0, Buri 1.4 and Open C 1.4.

Buri 2.1

Environmental Variables:
Device: Buri Master
Build ID: 20140715040206
Gaia: 46cd188fdda2397d2b8f3303a184dcd52952e2b2
Gecko: e032c429908b
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
BuildID: 20140715040206
Gaia: 46cd188fdda2397d2b8f3303a184dcd52952e2b2
Gecko: e032c429908b
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

Buri 2.0

Environmental Variables:
Device: Buri 2.0
Build ID: 20140715000201
Gaia: 2c6c413ed729d465c52d6c2d5d458e2eee79e956
Gecko: d32649a24965
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"

Flame 2.0(512mb)

Environmental Variables:
Device: Flame 2.0(512mb)
BuildID: 20140715000201
Gaia: 2c6c413ed729d465c52d6c2d5d458e2eee79e956
Gecko: d32649a24965
Version: 32.0a2 (2.0) 
Firmware Version: v122
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
Build ID: 20140715000201
Gaia: 2c6c413ed729d465c52d6c2d5d458e2eee79e956
Gecko: d32649a24965
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

Buri 1.4

Environmental Variables:
Device: Buri 1.4
Build ID: 20140715000202
Gaia: b7d36622c7df92c976c37520ccab25199c7ada91
Gecko: de7ecfb00955
Version: 30.0 (1.4)
Firmware Version: v1.2device.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: 20140715000202
Gaia: b7d36622c7df92c976c37520ccab25199c7ada91
Gecko: de7ecfb00955
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

Comment 2

[KTucker [:KTucker][Inactive 3/4/2016]]

After further research, the non functional buttons will occur when zooming and panning the Outlook website while the keyboard is up on the screen. The user will have to remove their battery at this point. There is not a workaround for this issue.

http://youtu.be/RK5xo3NlHRo

Comment 3

[Ben Francis [:benfrancis]]

Chris Lord suggests re-testing this with the APZC audit patch that landed today on mozilla-central in bug 1009733

Comment 4

[Gregor Wagner [:gwagner]]

Can we test again based on comment 3? not sure when the patch actually is in the nightly build.

Comment 5

[Milan Sreckovic [:milan] (needinfo for best results)]

Following the (new) rule of assigning to the person doing investigation; once we get the info mentioned in comment 4, please switch it back to unassigned, and I'll take it from there.

Comment 6

[Milan Sreckovic [:milan] (needinfo for best results)]

Also, there is an ongoing conversation as to how exactly we need to configure the Flame to simulate 256mb device; I see you're using 273mb - could you try with 319mb and see if that makes a difference?

Comment 7

[Pi Wei Cheng [:piwei] (inactive)]

I'll be fulfilling KTucker's testing requests tomorrow (so I can be sure we're testing a build that contains the fix from bug 1009733)

Comment 8

[Pi Wei Cheng [:piwei] (inactive)]

(In reply to Gregor Wagner [:gwagner] from comment #4)
> Can we test again based on comment 3? not sure when the patch actually is in
> the nightly build.

Tested again with today's master build and OOM still occurs, however, the device no longer locks up when OOM occurs with keyboard invoked on the screen - the device successfully responds to "Close tab" and "Reload" buttons.

Also I found the original repro could be hard to hit OOM even on a build on 7/15. It'd be easier to hit OOM if I go to a picture-heavy website like imgur.com, then go to outlook.com and do the repro.

(In reply to Milan Sreckovic [:milan] from comment #6)
> could you try with 319mb and see if that makes a difference?

It does make a difference. I tried for 15 minutes zooming&panning on imgur.com, outlook.com, and yahoo.co.jp with no browser OOM.

Tested on:
Device: Flame (273MB / 319MB)
Build ID: 20140718040333
Gaia: Unknown
Gecko: 74985b96c4c3
Version: 33.0a1 (Master)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Note:
Gaia is displayed as unknown due to bug 1039739

Comment 9

[Milan Sreckovic [:milan] (needinfo for best results)]

Re-triage based on comment 8:

I've lost track of whether 273mb or 319mb or some such value is the one that best simulates the problem, so trying this on a production device is probably something we need to do.

OOM is going to happen when we use too much memory - we seem to recover from it.

Still a blocker?

Comment 10

[Jason Smith [:jsmith]]

Kevin - I think we're talking about two different bugs here - the OOM issue & the non-functional buttons issue. The OOM issue is not a regression, but the non-functional buttons is a regression. Can you open a separate bug for the non-functional button issue?

On the basis of the OOM issue here, triage feels this isn't a blocker, as this is likely an issue with using Flame on 273 MB (not enough memory to use the site) & is not a regression.

Comment 11

[Kartikaya Gupta (email:[e-mail])]

(In reply to Jason Smith [:jsmith] from comment #10)
> but
> the non-functional buttons is a regression. Can you open a separate bug for
> the non-functional button issue?

According to comment 8 the non-functional buttons is no longer happening. That being said, please do file a separate bug if you still see that problem.

Comment 12

[KTucker [:KTucker][Inactive 3/4/2016]]

I was able to reproduce the non-functional buttons and lockscreen issue on the 7/21/2014 Flame 2.0(273mb) build.

I will write this up as a separate issue although the steps to reproduce are the same. This happened after reproducing the OOM issue about 7 times. The non-functional buttons issue seems to have a low repro rate overall but I'm going to try and get it down 100%.

Environmental Variables
Device: Flame v 2.0(273mb)
Build ID: 20140721000201
Gecko: https://hg.mozilla.org/releases/mozilla-aurora/rev/4bd4b0ae7bbe
Gaia: 8cb1a949f2e9650bb2c5598e78a6f24a58bbaf97
Platform Version: 32.0a2
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 13

[KTucker [:KTucker][Inactive 3/4/2016]]

The non-functional buttons issue has been logged in bug 1042349

Comment 14

[:Eli Perelman]

FxOS Perf Triage: With the 319MB Flame being the reference for low-memory devices, and this issue does not replicate on the 319MB Flame based on comment 8. Closing as wontfix.