865795 - crash in mozilla::gl::DoesStringMatch with error message: "Maybe this device does not support OpenGL ES2? (EGL error 3003)"

Status: RESOLVED INCOMPLETE

(Core :: Graphics, defect)

Description

[Scoobidiver (away)]

It's a low volume crash.

The affected devices for the last four days are:
LGE LG-P500 	9
ZTE ZTE-BLADE 	7
LGE LG-LW690 	7
LGE LG-MS690 	4
LGE LG-P505R 	4
Motorola MOTWX435KT 3
LGE LG-P500h 	1
LGE LG-P505 	1
ZTE V9e 	1
HTC Aria A6380 1

Signature 	mozilla::gl::DoesStringMatch More Reports Search
UUID	d17df502-4357-4e98-8732-81a7c2130425
Date Processed	2013-04-25 00:25:14
Uptime	5
Last Crash	13 seconds before submission
Install Age	22.4 hours since version was first installed.
Install Time	2013-04-24 02:02:05
Product	FennecAndroid
Version	20.0.1
Build ID	20130410154516
Release Channel	release
OS	Android
OS Version	0.0.0 Linux 2.6.32.9 #1 PREEMPT Fri Dec 17 18:41:57 KST 2010 armv6l metropcs/thunderc/thunderc/thunderc:2.2.1/FRG83/eng.lge.20101217.183801:user/release-keys
Build Architecture	arm
Build Architecture Info	
Crash Reason	SIGSEGV
Crash Address	0x1f00
App Notes 	
AdapterDescription: 'An error occurred earlier while querying gfx info: eglCreateContext failed to create a OpenGL ES2 contextMaybe this device does not support OpenGL ES2? (EGL error 3003).  --  --  -- Model: LG-MS690, Product: thunderc, Manufacturer: LGE, Hardware: thunderc'
nothumb Build
LGE LG-MS690
metropcs/thunderc/thunderc/thunderc:2.2.1/FRG83/eng.lge.20101217.183801:user/release-keys
Processor Notes 	sp-processor02.phx1.mozilla.com_15033:2012; exploitability tool: ERROR: unable to analyze dump
EMCheckCompatibility	True	
Device	LGE LG-MS690
Android API Version	8 (REL)
Android CPU ABI	armeabi

Frame 	Module 	Signature 	Source
0 	libc.so 	libc.so@0x1cf06 	
1 	libxul.so 	mozilla::gl::DoesStringMatch 	gfx/gl/GLContext.h:3078
2 	libxul.so 	mozilla::gl::GLContext::InitWithPrefix 	gfx/gl/GLContext.h:3075
3 	libxul.so 	mozilla::gl::GLContextEGL::Init 	gfx/gl/GLContextProviderEGL.cpp:343
4 	libxul.so 	mozilla::gl::GLContextProviderEGL::CreateForWindow 	gfx/gl/GLContextProviderEGL.cpp:236
5 	libxul.so 	mozilla::layers::LayerManagerOGL::CreateContext 	gfx/layers/opengl/LayerManagerOGL.cpp:466
6 	libxul.so 	mozilla::layers::LayerManagerOGL::Initialize 	gfx/layers/opengl/LayerManagerOGL.cpp:59
7 	libxul.so 	mozilla::layers::CompositorParent::AllocPLayers 	gfx/layers/ipc/CompositorParent.cpp:1123
8 	libxul.so 	mozilla::layers::PCompositorParent::OnMessageReceived 	obj-firefox/ipc/ipdl/PCompositorParent.cpp:591
9 	libxul.so 	mozilla::ipc::SyncChannel::OnDispatchMessage 	ipc/glue/SyncChannel.cpp:145
10 	libxul.so 	mozilla::ipc::RPCChannel::OnMaybeDequeueOne 	ipc/glue/RPCChannel.cpp:400
11 	libxul.so 	RunnableMethod<IPC::ChannelProxy::Context, void 	ipc/chromium/src/base/tuple.h:383
12 	libxul.so 	mozilla::ipc::RPCChannel::DequeueTask::Run 	RPCChannel.h:425
13 	libxul.so 	MessageLoop::RunTask 	ipc/chromium/src/base/message_loop.cc:333
14 	libxul.so 	MessageLoop::DeferOrRunPendingTask 	ipc/chromium/src/base/message_loop.cc:341
15 	libxul.so 	MessageLoop::DoWork 	ipc/chromium/src/base/message_loop.cc:441
16 	libxul.so 	base::MessagePumpDefault::Run 	ipc/chromium/src/base/message_pump_default.cc:23
17 	libxul.so 	MessageLoop::RunInternal 	ipc/chromium/src/base/message_loop.cc:215
18 	libxul.so 	MessageLoop::Run 	ipc/chromium/src/base/message_loop.cc:208
19 	libxul.so 	base::Thread::ThreadMain 	ipc/chromium/src/base/thread.cc:156
20 	libxul.so 	ThreadFunc 	ipc/chromium/src/base/platform_thread_posix.cc:39
21 	libc.so 	libc.so@0x1105e 	
22 	libc.so 	libc.so@0x40326 	
23 	libc.so 	libc.so@0x10b42 	

More reports at:
https://crash-stats.mozilla.com/report/list?signature=mozilla%3A%3Agl%3A%3ADoesStringMatch

Comment 1

[Milan Sreckovic [:milan] (needinfo for best results)]

Is this the same as bug 864103?

Comment 2

[Scoobidiver (away)]

(In reply to Milan Sreckovic [:milan] from comment #1)
> Is this the same as bug 864103?
No. See bug 864103 comment 2.

Comment 3

[u279076]

I am closing this bug as incomplete as there are no recent reports of this crash with current Fennec versions. Please reopen the bug if you can reproduce this crash in a currently supported Fennec version.