1047559 - crash in mozalloc_abort(char const*) | NS_DebugBreak | mozilla::dom::PContent::Transition(mozilla::dom::PContent::State, mozilla::ipc::Trigger, mozilla::dom::PContent::State*)

Status: RESOLVED WORKSFORME

(Core :: DOM: Content Processes, defect)

Description

[Martin Shuman [:Marty]]

This bug was filed from the Socorro interface and is 
report bp-86aed73f-f6b2-4d92-9b1b-1b8b32140801.
=============================================================

Description:
A second phone called the DTU while the DTU was locked.  While the DTU was ringing, the call was terminated, and the DTU crashed.  The DTU did not have any direct input from the user.

This occurred on the first missed call received since flashing the build, but not again on any subsequent missed calls.


Repro Steps:
1) Update a Flame to 20140801040326
2) Call the DTU from another phone.
3) Have the other phone hang up while the DTU is ringing.


Actual:
DTU crashed and restarted.


Expected:
Phone does not crash.

Environmental Variables:
Device: Flame Master
Build ID: 20140801040326
Gaia: 04ea7e1a4034a50d4a7a4f5b95a04a2ed8313908
Gecko: 104254bd1fc8
Version: 34.0a1 (Master)
Firmware Version: v123
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0


Keywords:  Missed Call, Crash, Lock Screen

Repro frequency: 1/7

Comment 1

[Martin Shuman [:Marty]]

This crash was encountered on a Flame device set to 319MB memory.  Adding the appropriate whiteboard tag.

Comment 2

[Cody Roesch [:croesch]]

With the reporters build I was able to reproduce this bug with Flame set to 512mb.

Environmental Variables:
Device: Flame Master
Build ID: 20140801040326
Gaia: 04ea7e1a4034a50d4a7a4f5b95a04a2ed8313908
Gecko: 104254bd1fc8
Version: 34.0a1 (Master)
Firmware Version: v123

STR
1. Flash to the build listed above.
2. Lock the DUT so that the screen is black.
3. Call the DUT with a second device.
4. As soon as the DUT starts to ring, hang up the call with the second device.
5. DUT will Crash and Reboot.

Was able to repro this 4/5 times simply repeating steps 2-5. No need to reflash.

Comment 3

[Cody Roesch [:croesch]]

I am UNABLE to reproduce this crash on the latest 2.1 Flame build.

Repro: 0/10 

Environmental Variables:
Device: Flame Master
BuildID: 20140805124418
Gaia: d85bbae28dd9ab9679b42d8d37c84810059e097c
Gecko: 191e834ff32b
Version: 34.0a1 (Master) 
Firmware Version: v123

Comment 4

[Joshua Mitchell (Inactive)]

Jason - comment 2 has reproducible steps and using them the tester has found this issue to NOT reproduce in the latest 2.1

I'd like to close this as Works-for-Me 
or
Resolved-Fixed - (by new firmware / base)

Comment 5

[Jason Smith [:jsmith]]

sgtm