Closed Bug 1031355 Opened 11 years ago Closed 11 years ago

crash in eglsubAndroid.so@0x4046

Categories

(Core :: Graphics, defect)

32 Branch
ARM
Gonk (Firefox OS)
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME
tracking-b2g backlog
Tracking Status
b2g-v2.0 --- affected

People

(Reporter: astole, Unassigned, NeedInfo)

References

Details

(Keywords: crash, Whiteboard: [b2g-crash])

Crash Data

Attachments

(1 file)

Attached file logcat
This bug was filed from the Socorro interface and is report bp-9e932c17-5544-476b-97f2-08df72140627. ============================================================= Description: Device crashed after unlocking the screen and opening the Dialer app. No exact repro steps since the crash only occurred once. One note is that a message was sent before the phone fell asleep, once it was unlocked and the Dialer app was tapped on, it crashed. 2.0 Environmental Variables: Device: Flame 2.0 BuildID: 20140627000201 Gaia: 8df02268fcd7e80c5fab8c1ec099772e37f8659d Gecko: 731a5e8831e6 Version: 32.0a2 Firmware Version: v122 Repro frequency: 10% See attached: logcat
Adding qawanted for repro steps.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA-Wanted - Repro steps and verify repro rate
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
blocking-b2g: --- → backlog
Component: Gaia::Dialer → Graphics
Keywords: qawanted
Product: Firefox OS → Core
Version: unspecified → 32 Branch
Whiteboard: [b2g-crash]
Attempted repro for a little over two hours, was unable to reproduce.
http://bit.ly/1kbc88Y - looks as if this has been hit about 7 times in the last week.
Blocks: MTBF-B2G
(In reply to Eric Kramer (Kramer) from comment #3) > Attempted repro for a little over two hours, was unable to reproduce. Dupe of this bug makes it clear this is going to be hard to reduce STR on.
Keywords: steps-wanted
(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #5) > This might be fixed by Bug 1031553. If we reproduce this again post landing of that patch on 2.0, then feel free to nominate this bug as a MTBF blocker.
I was able to repro this crash while trying to repro bug 1030803. It was on an older build so my next step is to try and repro this in a recent build. The STR I'll be working with are as follows. 1. Launch Browser 2. Load https://etherpad.mozilla.org/ 3. Select 'Create new public pad' 4. Zoom in and out and scroll aggressively. (as fast as possible) Environmental Variables: Device: Flame Master Build ID: 20140522193023 Gaia: b61129780e085636d09406f2a46e922d0f8b9757 Gecko: e9b2b72f4e6c Version: 32.0a1 (Master) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
Update - I have not been able to crash this on the latest master I have gotten 3 'Well this is embarrassing" error messages and 5 device reboots; but have not gotten it to crash with a crash report to verify that THIS bug still repros.
Is the STR in comment 9 reproducible on the build as filed in comment 0?
Keywords: qawanted
(In reply to Jason Smith [:jsmith] from comment #11) > Is the STR in comment 9 reproducible on the build as filed in comment 0? Using the steps from comment 9, in the build from comment 0, I was able to get the 'Well this is embarrassing' error 4 times and the device reboot once I was not able to get the crash w/ report.
I was unable to reproduce this crash on the original build or the latest master build with the steps from comment 9. On the original build, I could get the phone to restart without a crash report within 30 seconds of starting, same as Joshua did. On the latest Master, I could not get the restart to occur just the "Well this is embarassing" error. Leaving the qawanted tag so others can check. Environmental Variables: Device: Flame Master BuildID: 20140804131526 Gaia: 19bf9795263e2ccc15d824a52ebf23c2670fa9b9 Gecko: 7f81be7db528 Version: 34.0a1 (Master) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Flags: needinfo?(jmitchell)
Unable to reproduce the crash using either of these methods described with the dialer or Etherpad. Have been working a couple hours on this with no luck other than a couple "This is embarrassing" errors. Builds used below: Environmental Variables: Device: Flame Master BuildID: 20140814005107 Gaia: 5e074831f9ddacdf6f622a6dffaecb626f740be8 Gecko: 5299864050ee Version: 34.0a1 (Master) Firmware Version: v123 ---------------------------------------------- Environmental Variables: Device: Flame 2.0 BuildID: 20140814084205 Gaia: 2b42351cbc8f652b1cbafb76768386546d752204 Gecko: 78858046e786 Version: 32.0 (2.0) Firmware Version: v123
Flags: needinfo?(jmitchell)
Flags: needinfo?(jmitchell)
QA Whiteboard: [QAnalyst-Triage?]
We've made multiple attempts to find STR here, but we're not successful. If we get new information that could imply a hint of STR here, then let's re-add the QA keyword.
Keywords: qawanted
Hi, Andrew, Any updates or reproduction of this bug? I need more information so that I can try to reproduce or deal with this bug. Or, is it too old to track? Should I close it as worksforme now?
Flags: needinfo?(astole)
Andrew is no longer here - According to the crash reports this has not been seen in the last 28 days, in addition to multiple no-repro's let's close it as WFM
Status: NEW → RESOLVED
Closed: 11 years ago
QA Whiteboard: [QAnalyst-Triage+]
Resolution: --- → WORKSFORME
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: