1080632 - [Dialer] Blue screen shown when dialing a number from the Contacts app

Status: VERIFIED FIXED

(Firefox OS Graveyard :: Gaia::Dialer, defect)

Description

[Marcia Knous [:marcia]]

Attachment: Dialer while making a call from contacts app

Flame, while running:

Gaia   7e2ef41d3ac98757acaf490b5413fb42061ad3e6
SourceStamp 75ebb70f8b38
BuildID 20141009000203
Version 34.0a2
Base image: v184

STR:
1. From Contacts App Press the Telephone Icon next to the contact name

Expected: Dialer is shown
Actual: Blue screen is shown

Repro 2/2 during testing. Unfortunately no logcat yet but will get one.

Comment 1

[Marcia Knous [:marcia]]

Attachment: Logcat during Blue Screen

Comment 2

[Marcia Knous [:marcia]]

[Blocking Requested - why for this release]: Visible regression - dialer app should show when you are dialing a contact.

Comment 3

[Marcia Knous [:marcia]]

The device that I was seeing this on has 319 MB RAM.

Comment 5

[Marcia Knous [:marcia]]

Joshua: This is not a dupe of the but you have in Comment 4 - at no time was my phone asleep when this is happening. I believe it is different than the bug you filed yesterday.

Comment 6

[Joshua Mitchell (Inactive)]

[Blocking Requested - why for this release]: Restoring Keywords / blocking flag from comment 2

Comment 7

[Marcia Knous [:marcia]]

I see this happening while I am in an active call as well.

Comment 8

[Doug Sherk (:drs) (inactive)]

With identical setups, Francisco and I can't repro this. qawanted to see if others can.

Comment 9

[Chris Kreinbring [:CKreinbring]]

I am unable to repro the bug using the reporter's build in both shallow and full flash.  I've attempted creating a new contact and importing from various sources.  Tested in v180 and v184.

Comment 10

[Doug Sherk (:drs) (inactive)]

Marcia, can you provide any additional info that you think may be helpful here?

Comment 11

[Joshua Mitchell (Inactive)]

Let's change this to a Steps-Wanted tag then, and continue to explore it

However - without reliable repro steps it is not standard to keep a blocking flag

Comment 12

[Marcia Knous [:marcia]]

(In reply to Doug Sherk (:drs) from comment #10)
> Marcia, can you provide any additional info that you think may be helpful
> here?

I will try - Johan Lorenzo was seeing this intermittently as well. Also in the ST report it was noted that the phone is needing to be rebooted as a result of this.

I have seen it numerous times this morning, always when either on an active call or trying to dial a number.

Comment 13

[Marcia Knous [:marcia]]

Video of issue in action: http://youtu.be/hwm0JcLw5-s

Note that there is recoverable state here - hitting the home button shows me the Active Call status bar at the top, and then the dialer UI will draw.

Comment 14

[Marcia Knous [:marcia]]

Other information:

(1) This device is running today's build which was OTA'd from yesterday's 2.1 build.
(2) The device only has one contact which is a also a favorite

Comment 15

[Marcia Knous [:marcia]]

Also, in case it helps I have the Developer Tools setting turned on to "ADB and Devtools." I know there have been other bugs which have mentioned that having this pref'd on consumes resources.

Comment 16

[Doug Sherk (:drs) (inactive)]

Since we don't have steps yet, I'd like to take a shot in the dark and ask if this can still be repro'd with bug 1076597 now fixed.

Comment 17

[Doug Sherk (:drs) (inactive)]

KTucker pointed out that this may still be a dupe of bug 1080254. Note that the STR in bug 1080254 have been refined since this bug was reopened. I think there's a strong possibility of this being a dupe, but we don't have enough evidence to mark it as such yet.

Knowing what branches are affected by this would be a helpful, but not certain, tell. I'm dropping qawanted for now as I'm less confident in what I said in comment 16 after reading bug 1080254.

Comment 18

[Johan Lorenzo [:jlorenzo]]

Comms triage: This bug prevent a user to make or receive any phone call until he restarts the phone. Even though, we need to find the actual STR, we can't ship a release with that bug.

Comment 19

[Johan Lorenzo [:jlorenzo]]

Like Marcia said and like I said in the comms triage, I was able to repro the issue many times yesterday.

I still don't know the exact STR but once you've got this blue screen, you can't make or receive any phone call until you restart the phone. Now that my phone has restarted, I'm not able to get in the same state as Marcia and I were yesterday.

I'll try to repro this issue during the day. I'll keep you noticed.

Comment 20

[Johan Lorenzo [:jlorenzo]]

I found a way to trigger the blue screen (5/6 times).

1. Close all apps
2. Receive a phone call on the DuT but don't answer it.
3. With the other phone, hang up.
4. On the DuT, tap the notification of the missed call.
5. Press home button.
6. Go to Contacts, add a new contact with a name and a phone number.
7. In the meantime, with the other phone, call the DuT.
8. On the DuT, continue to add you contact. When the keyboard disappear, keep tapping on the screen.
9. Now you see the "BSOD" ;) 

