Closed
Bug 736421
Opened 13 years ago
Closed 12 years ago
crash in mozilla::AndroidLayerRendererFrame::DrawForeground @ CgDrv_Create on MB860, LG-P990 and LG-P999 (Tegra2 + ICS)
Categories
(Core Graveyard :: Widget: Android, defect)
Tracking
(firefox14 wontfix, firefox15 fixed, firefox16 fixed, blocking-fennec1.0 .N+)
RESOLVED
FIXED
mozilla16
People
(Reporter: scoobidiver, Assigned: vlad)
References
Details
(Keywords: crash, regression, topcrash, Whiteboard: [native-crash][gfx])
Crash Data
Attachments
(1 file, 1 obsolete file)
2.68 KB,
patch
|
snorp
:
review+
blassey
:
approval-mozilla-aurora+
blassey
:
approval-mozilla-beta-
|
Details | Diff | Splinter Review |
It first appeared in 14.0a1/20120315:
bp-5ed33483-218c-4419-b1f1-cce432120316
It's currently #3 top crasher in 14.0a1.
More reports at:
https://crash-stats.mozilla.com/report/list?signature=CgDrv_Create
Updated•13 years ago
|
Component: General → Graphics
Product: Fennec Native → Core
QA Contact: general → thebes
Version: Firefox 14 → 14 Branch
Comment 1•13 years ago
|
||
ajuma, do you have any recommendations for this topcrash? It looks like we're crashing in the Atrix MB860's GL driver.
Assignee: nobody → ajuma
Comment 2•13 years ago
|
||
We need to get our hands on the GL driver from this device so we can grab symbols and find out where in the driver this is happening.
Knowing the URLs where this crash happens would be helpful too.
Keywords: needURLs
Reporter | ||
Comment 3•13 years ago
|
||
There's one crash on LG-P990 CyanogenMod: bp-3a0f9dab-423b-4345-9823-5c33f2120318.
Comment 4•13 years ago
|
||
Only two URLs came up in the search:
17 \N
1 http://www.bbc.co.uk/news/10318089
1 http://www.abovetopsecret.com/forum/thread819897/pg1
Keywords: needURLs
The crash seemed to have died down. Last crash from build: 20120331031108
Found only one other URL:
http://www.ouest-france.fr/actu/actuDet_-Orelsan-programme-a-La-Reunion-la-Region-retire-sa-subvention_39382-2060296_actu.Htm
Reporter | ||
Comment 6•13 years ago
|
||
(In reply to Naoki Hirata :nhirata from comment #5)
> The crash seemed to have died down. Last crash from build: 20120331031108
There are still recent crashes, but it's no longer a top crasher.
Keywords: topcrash
Summary: crash in mozilla::layers::Layer::CalculateScissorRect @ CgDrv_Create on MB860 → crash in mozilla::layers::Layer::CalculateScissorRect @ CgDrv_Create on MB860 and LG-P99.
Reporter | ||
Comment 7•13 years ago
|
||
There's a spike in crashes from two users that use those devices unsupported on native Fennec, but supported on XUL Fennec.
It's within the top 10 top crashers now... not placing in topcrash due to comment 7
Reporter | ||
Comment 9•13 years ago
|
||
It affects 11 users over the last week.
Reporter | ||
Comment 10•13 years ago
|
||
Should we consider MB860 (2.3% of Android devices - source [1]) and LG-P99* as unsupported?
[1]: https://docs.google.com/spreadsheet/ccc?key=0ArpSb7XMTvzydDhVNWFXbXRkQ3VoQW4yaWptTjJjY3c&authkey=COzTgpEG&authkey=COzTgpEG
Assignee | ||
Comment 11•13 years ago
|
||
Well, I have an MB860/Atrix... would be nice to figure out what's going on :)
Reporter | ||
Comment 12•13 years ago
|
||
It's #6 top crasher in the first days of 14.0b1.
It occurs also after the fix of bug 748531.
It would be interesting to have recent URLs now that 14.0b1 is released.
Assignee: ajuma → nobody
blocking-fennec1.0: --- → ?
Component: Graphics → Widget: Android
QA Contact: thebes → android
Summary: crash in mozilla::layers::Layer::CalculateScissorRect @ CgDrv_Create on MB860 and LG-P99. → crash in mozilla::AndroidLayerRendererFrame::DrawForeground @ CgDrv_Create on MB860, LG-P990 and LG-P999
Updated•13 years ago
|
Assignee: nobody → vladimir
blocking-fennec1.0: ? → +
Scoobidiver, what's the 14.0b1 that you are looking at? We have some bad data for 14b1 graphs. Yesterday was the first official release of 14b1 Native; 14b1 XUL is not released.
Comment 14•13 years ago
|
||
FWIW, those LG phones and the Atrix are all Tegra devices, and CgDrv_Create makes me think NVIDIA too.
Reporter | ||
Comment 15•13 years ago
|
||
(In reply to Naoki Hirata :nhirata from comment #13)
> Scoobidiver, what's the 14.0b1 that you are looking at? We have some bad
> data for 14b1 graphs. Yesterday was the first official release of 14b1
> Native; 14b1 XUL is not released.
This 14.0b1, https://crash-stats.mozilla.com/query/query?product=FennecAndroid&version=FennecAndroid%3A14.0b1&range_value=1&range_unit=weeks&query_search=signature&query_type=contains&query=&do_query=1, updated continuously contrarily to https://crash-stats.mozilla.com/topcrasher/byversion/FennecAndroid/14.0b1 updated once a day.
Comment 16•13 years ago
|
||
Yes, /query (advanced search) is doing live searches on what's in the database, topcrasher is generated once every day for the recent UTC day.
(In reply to Scoobidiver from comment #15)
> (In reply to Naoki Hirata :nhirata from comment #13)
> > Scoobidiver, what's the 14.0b1 that you are looking at? We have some bad
> > data for 14b1 graphs. Yesterday was the first official release of 14b1
> > Native; 14b1 XUL is not released.
> This 14.0b1,
> https://crash-stats.mozilla.com/query/
> query?product=FennecAndroid&version=FennecAndroid%3A14.
> 0b1&range_value=1&range_unit=weeks&query_search=signature&query_type=contains
> &query=&do_query=1, updated continuously contrarily to
> https://crash-stats.mozilla.com/topcrasher/byversion/FennecAndroid/14.0b1
> updated once a day.
Thanks Scoobi for the link. Would this link qualify the public beta (release date of 5/15) better?
https://crash-stats.mozilla.com/query/query?product=FennecAndroid&version=FennecAndroid%3A14.0b1&range_value=1&range_unit=weeks&date=05%2F22%2F2012+18%3A19%3A56&query_search=signature&query_type=contains&query=&reason=&build_id=&process_type=any&hang_type=any&do_query=1
Reporter | ||
Comment 18•13 years ago
|
||
(In reply to Naoki Hirata :nhirata from comment #17)
> Thanks Scoobi for the link. Would this link qualify the public beta
> (release date of 5/15) better?
My link is shorter because, with the date field, new crashes are not taken into account, and the reason, build_id, process_type and hang_type fields have their default value.
Ah. I was referring to adding the date of 5/22/2012 in the search field so that the start date would be from the official release date of 5/15.
Assignee | ||
Comment 20•13 years ago
|
||
These seem to have disappeared since the 0516 nightly build; I'm guessing that this is another bug 752368 dup. Also, given that most of the crashes are from CM users, not sure this needs to block. Keeping this open until we can verify crash numbers when next beta goes out.
Reporter | ||
Comment 21•13 years ago
|
||
(In reply to Vladimir Vukicevic (:vlad) from comment #20)
> These seem to have disappeared since the 0516 nightly build
Nightly is not statistically representative. There are still recent crashes in Aurora after the fix of bug 752368: bp-6a5085ee-1414-474f-bb31-542132120523.
Assignee | ||
Comment 22•13 years ago
|
||
True, I guess 3 crashes are enough to say "It's still happening", though much lower on the list. It could still be bug 752368 but in a different situation, but like I said, let's keep this open until the beta ships and see what happens.
Updated•13 years ago
|
Whiteboard: [native-crash] → [native-crash][gfx]
Comment 23•13 years ago
|
||
Looks like this is happening on beta3 still:
https://crash-stats.mozilla.com/report/list?product=FennecAndroid&version=FennecAndroid%3A14.0b3&query_search=signature&query_type=contains&reason_type=contains&date=05%2F26%2F2012%2002%3A32%3A36&range_value=1&range_unit=weeks&hang_type=any&process_type=any&do_query=1&signature=CgDrv_Create
Comment 24•13 years ago
|
||
Bug 757944 might help here.
Assignee | ||
Comment 25•13 years ago
|
||
I'd be surprised if bug 757944 helps, but maybe!
Comment 26•12 years ago
|
||
Bug 757944 has stalled - do we need to unstick it?
Comment 27•12 years ago
|
||
(In reply to JP Rosevear [:jpr] from comment #26)
> Bug 757944 has stalled - do we need to unstick it?
Bug 757944 has now landed on inbound. I'm also going to try to get symbols for these crashes, so that we can get a better idea of what might be causing this.
Comment 28•12 years ago
|
||
FWIW, the entry point into the driver is unsurprisingly glCompileShader()
Comment 29•12 years ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #28)
> FWIW, the entry point into the driver is unsurprisingly glCompileShader()
And it crashes because the compiler does a division by 0. It would be nice to know which shader is causing the crash.
Comment 30•12 years ago
|
||
Interestingly, there haven't been any of these on FF15 for quite a while.
Assignee | ||
Comment 32•12 years ago
|
||
We suspect that this might be flash related; it would be helpful if we could get a module correlation for all of these crashes, to see if libflashplayer.so appears in all of them.
Assignee | ||
Comment 33•12 years ago
|
||
So looking more at this, these all look to be Tegra 2 devices that are running some form of ICS rom (almost all non-vendor-provided, e.g. CM9). The flash version is likely to be the same one that shipped with gingerbread on these phones (which is the stock vendor-provided one), and so we're most likely getting some sort of form of bug 703056, but we're not being blocked because the devices are running ICS.
I think we need a finer-grained block here somehow.
Depends on: 703056
Summary: crash in mozilla::AndroidLayerRendererFrame::DrawForeground @ CgDrv_Create on MB860, LG-P990 and LG-P999 → crash in mozilla::AndroidLayerRendererFrame::DrawForeground @ CgDrv_Create on MB860, LG-P990 and LG-P999 (Tegra2 + ICS)
Assignee | ||
Comment 34•12 years ago
|
||
All of the crashes in b4/b5 are with 1) homebrew ICS; 2) libflashplayer.so with a 'debug id' of 79B73C212164CC7699C039D8B6C646570 . Some of the online reviews about CM9 on some of these devices say that flash does not work with the built in browser.
That 'debug id' is generated by taking the first 4096 bytes of the text section of the .so and xor'ing guid-sized chunks together, as seen here http://mxr.mozilla.org/mozilla-central/source/toolkit/crashreporter/google-breakpad/src/common/linux/file_id.cc#144 .
So maybe we block flash on Tegra 2 devices that have libflashplayer.so that has that signature?
Assignee | ||
Comment 35•12 years ago
|
||
The latest libflashplayer.so that's served by the market is:
SDK version 8..14 (downloaded on my Atrix with gingerbread):
79 b7 31 21 14 20 cc 76 15 a7 39 d8 b6 c6 46 57 0
SDK version 15 onward (downloaded on my Galaxy Nexus with ICS):
79 b7 3c 21 cc 76 21 64 d8 39 c0 99 57 46 c6 b6 0
(note if anyone repeats this exercise: you can xor the bytes together, but the version that's displayed on breakpad is the GUID form -- int, short, short, bytes -- so you have to rearrange bytes appropriately). The flash version that we're crashing with is the ICS one which makes sense, that's what they'd get from the market given that they'll be prsenting an ICS SDK version.
So we have:
1) Homebrew ICS
2) Tegra 2
3) ICS Flash 11
Assignee | ||
Comment 36•12 years ago
|
||
Renomming. This only seems to happen with aftermarket android firmware; most common with CM9 but with others as well. I suggest we either minus and ignore this crash for now, or add some filtering based on kernel version and block some common kernel strings (CM9, cyanogen, nova, a few others). I may just write up that version anyway, since should just be able to look at /proc/version.
blocking-fennec1.0: + → ?
Assignee | ||
Comment 37•12 years ago
|
||
Sort of band-aid-y, but should work to get rid of this crash. It would be nice to have a way to override our blacklisting of Flash, but meh.
Attachment #629877 -
Flags: review?(snorp)
Updated•12 years ago
|
blocking-fennec1.0: ? → soft
Comment 38•12 years ago
|
||
Comment on attachment 629877 [details] [diff] [review]
maybe like this?
Review of attachment 629877 [details] [diff] [review]:
-----------------------------------------------------------------
Should probably put vreader.close() in a finally() clause since readLine() and other stuff can throw. Looks fine otherwise.
Attachment #629877 -
Flags: review?(snorp) → review+
Assignee | ||
Comment 39•12 years ago
|
||
Better; adds some logging as well, just in case.
Attachment #630239 -
Flags: review?(snorp)
Comment 40•12 years ago
|
||
Comment on attachment 630239 [details] [diff] [review]
better
Review of attachment 630239 [details] [diff] [review]:
-----------------------------------------------------------------
Might as well put the bug number in the log message too :)
Attachment #630239 -
Flags: review?(snorp) → review+
Assignee | ||
Comment 41•12 years ago
|
||
Pushed to inbound with bug # in log message:
https://hg.mozilla.org/integration/mozilla-inbound/rev/18c5fc416d4a
Assignee | ||
Updated•12 years ago
|
Attachment #629877 -
Attachment is obsolete: true
Assignee | ||
Updated•12 years ago
|
Target Milestone: --- → mozilla16
Reporter | ||
Comment 42•12 years ago
|
||
Based on affected devices, I add the kill | raise signature: https://crash-stats.mozilla.com/report/list?signature=kill+|+raise
Crash Signature: [@ CgDrv_Create] → [@ CgDrv_Create]
[@ kill | raise]
status-firefox14:
--- → affected
status-firefox15:
--- → affected
Keywords: needURLs
Assignee | ||
Comment 43•12 years ago
|
||
It's definitely the same set of devices, but it might not be the same issue. I wouldn't necessarily expect it to go away with this patch.
Comment 44•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
removing QA wanted. Not going to root a specific phone w/ CM specifically for this. Will monitor in Socorro.
Keywords: qawanted
Comment 46•12 years ago
|
||
Vlad, please nominate this for aurora and beta
Updated•12 years ago
|
blocking-fennec1.0: soft → .N+
Assignee | ||
Comment 47•12 years ago
|
||
Comment on attachment 630239 [details] [diff] [review]
better
[Approval Request Comment]
User impact if declined: ugly crashes with flash plugin on some devices, though largely ones with CyanogenMod and other custom firmware
Testing completed (on m-c, etc.): on m-c
Risk to taking this patch (and alternatives if risky): none; just adds some more checks to our existing flash blacklisting code
String or UUID changes made by this patch: none
Attachment #630239 -
Flags: approval-mozilla-beta?
Attachment #630239 -
Flags: approval-mozilla-aurora?
Updated•12 years ago
|
Attachment #630239 -
Flags: approval-mozilla-beta?
Attachment #630239 -
Flags: approval-mozilla-beta-
Attachment #630239 -
Flags: approval-mozilla-aurora?
Attachment #630239 -
Flags: approval-mozilla-aurora+
Reporter | ||
Comment 48•12 years ago
|
||
There are still crashes in the trunk:
bp-19622233-0162-4d57-bfc0-0e4462120613
bp-fdd23e04-f49c-409c-8ffa-e7e222120615
bp-c4299b36-c585-4444-85a2-dda3f2120615
Assignee | ||
Comment 49•12 years ago
|
||
Yup, those are all on platforms where we didn't block it -- "p990-ics" is one of them, because it wasn't clear whether that was a custom firmware or an early build of ics for the p990. The third one there could be a normal motorola kernel; they have a bad habit of building some random git revision without giving it any useful name. Regardless, none of those crashes would have been stopped by the patch here, but the overall number should have gone down.
Updated•12 years ago
|
Assignee | ||
Comment 50•12 years ago
|
||
Target Milestone: mozilla16 → mozilla15
Reporter | ||
Updated•12 years ago
|
status-firefox16:
--- → fixed
Reporter | ||
Comment 51•12 years ago
|
||
Target Milestone is for m-c.
Target Milestone: mozilla15 → mozilla16
Reporter | ||
Comment 52•12 years ago
|
||
There are still crashes: https://crash-stats.mozilla.com/report/list?signature=CgDrv_Create
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•