Closed Bug 1218600 Opened 4 years ago Closed 4 years ago

crash in libxul.so@0xe7bbdc | libxul.so@0x6b3095 | libxul.so@0x8ec97b | libxul.so@0x8ec9c7 | libxul.so@0x6d78ef | libxul.so@0x6dfbf9 | libxul.so@0x6e210f | libxul.so@0x937dc9 | libxul.so@0xe7bb5b | libxul.so@0x411f31 | libxul.so@0x6e1cc1 | libxul.so@0x...

Categories

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

ARM
Gonk (Firefox OS)
defect

Tracking

(b2g-v2.5 affected, b2g-master affected)

RESOLVED WORKSFORME
Tracking Status
b2g-v2.5 --- affected
b2g-master --- affected

People

(Reporter: AdamA, Unassigned)

References

()

Details

(Keywords: crash, Whiteboard: [2.5-Daily-Testing][Spark])

Crash Data

Attachments

(1 file)

Attached file logcat
This bug was filed from the Socorro interface and is 
report bp-49273054-0e2f-4c43-be03-2b90a2151026.
=============================================================

Summary (title) Field:
Dialer will crash when going to call log after FOTA/Sideload with a large call log

Description:
If the user has a large call log and FOTA/Sideloads to the latest base the dialer will crash.

Repro Steps:
1) Flash the flame to the V4 base build
2) Create a large call log by pushing a profile or making over 100 calls to unique numbers
3) Update a Flame to 20151022144730 - Base V5
4) Open dialer
5) Select call log
6) Observe Crash

Actual:
The phone crashes when viewing call log

Expected:
It is expected that the phone does not crash

Environmental Variables:
Device: Flame 2.5 [FOTA-Sideload]
Build ID: 20151022144730
Gaia: 32d827a70af90a05918f234e5b16b35d5d2a07e8
Gecko: 894a28d90bcdf0c845b9c47d4a36fc6e0815d2b1
Gonk: 205ac4204bbbb2098a8046444acba551ba5dc75a
Version: 44.0a1 (2.5)
Firmware Version: v18D
User Agent: Mozilla/5.0 (Mobile; rv:44.0) Gecko/44.0 Firefox/44.0

Repro frequency: 10/10
Link to failed test case: https://moztrap.mozilla.org/manage/case/14042/
See attached: video clip(https://youtu.be/zU3svxrroWQ), logcat
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
We've had crashes related to IndexedDB lately when using reference workloads in the call log (see bug 1214222); this might be related.
See Also: → 1214222
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage?][flame-blocker]
Whiteboard: [2.5-Daily-Testing][Spark][dogfood-blocker] → [2.5-Daily-Testing][Spark]
Thanks Gabriele; I've moved it from dogfood blocking as it may have something to do with the script.  If that could be fixed, it would be wonderful.
QA Whiteboard: [QAnalyst-Triage?][flame-blocker] → [QAnalyst-Triage+][flame-blocker]
Flags: needinfo?(ktucker)
OS: Android → Gonk (Firefox OS)
Priority: -- → P1
Hardware: Unspecified → ARM
Crash is related to the database being populated incorrectly.  Closing as WFM.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.