See this video for details: http://mzl.la/1C04nv0 (Don't mind the Buri, it's not up to date).

I'll attach the logcat and I'll do the branch check.

Comment 21

[Johan Lorenzo [:jlorenzo]]

Attachment: Logcat when blue screen is triggered - Gaia debug traces enabled

Comment 22

[Anthony Ricaud (:rik)]

That doesn't sound like Dialer at all then :)

I think the blue screen is the color of the app-window from system. So that would indicate that Contacts has crashed and somehow, we don't go back to Homescreen.

Comment 23

[Johan Lorenzo [:jlorenzo]]

I am not able to reproduce neither 2.0 or 2.2 (0/5 times each). It seems like the dialer appears faster than 2.1 in both versions.
Gaia-Rev        c1f60895e5bcc6a951f3667c2a1e1bd39d393420
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-b2g32_v2_0/rev/4540201b5da0
Build-ID        20141009160206
Version         32.0
Device-Name     flame-kk
FW-Release      4.4.2
FW-Incremental  34
FW-Date         Tue Sep 30 14:06:36 CST 2014
Bootloader      L1TC00011840

Gaia-Rev        7b92615bdc97e5c675cd385ec68bc5e47e0c5288
Gecko-Rev       https://hg.mozilla.org/mozilla-central/rev/f0bb13ef0ee4
Build-ID        20141009160202
Version         35.0a1
Device-Name     flame-kk
FW-Release      4.4.2
FW-Incremental  34
FW-Date         Tue Sep 30 14:06:36 CST 2014
Bootloader      L1TC00011840


I was curious if I could repro (on 2.1) on a newer build than comment 0 and I can't repro anymore (0/5 times):
Gaia-Rev        bc8eb493311c58f1f311a56b8b645b52bfbd2f71
Gecko-Rev       https://hg.mozilla.org/releases/mozilla-aurora/rev/72c13d8631ff
Build-ID        20141010000201
Version         34.0a2
Device-Name     flame-kk
FW-Release      4.4.2
FW-Incremental  34
FW-Date         Tue Sep 30 14:06:36 CST 2014
Bootloader      L1TC00011840


Hence, this looks like a perf issue on that particular build. Doug, can you tell if it is regarding the logcat?

Comment 24

[Doug Sherk (:drs) (inactive)]

Based on the STR, bug 1080362 being fixed now, and this no longer being reproable.

Comment 25

[Tony Chung [:tchung]]

Even though this is a marked dupe, please also verifyme on 2.1 this bug is fixed as a result of bug 1080362.  This bug has a completely different STR than that bug, so we need to verify this fix really does affect it properly.   ni? kevin, but also marcia to check since she was able to reproduce originally.

Comment 26

[Adam Alldredge [:AdamA][Inactive]]

The issue is verified fixed in Flame 2.1.

Flame 2.1 KK (319mb) (Full Flash)

Environmental Variables:
Device: Flame 2.1
BuildID: 20141010000201
Gaia: bc8eb493311c58f1f311a56b8b645b52bfbd2f71
Gecko: 72c13d8631ff
Gonk: 52c909e821d107d414f851e267dedcd7aae2cebf
Version: 34.0a2 (2.1)
Firmware: V180
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

I checked this issue using the steps from the description, Comment 13, Comment 14, Comment 15, and Comment 20. I was unable to get the blue screen appear.