Closed
Bug 766816
Opened 12 years ago
Closed 8 years ago
crash in mozilla::WebGLContext::SetDimensions @ libGLESv2_adreno200
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: alex_mayorga, Unassigned)
References
()
Details
(Keywords: crash, reproducible, Whiteboard: [native-crash][gfx] webgl-driver)
Crash Data
Attachments
(1 file)
(deleted),
text/plain
|
Details |
This bug was filed from the Socorro interface and is 
report bp-11c8f6ed-0a74-4792-88f1-2c5232120621 .
============================================================= 
Comment 1•12 years ago
|
||
What are your STR?
Can you provide the logcat using aLogcat?
Does it happen with the latest Nightly build?
Crash Signature: [@ __libc_android_abort | dlfree | free | libGLESv2_adreno200.so@0x6d9e3] → [@ __libc_android_abort | dlfree | free | libGLESv2_adreno200.so@0x6d9e3 ]
OS: Linux → Android
Hardware: All → ARM
Summary: crash in __libc_android_abort → crash in mozilla::gl::GLContextEGL::MakeCurrentImpl @ libGLESv2_adreno200
Whiteboard: [native-crash][gfx]
Version: unspecified → Trunk
Reporter | ||
Comment 2•12 years ago
|
||
Reporter | ||
Comment 3•12 years ago
|
||
There are no STR just visiting about:crashes shows dozens of these crashes.
Comment 4•12 years ago
|
||
The stack shows that this happened while creating a WebGL context (see WebGLContext::SetDimensions in the stack).
WebGL is already blacklisted on Adreno devices. We can't be 100% sure that blacklisting works until bug 766251 lands, but we already see in the App Notes that earlier in the same session, we see that a WebGL context creation had failed (WebGL-) almost certainly due to blacklisting. So the question is why did blacklisting not work this second time?
Normally one would suspect that the user force-enabled the feature, but this should have added a WebGL! to the app notes. Unclear at the moment. Bug 766251 will add GPU identification information to the appnotes, so maybe we'll have more clues then.
Updated•12 years ago
|
Component: General → Canvas: WebGL
Product: Fennec Native → Core
QA Contact: general → canvas.webgl
Updated•12 years ago
|
Crash Signature: [@ __libc_android_abort | dlfree | free | libGLESv2_adreno200.so@0x6d9e3 ] → [@ __libc_android_abort | dlfree | free | libGLESv2_adreno200.so@0x6d9e3 ]
[@ __libc_android_abort | dlfree | free | libGLESv2_adreno200.so@0x9bb37 ]
[@ __libc_android_abort | dlfree | free | libGLESv2_adreno200.so@0x6d9eb ]
[@ libGLESv2_adreno200.so@0…
Summary: crash in mozilla::gl::GLContextEGL::MakeCurrentImpl @ libGLESv2_adreno200 → crash in mozilla::WebGLContext::SetDimensions @ libGLESv2_adreno200
Comment 6•12 years ago
|
||
Here is a recent crash report: bp-7c02b801-51b5-4569-8b85-635112120823. The App Notes contain:
AdapterDescription: 'Qualcomm -- Adreno (TM) 225 -- OpenGL ES 2.0 AU_LINUX_ANDROID_JB.04.01.01.00.036 (CL2644550) -- Model: SCH-I535, Product: d2vzw, Manufacturer: Samsung, Hardware: qcom'
EGL? EGL+ GL Context? GL Context+ GL Layers? GL Layers+
Comment 7•12 years ago
|
||
Re: comment 6: the AppNotes don't show WebGL, so this was not a WebGL context creation crash i.e. it's a separate bug.
Comment 8•12 years ago
|
||
I hit this running Peacekeeper.
Samsung Galaxy SII i727
Android 2.3.6
Keywords: reproducible
Comment 9•11 years ago
|
||
On HTC Desire Z (Android 2.3) using Nightly 27.0a1 (2013-10-09) sometimes Firefox crashes with this crash signature.
after installing or launching the "Pasjans/Solitaire" app.
--
https://crash-stats.mozilla.com/report/index/17eacb87-6b1c-466b-be70-e23002131010
Comment 10•11 years ago
|
||
That crash stack shows it's a canvas 2D crash, not a WebGL crash. Maybe file a new bug for it?
Updated•11 years ago
|
Whiteboard: [native-crash][gfx] → [native-crash][gfx] webgl-driver
Comment 11•8 years ago
|
||
There are no crashes reported recently with current Fennec builds. For the most part this seems to have stopped after Fennec 27. Please reopen this bug report if you can reproduce the crash in a current Fennec build.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•