Closed
Bug 970096
Opened 12 years ago
Closed 12 years ago
crash in mozilla::gl::GLContextProviderEGL::CreateForWindow(nsIWidget*) - mostly on Sony ICS devices
Categories
(Firefox for Android Graveyard :: Toolbar, defect)
Tracking
(firefox27 unaffected, firefox28+ fixed, firefox29+ fixed, firefox30+ fixed, b2g-v1.3 fixed, fennec28+)
RESOLVED
FIXED
Firefox 30
People
(Reporter: kbrosnan, Assigned: snorp)
References
Details
(Keywords: crash, topcrash-android-armv7, Whiteboard: [native-crash])
Crash Data
Attachments
(1 file)
|
1.00 KB,
patch
|
bjacob
:
review+
Sylvestre
:
approval-mozilla-aurora+
Sylvestre
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
This bug was filed from the Socorro interface and is
report bp-847b7405-1e51-4eae-aa4f-84be02140208.
=============================================================
Some sort of startup crash.
Updated•12 years ago
|
Updated•12 years ago
|
Assignee: nobody → snorp
tracking-fennec: ? → 28+
| Assignee | ||
Comment 1•12 years ago
|
||
Do we have any STR here? I've never seen this myself, AFAIK.
| Reporter | ||
Comment 2•12 years ago
|
||
Seems to be common on Sony Ericsson ICS phones. There is a long tail of other manufactures. This can be seen on the "Signature Summary" page -> "Mobile Devices" at https://crash-stats.mozilla.com/report/list?product=FennecAndroid&signature=mozilla%3A%3Agl%3A%3AGLContextProviderEGL%3A%3ACreateForWindow(nsIWidget*)
Sony Ericsson LT18i
Sony Ericsson MT11i
Sony Ericsson SK17i
Sony Ericsson WT19a
Sony Ericsson ST15i
Sony Ericsson WT19i
Sony Ericsson MT25i
Sony Ericsson MT15i
Sony Ericsson MK16i
Sony Ericsson ST18i
We don't have these phones, likely would require scouring eBay or similar.
Comments do not contain anything useful nor do URLs.
Summary: crash in mozilla::gl::GLContextProviderEGL::CreateForWindow(nsIWidget*) → crash in mozilla::gl::GLContextProviderEGL::CreateForWindow(nsIWidget*) - mostly on Sony ICS deivces
| Assignee | ||
Comment 3•12 years ago
|
||
So this appears to be due to a MOZ_CRASH() that gets hit when we are unable to find a usable EGLConfig. It looks like if the screen depth is 24bit, we only try to get a 24bit EGLConfig. Maybe these devices can only support a 16bit one?
QA, can we try to get one of these devices please? In the mean time, I guess we could try a speculative patch.
| Assignee | ||
Comment 4•12 years ago
|
||
Attachment #8380817 -
Flags: review?(bjacob)
Comment 5•12 years ago
|
||
Since, in the fallback case, it seems that we're willing to continue with whichever R/G/B channels depth we'll get, why bother specifying them in the attribs list at all?
Comment 6•12 years ago
|
||
Comment on attachment 8380817 [details] [diff] [review]
Try a 16 bit OpenGL context as a last result on Android
Review of attachment 8380817 [details] [diff] [review]:
-----------------------------------------------------------------
but, if you need a 2-line patch to land to see if this fixes crash-stat, then sure.
Attachment #8380817 -
Flags: review?(bjacob) → review+
| Assignee | ||
Comment 7•12 years ago
|
||
| Assignee | ||
Comment 8•12 years ago
|
||
(In reply to Benoit Jacob [:bjacob] from comment #5)
> Since, in the fallback case, it seems that we're willing to continue with
> whichever R/G/B channels depth we'll get, why bother specifying them in the
> attribs list at all?
It's not clear to me that the configs would be sorted in any meaningful way if we leave those out entirely. So we'd have to go through and figure out which one is best, which is pretty ugh. I could be wrong, though? If we just request 565, will it return 888 if that's available?
Comment 9•12 years ago
|
||
It is "pretty ugh" indeed, but it is what we are supposed to be doing; maybe that's what we should be fixing!
I don't know at the moment is the size attributes require == or >= matching.
| Assignee | ||
Comment 10•12 years ago
|
||
http://www.khronos.org/registry/egl/sdk/docs/man/xhtml/eglChooseConfig.html
The comments there about sort order seem to indicate that maybe it's >=, but then how would our 16bit thing ever work right now if a driver supports 24? Changing stuff like this makes me very nervous, because it's so fragile and seemingly device-dependent.
Comment 11•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 30
| Assignee | ||
Comment 12•12 years ago
|
||
Comment on attachment 8380817 [details] [diff] [review]
Try a 16 bit OpenGL context as a last result on Android
There are no crashes on m-c from this bug, so we'll need to uplift it to see if it fixes things or not.
[Approval Request Comment]
Bug caused by (feature/regressing bug #): N/A
User impact if declined: Startup crashes on some phones
Testing completed (on m-c, etc.): m-c
Risk to taking this patch (and alternatives if risky): None
String or IDL/UUID changes made by this patch: None
Attachment #8380817 -
Flags: approval-mozilla-beta?
Attachment #8380817 -
Flags: approval-mozilla-aurora?
Updated•12 years ago
|
Attachment #8380817 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
Updated•12 years ago
|
Summary: crash in mozilla::gl::GLContextProviderEGL::CreateForWindow(nsIWidget*) - mostly on Sony ICS deivces → crash in mozilla::gl::GLContextProviderEGL::CreateForWindow(nsIWidget*) - mostly on Sony ICS devices
Updated•12 years ago
|
Attachment #8380817 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Comment 13•12 years ago
|
||
Comment 14•12 years ago
|
||
Updated•12 years ago
|
status-b2g-v1.3:
--- → fixed
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•