Closed
Bug 1071886
Opened 11 years ago
Closed 8 years ago
crash in libxul.so@0x5a9f7c | libxul.so@0x5a9f8f | libxul.so@0x391d5b | libxul.so@0x3920e1 | libxul.so@0x34bea5 | libxul.so@0x356081 | libnss3.so@0xf9fb9
Categories
(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)
Tracking
(b2g-v2.1 affected)
RESOLVED
WONTFIX
| Tracking | Status | |
|---|---|---|
| b2g-v2.1 | --- | affected |
People
(Reporter: smiko, Unassigned)
Details
(Keywords: crash, Whiteboard: [2.1-exploratory-2][b2g-crash])
Crash Data
This bug was filed from the Socorro interface and is
report bp-6fc367a2-c066-4995-ab65-f1b852140923.
=============================================================
STR:
1: Install and launch Cut the Rope via Wi-fi
2: Set in game language to German and turn off in-game music
3: Get into gameplay.
3: Send a Msg to the DUT from another device
4: Click on the notification to open the Msg.
5: Relaunch Cut the Rope and return to gameplay
6: Use two fingers to simultaneously swipe, stressing out the device.
7: Press Home button to exit app.
Repro Rate: 1/10
Environmental Variables
Flame 2.1(KK base/319mb)
Environmental Variables:
Device: Flame 2.1 (319mb)
Build ID: 20140923003005
Gaia: 3742913e11f69e789dcb0aa0dedf2e5572da0129
Gecko: df42b05782aa
Version: 34.0a2
Firmware Version:
User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
| Reporter | ||
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-v2.1:
--- → affected
Flags: needinfo?(dharris)
Whiteboard: [2.1-exploratory-2]
Updated•11 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(dharris)
Updated•11 years ago
|
Whiteboard: [2.1-exploratory-2] → [2.1-exploratory-2][b2g-crash]
Comment 1•11 years ago
|
||
Kairo, do you know if this is a top crasher or not for b2g?
Flags: needinfo?(kairo)
Comment 2•11 years ago
|
||
(In reply to Tony Chung [:tchung] from comment #1)
> Kairo, do you know if this is a top crasher or not for b2g?
For signatures like this it's hard to tell as all the frames are unsymbolized and therefore changing with every build, and a lot of different crashes can give the same pattern of signature. There are a number of signatures like this around in https://crash-analysis.mozilla.com/rkaiser/2014-10-01/2014-10-01.b2g.topcrashes.weekly.html but it's hard to tell which ones are this same issue and how they would sum up to a topcrash or not.
Flags: needinfo?(kairo)
Comment 3•8 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•