1050515 - Contacts becomes unusable when tapping settings repeatedly

Status: RESOLVED DUPLICATE of bug 1038815

(Firefox OS Graveyard :: Gaia::Contacts, defect, P1)

Description

[Fred Muyumba [:FredM]]

Attachment: Contacts Issue.txt

Description:
Repeated double-tapping on "Settings" icon renders the "Contacts" App unusable due to an Oom


Repro Steps:
1) Update a Flame to 20140807000201
2) Tap on "Contacts" 
3) Double-tap "Settings" 
4) Repeat step 3


Actual:
The App gets a white screen when the "Settings" icon is double-tapped repeatedly 


Expected:
Under Oom, App should continue being usable

Environmental Variables:
Device: Flame 2.0 319mb
Build ID: 20140807000201
Gaia: 8cc28fd31905a0ea2b2e15d13e80a0eab2feb1ba
Gecko: 25980b5120b0
Version: 32.0 (2.0)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0


Keywords: Contacts, Oom, Blank screen, Settings, Gear, Lmk, Crash, White



Repro frequency: 100%

See attached: video clip, logcat http://youtu.be/mKqRl9TO6Ag

Comment 1

[Fred Muyumba [:FredM]]

This issue DOES reproduce on Flame 2.1 319mb, Buri 2.1, Flame 2.0 512mb and Buri 2.0

When tapped repeatedly, the "Contacts" App turns into a white screen. This is due to Oom

Environmental Variables:
Device: Flame Master 319mb
Build ID: 20140807040201
Gaia: 079c5f85875b0f2eb341ca9fd375f1b905ed7157
Gecko: afcb3af79d09
Version: 34.0a1 (Master)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0


Environmental Variables:
Device: Buri Master
BuildID: 20140807040201
Gaia: 079c5f85875b0f2eb341ca9fd375f1b905ed7157
Gecko: afcb3af79d09
Version: 34.0a1 (2.1)
Firmware: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.


Enviromental Variables:
Device: Flame 2.0 512mb
BuildID: 20140807000201
Gaia: 8cc28fd31905a0ea2b2e15d13e80a0eab2feb1ba
Gecko: 25980b5120b0
Version: 32.0 (2.0)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0


Enviromental Variables:
Device: Buri 2.0
BuildID: 20140807063003
Gaia: 9d681c6a3b69af2d76e7e00c31bc57e0c3efb6b9
Gecko: ca7386df2e91
Version: 32.0 (2.0)
Firmware: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0




This issue DOES NOT reproduce on Flame 1.4319mb, Buri 1.4 and Buri 1.3  

When tapped repeatedly, the "Contacts" App DOES NOT close due to Oom


Environmental Variables:
Device: Flame 1.4 319mb
Build ID: 20140806183051
Gaia: e9dce1f60f729e228810f751417681b5ff937b6b
Gecko: 89a8a24a8b1b
Version: 30.0 (1.4)
Firmware Version: v123turn into a white screen
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0


Enviromental Variables:
Device: Buri 1.4
BuildID: 20140806183051
Gaia: e9dce1f60f729e228810f751417681b5ff937b6b
Gecko: 89a8a24a8b1b
Version: 30.0 (1.4)
Firmware: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0


Environmental Variables:
Device: Buri 1.3
BuildID: 20140807024001
Gaia: 23f55be856cef53c6604a6fe4aeb09061afbc897
Gecko: 9727017eabb9
Version: 28.0 (1.3)
Firmware: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:28.0) Gecko/28.0 Firefox/28.0

Comment 2

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

Please attach a dmesg log.

Comment 3

[Fred Muyumba [:FredM]]

Attachment: dmsg.txt

Comment 4

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

[Blocking Requested - why for this release]:

I can see this impacting a lot of end users. It is a regression too so nominating 2.0?

Comment 5

[Dietrich Ayala (:dietrich)]

Triage group concludes this is not a shippable state, blocking+.

Comment 6

[Mason Chang [Inactive] [:mchang]]

Triage:

Comment 7

[Mason Chang [Inactive] [:mchang]]

Triage: David, can you please have someone look into this who is familiar with the contacts app? Thanks!

Comment 8

[Chris Kreinbring [:CKreinbring]]

Note: This bug had highly variable repro rates, leading to windows where it turned out that the supposed last working build was actually reproing the bug.

