Closed Bug 782223 Opened 12 years ago Closed 7 years ago

crash in NvGl214081946277 on Asus Nexus 7 (NVIDIA Tegra 3) running JB

Categories

(Firefox for Android Graveyard :: Plugins, defect)

ARM
Android
defect
Not set
normal

Tracking

(firefox16 affected, firefox17 affected, firefox18- wontfix, firefox19- affected, firefox20 affected, firefox21 affected, firefox22 affected, firefox23 affected)

RESOLVED WONTFIX
Tracking Status
firefox16 --- affected
firefox17 --- affected
firefox18 - wontfix
firefox19 - affected
firefox20 --- affected
firefox21 --- affected
firefox22 --- affected
firefox23 --- affected

People

(Reporter: scoobidiver, Unassigned)

Details

(Keywords: crash, Whiteboard: [native-crash][unactionable])

Crash Data

Attachments

(2 files)

This bug was filed from the Socorro interface and is 
report bp-e87d9372-6aca-4607-b524-f58be2120811 .
============================================================= 

It's #31 top crasher in 15.0b4, #24 in 16.0a2, and #92 in 17.0a1.
Oddly, 14.0.2 that is JB only is not affected.

More reports at:
https://crash-stats.mozilla.com/report/list?signature=libGLESv2_tegra.so%400x4ae10
Crash Signature: [@ libGLESv2_tegra.so@0x4ae10] → [@ libGLESv2_tegra.so@0x4ae10] [@ libGLESv2_tegra.so@0x4ae28]
Summary: crash in libGLESv2_tegra.so@0x4ae10 on Galaxy Nexus 7 (NVIDIA Tegra 3) with JB → crash in libGLESv2_tegra.so@0x4ae.. on Galaxy Nexus 7 (NVIDIA Tegra 3) with JB
With the release of Android 4.2, it's #6 top crasher in 17.0b7.
tracking-fennec: --- → ?
(In reply to Scoobidiver from comment #1)
> With the release of Android 4.2, it's #6 top crasher in 17.0b7.
Android 4.2 users were over-represented in 17.0b7. It's no longer a top crasher in 17.0.
tracking-fennec: ? → ---
Keywords: topcrash
I still want us to consider tracking those JB and Tegra3 crashes and trying to figure out what we can do there as I think the Tegra3 devices will grow in volume - probably even soon, as many of those could land under the tree at Christmas.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #3)
> I still want us to consider tracking those JB and Tegra3 crashes and trying
> to figure out what we can do there as I think the Tegra3 devices will grow
> in volume - probably even soon, as many of those could land under the tree
> at Christmas.

Agreed, but before we track, where does this fall in the 4.2 top crash list?
We don't yet have a 4.2-specific top crash list, but given comment 1, it's obviously up there.

Sending over to Mark to re-assign.
Assignee: nobody → mark.finkle
(KaiRo mentions that this is related to Flash on JB, given the stacks found on Socorro)
Keywords: needURLs
We only have 6 URLs for this signature, two of which are adult videos which I won't cite publicly (if you really need them for testing, please ping us privately), the four others are:

1 	https://apps.facebook.com/d-slots/?ref1=profile&ref=wall_BCB_112012
1 	http://www.nexttv.com.tw/
1 	http://www.itv.com/itvplayer/video/?Filter=327699
1 	http://www.amazon.com/Sony-DSC-RX100-Sensor-Digital-Camera/dp/B00889ST2G/ref=sr_1_3?s=photo&ie=UTF8&qid=1353347431&sr=1-3&keywords=Canon+eos+m
Kevin/Aaron - who's planning on filling this qawanted request?
Visiting those URL's above on my Nexus 7 (Android 4.2), and Galaxy Nexus (Android 4.2.1) w/Adobe Player 11.1 for Android 2.x and 3.x (11.1.111.24), I was unsuccessful in being able to reproduce any crash.
Keywords: qawanted
Mark - do you think blind engineering investigation could yield anything here?
It's #4 top crasher in 18.0b3 but Android 4.2 users are overrepresented.
Keywords: topcrash
This crash continues to be #2 on 18 beta.

Mark, is there any way we can get someone to investigate what is going on there?
Note that there are a lot of libflashplayer frames in those stacks.
Flags: needinfo?(mark.finkle)
There is nothing but guess work to be done. I can't assign that to someone. We'd have more of a chance of seeing this crash if more devs and QA were using the device. I'll ask about that possibility. I notice this only seems to occur when we hit beta. I don't see any fx20 or fx21 crashes. Our nightly and aurora audiences are small, but I would have figured seeing at least one crash.
Assignee: mark.finkle → nobody
Flags: needinfo?(mark.finkle)
(In reply to Mark Finkle (:mfinkle) from comment #14)
> There is nothing but guess work to be done. I can't assign that to someone.
> We'd have more of a chance of seeing this crash if more devs and QA were
> using the device. I'll ask about that possibility. I notice this only seems
> to occur when we hit beta. I don't see any fx20 or fx21 crashes. Our nightly
> and aurora audiences are small, but I would have figured seeing at least one
> crash.

Given that, there's no need to track for a specific release. This will remain on the topcrash list.

This crash is currently at #5 on beta.
Summary: crash in libGLESv2_tegra.so@0x4ae.. on Galaxy Nexus 7 (NVIDIA Tegra 3) with JB → crash in libGLESv2_tegra.so@0x4ae.. on Asus Nexus 7 (NVIDIA Tegra 3) with JB
Until we get steps let's get the tegra driver so we can pull symbols. This will give us better crash reports for Nexus 7 tegra crashes.

Can someone who has a tegra 3 device pull the library and email them to ted? They are typically, but not always, in '/system/lib/vendor'.
Pulled a full copy of /system/lib @ http://people.mozilla.com/~kbrosnan/tmp/782223/nexus-7-Android-4.2.2.zip handing off to Ted.
Flags: needinfo?(ted)
Okay, I finally dumped symbols out of these and fiddled with it. Along the way I found a bug in the symbol dumping code I had written, so after I fixed that I found that this stack goes into libflashplayer.so. :-/

This stack is from bp-fe455f1a-978d-4204-a250-0ca4d2130417.

I'll put these symbols on the symbol server and we'll see if reprocessing them clears anything up.
Flags: needinfo?(ted)
Adding the symbolized signature. It's not actually in this function (it's libGLESv2_tegra.so!NvGl214081946277 + 0x246d4, so it's *way* outside), but that's just an artifact of how Breakpad deals with export symbols.
Crash Signature: [@ libGLESv2_tegra.so@0x4ae10] [@ libGLESv2_tegra.so@0x4ae28] → [@ libGLESv2_tegra.so@0x4ae10] [@ libGLESv2_tegra.so@0x4ae28] [@ libGLESv2_tegra.so!NvGl214081946277 ]
Pulling in snorp since flash is causing the crash.

Ted should we look into getting you that libflashplayer.so?
Component: Graphics, Panning and Zooming → Plugins
kbrosnan pointed me at the Adobe download page, I'll track it down.
It doesn't appear to be any of the versions of Flash 11.5 on the Adobe download page. We have a symbol file for it on the symbol server that I uploaded in January, but it doesn't seem to have unwind info covering the function in question, so it doesn't make the stack any better. I have no idea where I got that symbol file from.
These reports are still coming in, they're using the new symbols I uploaded:
https://crash-stats.mozilla.com/report/list?product=FennecAndroid&query_search=signature&query_type=exact&query=NvGl214081946277&reason_type=contains&date=04%2F18%2F2013%2011%3A39%3A43&range_value=1&range_unit=weeks&hang_type=any&process_type=any&do_query=1&admin=1&signature=NvGl214081946277

(adjusting signature because I flubbed it the first time)

The stack ends in libflashplayer.so, unhelpfully:
https://crash-stats.mozilla.com/report/index/f3c1431d-769e-46d3-ac45-8eb302130418

I guess that's better than it used to be, though.
Crash Signature: [@ libGLESv2_tegra.so@0x4ae10] [@ libGLESv2_tegra.so@0x4ae28] [@ libGLESv2_tegra.so!NvGl214081946277 ] → [@ libGLESv2_tegra.so@0x4ae10] [@ libGLESv2_tegra.so@0x4ae28] [@ NvGl214081946277 ]
I ran my dump-lookup tool against the crash from comment 18, and once you get past the flashplayer stuff there's a plausible looking stack in Gecko on the bottom. The last bit of Gecko on the stack appears to be PluginTimerCallback:
http://hg.mozilla.org/releases/mozilla-release/annotate/48255272a995/dom/plugins/base/nsNPAPIPluginInstance.cpp#l1430
(In reply to Ted Mielczarek [:ted.mielczarek] from comment #22)
> It doesn't appear to be any of the versions of Flash 11.5 on the Adobe
> download page. We have a symbol file for it on the symbol server that I
> uploaded in January, but it doesn't seem to have unwind info covering the
> function in question, so it doesn't make the stack any better. I have no
> idea where I got that symbol file from.

I generated symbol files for you a while back (apparently January) by running the appropriate things on all the libraries on the Flash archive web page.
Summary: crash in libGLESv2_tegra.so@0x4ae.. on Asus Nexus 7 (NVIDIA Tegra 3) with JB → crash in NvGl214081946277 on Asus Nexus 7 (NVIDIA Tegra 3) running JB
Adding needsurl's to see if we have any new/popular urls here for QA to start here as the url's posted in comment# 8 are ~5months old.
Keywords: needURLs
Adding the JB 4.3 signature.
Crash Signature: [@ libGLESv2_tegra.so@0x4ae10] [@ libGLESv2_tegra.so@0x4ae28] [@ NvGl214081946277 ] → [@ libGLESv2_tegra.so@0x4ae10] [@ libGLESv2_tegra.so@0x4ae28] [@ libGLESv2_tegra.so@0x4a2c4] [@ NvGl214081946277 ]
Hey Snorp, we're leaning towards adding [unactionable] to the whiteboard since this has had such little traction. If you agree, please add [unactionable]
Flags: needinfo?(snorp)
(In reply to Alex Keybl [:akeybl] from comment #30)
> Hey Snorp, we're leaning towards adding [unactionable] to the whiteboard
> since this has had such little traction. If you agree, please add
> [unactionable]

I think that's ok unless we get some further information later on.
Flags: needinfo?(snorp)
Whiteboard: [native-crash] → [native-crash][unactionable]
This is not a top crash any more. Its rank in 25 release is in the 40s.
Severity: critical → normal
Flash is going away: Bug 1381916.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: Firefox for Android → Firefox for Android Graveyard

Removing steps-wanted keyword because this bug has been resolved.

Keywords: steps-wanted

Removing steps-wanted keyword because this bug has been resolved.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: