1071607 - [Dialer] Intermittent -- second call incorrectly dropped when 1 party dropped from conf call

Status: RESOLVED WONTFIX

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

Description

[Tamara Hills [:thills]]

Attachment: D is dropped.txt

Observed behavior: when user has one conf call + one other call and one party of the conf call hangs up, the other call is intermittently dropped.

A = Flame user, B, C, D are other PSTN/mobile/voip phones.  

STR:
1.  A calls B and answers
2.  C calls A and A answers, holding B
3.  A merges B, C into a Conf call
4.  D calls A and A answers (putting conf call on hold)
5.  background the app.  
6.  B hangs up (I'm not 100% about this, but I had better luck repro'ing while the banner is still there saying that you have a call... this eventually goes away and you're left with the slim notification bar)
7.  A few seconds later D drops (this is intermittent).
8.  Swipe and unswipe the notification bar to check that C is still connected
9.  Hang Up C.  At this point I once had a total freeze of the device.

Comment 1

[Tamara Hills [:thills]]

Attachment: phone freeze settings error.txt.zip

This is the log from when I had the device freeze.  This is the main error that is repeated:

E/GeckoConsole(15288): [JavaScript Error: "Settings lock trying to run more tasks after finalizing. Ignoring tasks, but this is bad. Lock: {978d2834-d180-4eb6-9881-c1fcedf01575}" {file: "resource://gre/modules/SettingsRequestManager.jsm" line: 583}]

Comment 2

[Tamara Hills [:thills]]

Hi Kyle, 

I ran into this a couple times where the device would freeze up.  Once, I was able to capture the logcat from it.  It's fairly intermittent, but thought we would check with you to see if there is something we should look for in the way we are using the settings which could be causing this type of error.

Thanks,

-tamara

Comment 3

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

Ok. Definitely something wrong with the settings API again. Not sure how we're getting into this state though. Will investigate.

In the meantime, do you have a build version for the gecko/gaia you were using?

Comment 4

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

Build info (IRC):

Build Identifier: 20140918160202
Gaia Hash: 4baea43

Comment 5

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

Requesting QA repro, as I don't have the ability to test this (not enough phone lines). Also need to see if it's happening on v2.1 (I would assume it is)

Comment 6

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

Any luck on reproing this yet?

Comment 7

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

In response to comment 6, we are checking this now on 2.1. What branch was this originally found on?

Comment 8

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

Was originally found on master as far as I know.

Comment 9

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

Did this ever get repro'd/qawanted'd?

Comment 10

[Tamara Hills [:thills]]

Hi Kyle,

I can no longer repro this issue.  I'm marking it as works for me.  

Thanks,

-tamara

Comment 11

[Duane Dixon [:ddixon]]

This issue was reproduced. Repro Rate: 3/7

Device "D" was dropped from the conference call and user was presented with an error message. 

Attaching logcat and screenshot (from device "D"). 

Test devices used: 
Device A = Flame 2.2 Device B = Open C on 2.2 Device C = Android Device D = Flame 2.2

Environmental variables from Device "D": 
Device: Flame 2.2 (shallow flash, engineering, 319 MB memory)
BuildID: 20141204080450
Gaia: 0462090a99093049add9268d14cbc7e44c1d1ccb
Gecko: 29d086b32a26
Version: 37.0a1 (2.2)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:37.0) Gecko/37.0 Firefox/37.0

NOTE: Step 9 (listed in Comment 0) did not repro.  Device "A" did not freeze after call was dropped.

Comment 12

[Duane Dixon [:ddixon]]

Attachment: conference_drop_logcat

Comment 13

[Duane Dixon [:ddixon]]

Attachment: drop_call_error.png

Comment 14

[Duane Dixon [:ddixon]]

This issue was also reproduced on the latest Flame 2.1 (shallow flash, engineering, 319 MB memory). 

Repro Rate: 2/5 

Device: Flame 2.1
BuildID: 20141204133046
Gaia: 38e17b0219cbc50a4ad6f51101898f89e513a552
Gecko: 8b92c4b8f59a
Version: 34.0 (2.1)
Firmware: V188-1
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0

Attaching logcat: "call_drop_2.1_logcat"

Comment 15

[Duane Dixon [:ddixon]]

Attachment: call_drop_2.1_logcat

Comment 16

[Tamara Hills [:thills]]

Hi Duane,

Do you think you can get a complete log?  From the log you posted, it does not look like a settings issue anymore.  I don't see the "Settings Lock" error that I posted in Comment 1.

Thanks,

-tamara

Comment 17

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

Wow, looks like something going wrong with the termination of the callscreen app (which is what would've caused the error in Comment 1 but we fixed that in settings since that comment was posted). There's just a whole cascade of errors there, reminiscent of some of the issues we were also having that spawned things like bug 1078448. I'm unassigning from myself at the moment, but will stay on CC. We should probably find someone on dialer/communications to start looking at this.

Comment 18

[Joshua Mitchell (Inactive)]

Johan? You own Dialer - can you find someone to look into this?

Comment 19

[Johan Lorenzo [:jlorenzo]]

After 10 tries, I am unable to reproduce this issue on the current master. I saw Tamara reproducing it during the workweek though.

This bug might be carrier-dependent. Somebody with AT&T/T-Mobile SIM cards might help us to point out the issue and get a logcat.

Comment 20

[Armen [:armenzg]]

Closing all intermittent test failures for Firefox OS (since we're not focusing on it anymore).

Please reopen if my search included your bug by mistake.

Comment 21

[BMO Automation]

Firefox OS is not being worked on