Regression window
Last working
BuildID: 20140604142816
Gaia: a38a6a5c6fabc97dd16d5360632b5ac5c7e06241
Gecko: 951e3a671279
Platform Version: 32.0a1
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

First broken
BuildID: 20140604173717
Gaia: d2cfef555dabab415085e548ed44c48a99be5c32
Gecko: 2ebadbba6cc8
Platform Version: 32.0a1
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Working Gaia / Broken Gecko = No repro
Gaia: a38a6a5c6fabc97dd16d5360632b5ac5c7e06241
Gecko: 2ebadbba6cc8
Broken Gaia / Working Gecko = Repro
Gaia: d2cfef555dabab415085e548ed44c48a99be5c32
Gecko: 951e3a671279
Gaia push log: https://github.com/mozilla-b2g/gaia/compare/a38a6a5c6fabc97dd16d5360632b5ac5c7e06241...d2cfef555dabab415085e548ed44c48a99be5c32


B2G-inbound
Last working
BuildID: 20140604084216
Gaia: 2a4c7becdb141d2601e47a040a27eebe52a8db79
Gecko: fd5bb34861d6
Platform Version: 32.0a1
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

First broken
BuildID: 20140604105916
Gaia: 18e2e8dc2d9ff19cd1210026367c14956d04eb0d
Gecko: c36c5f011229
Platform Version: 32.0a1
Firmware Version: V123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Working Gaia / Broken Gecko = No repro
Gaia: 2a4c7becdb141d2601e47a040a27eebe52a8db79
Gecko: c36c5f011229
Broken Gaia / Working Gecko = Repro
Gaia: 18e2e8dc2d9ff19cd1210026367c14956d04eb0d
Gecko: fd5bb34861d6
Gaia pushlog: https://github.com/mozilla-b2g/gaia/compare/2a4c7becdb141d2601e47a040a27eebe52a8db79...18e2e8dc2d9ff19cd1210026367c14956d04eb0d

Comment 9

[Joshua Mitchell (Inactive)]

This window is the Vertical homescreen split (where the first V Homescreen is the 'first broken') - I don't think there is anything from this pushlog to nominate as the regressing bug as this issue seems similar to many of the 256 mem bugs where the V. Homescreen was indicated in the regression-window because of the jump in memory usage causing other apps or programs to be more likely to OOM.

Comment 10

[Kevin Grandon :kgrandon]

Does pressing the home button after this state do anything? We may want to re-verify that this is still a problem after bug 1047645 landed. It could be the same issue.

Comment 11

[Jason Smith [:jsmith]]

QA Wanted for a retest since bug 1047645 landed.

Comment 12

[Joshua Mitchell (Inactive)]

Issue DOES still reproduce on the latest 2.0

Actual Results: The App gets a white screen when the "Settings" icon is double-tapped repeatedly, pressing the HOME button returns the user to the homescreen. Long pressing the home button the Contacts card is seen with an all-white screen. Returning to it returns the user to the all white screen. 

Device: Flame 2.0
Build ID: 20140818095113
Gaia: 1a215917df01bb815811f33665bd3fdca4130708
Gecko: ceb9b2aa1f14
Version: 32.0 (2.0)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Comment 13

[bhavana bajaj [:bajaj]]

moving the NI from david to rik, given this is a blocker and needs help.

Comment 14

[Thinker Li [:sinker]]

It is very weird to have a lot of channel error message in the log.

Comment 15

[Cervantes Yu [:cyu] [:cervantes]]

It's strange that from dmesg there is no sign of OOM killing, and we only see repeated IPC channel errors observed on the parent side. Need to reproduce this locally to see what's going on.

Comment 16

[Anthony Ricaud (:rik)]

Moving in the appropriate component.

Francisco: Can you take a look please?

Comment 17

[Francisco Jordano [:arcturus] [:francisco]]

I don't think this is a bug related to Oom, but a race condition on the contacts navigation code.

We already opened a bug (even have a patch), for this problem, let me just try to find it.

Comment 18

[Francisco Jordano [:arcturus] [:francisco]]

I think this could be a duplicated of bug 1038815

Comment 19

[Francisco Jordano [:arcturus] [:francisco]]

This bug has already a patch, but wasn't merged since it doesnt contain tests, Sergi was working on it and will add the tests for landing it.

Comment 20

[Cervantes Yu [:cyu] [:cervantes]]

It's highly likely. I just reproduced this on a memory-rich flame (1GB memory) and there is no sign of OOM kill.