Closed Bug 1164472 Opened 9 years ago Closed 9 years ago

Dialer crashes after making a call

Categories

(Firefox OS Graveyard :: RIL, defect)

ARM
Gonk (Firefox OS)
defect
Not set
major

Tracking

(blocking-b2g:2.5+, b2g-master verified)

VERIFIED FIXED
2.2 S12 (15may)
blocking-b2g 2.5+
Tracking Status
b2g-master --- verified

People

(Reporter: gsvelto, Assigned: bhsu)

References

Details

(4 keywords)

Crash Data

+++ This bug was initially created as a clone of Bug #1147736 +++

STR:

1. Launch the dialer
2. Type a number
3. Call it

Result: the dialer crashes, once you close the callscreen you'll find yourself with the crashreporter dialer. Note that re-launching the dialer during the call makes it crash again right away.

I've bisected this down to bug 1147736, unfortunately I didn't have time to check what's wrong with that exactly. Backing out the entire patch-set fixes the issue so suggest backing out if a solution cannot be found quickly as the result is quite bad for people dogfooding on master.

Note, I've seen this happen both on a device and on the emulator.
CC'ing other dialer peers so they're aware of this issue.
Here's the crash report for the bug:

https://crash-stats.mozilla.com/report/index/0de636bd-39df-49bd-a325-aeea92150513

Environmental Variables:
Device: Flame 3.0 (KK, 319mb, full flash)
Build ID: 20150513010202
Gaia: 0d6c04f13fd385bda045f4e539b2a67cb5d84b1d
Gecko: 62d9b117c688
Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67
Version: 41.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Crash Signature: [@ mozalloc_abort(char const*) | NS_DebugBreak | mozilla::ipc::FatalError(char const*, char const*, int, bool) | mozilla::dom::telephony::PTelephonyChild::OnMessageReceived(IPC::Message const&)]
[Blocking Requested - why for this release]: Smoketest blocker
blocking-b2g: --- → spark?
Keywords: crash, reproducible
blocking-b2g: spark? → spark+
Marking fixed by backout.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
This issue is Verified Fixed in the latest Flame 3.0 build.
Dialer remains performant when dialing and accepting calls.

Environmental Variables:
Device: Flame 3.0
Build ID: 20150515010201
Gaia: 8897e1810aa6426ca483269af76ce2bfd2029d25
Gecko: 25c5525a1000
Gonk: 040bb1e9ac8a5b6dd756fdd696aa37a8868b5c67
Version: 41.0a1 (3.0)
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Status: RESOLVED → VERIFIED
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(pbylenga)
blocking-b2g: spark+ → 2.5+
Assignee: nobody → bhsu
Target Milestone: --- → 2.2 S12 (15may)
Moving the bug to the component where the regression came from.
Component: Gaia::Dialer → RIL
You need to log in before you can comment on or make changes to this bug.