Closed Bug 763173 Opened 12 years ago Closed 12 years ago

Startup crash in AndroidGLController::ProvideEGLSurface during LayerManagerOGL::CreateContext

Categories

(Firefox for Android Graveyard :: General, defect)

14 Branch
ARM
Android
defect
Not set
critical

Tracking

(firefox14 affected, firefox15 unaffected, firefox16 unaffected)

RESOLVED WORKSFORME
Tracking Status
firefox14 --- affected
firefox15 --- unaffected
firefox16 --- unaffected

People

(Reporter: scoobidiver, Unassigned)

Details

(Keywords: crash, Whiteboard: [native-crash][gfx][startupcrash])

Crash Data

This bug tracks startup crashes not fixed by bug 745243.
In 14.0b6, there are currently 6 crashes with the AndroidGLController::ProvideEGLSurface signature amongst 1323 crashes, i.e. 0.45% of all crashes.
I don't see the stack in crashes with the JNI_GetCreatedJavaVMs | AndroidGLController::ProvideEGLSurface signature.

Signature 	AndroidGLController::ProvideEGLSurface More Reports Search
UUID	a7b4728a-e53b-4d31-b709-d16522120608
Date Processed	2012-06-08 19:21:09
Uptime	34
Install Age	34 seconds since version was first installed.
Install Time	2012-06-08 19:20:12
Product	FennecAndroid
Version	14.0
Build ID	20120605235323
Release Channel	beta
OS	Linux
OS Version	0.0.0 Linux 3.0.8+ #1 PREEMPT Fri Apr 6 20:21:41 CST 2012 armv7l
Build Architecture	arm
Build Architecture Info	
Crash Reason	SIGSEGV
Crash Address	0x8
App Notes 	
AdapterVendorID: sun4i, AdapterDeviceID: MID.
AdapterDescription: 'Model: 'MID', Product: 'crane_a710', Manufacturer: 'unknown', Hardware: 'sun4i''.
unknown MID
BRONCHO/crane_a710/crane-a710:4.0.3/IML74K/20120409:eng/test-keys
EMCheckCompatibility	True

Frame 	Module 	Signature 	Source
0 	libdvm.so 	libdvm.so@0x56b72 	
1 	dalvik-LinearAlloc (deleted) 	dalvik-LinearAlloc @0x238cc6 	
2 	libxul.so 	AndroidGLController::ProvideEGLSurface 	jni.h:706
3 	libxul.so 	mozilla::AndroidBridge::ProvideEGLSurface 	widget/android/AndroidBridge.cpp:1217
4 	libxul.so 	mozilla::gl::GLContextProviderEGL::CreateForWindow 	gfx/gl/GLContextProviderEGL.cpp:1563
5 	libxul.so 	mozilla::layers::LayerManagerOGL::CreateContext 	gfx/layers/opengl/LayerManagerOGL.cpp:176
6 	libxul.so 	mozilla::layers::CompositorParent::AllocPLayers 	LayerManagerOGL.h:111
7 	libxul.so 	mozilla::layers::PCompositorParent::OnMessageReceived 	obj-firefox/ipc/ipdl/PCompositorParent.cpp:470
8 	libxul.so 	mozilla::ipc::SyncChannel::OnDispatchMessage 	ipc/glue/SyncChannel.cpp:175
9 	libxul.so 	mozilla::ipc::RPCChannel::OnMaybeDequeueOne 	ipc/glue/RPCChannel.cpp:432
10 	libxul.so 	RunnableMethod<mozilla::ipc::RPCChannel, bool , Tuple0>::Run 	ipc/chromium/src/base/tuple.h:383
11 	libxul.so 	mozilla::ipc::RPCChannel::DequeueTask::Run 	RPCChannel.h:462
12 	libxul.so 	MessageLoop::RunTask 	ipc/chromium/src/base/message_loop.cc:318
13 	libxul.so 	MessageLoop::DeferOrRunPendingTask 	ipc/chromium/src/base/message_loop.cc:326
14 	libxul.so 	MessageLoop::DoWork 	ipc/chromium/src/base/message_loop.cc:426
15 	libxul.so 	base::MessagePumpDefault::Run 	ipc/chromium/src/base/message_pump_default.cc:23
16 	libxul.so 	MessageLoop::RunInternal 	ipc/chromium/src/base/message_loop.cc:208
17 	libxul.so 	MessageLoop::Run 	ipc/chromium/src/base/message_loop.cc:201
18 	libxul.so 	base::Thread::ThreadMain 	ipc/chromium/src/base/thread.cc:156
19 	libxul.so 	ThreadFunc 	ipc/chromium/src/base/platform_thread_posix.cc:26
20 	libc.so 	libc.so@0x12be6 	
21 	libc.so 	libc.so@0x1273a 	

More reports at:
https://crash-stats.mozilla.com/report/list?signature=AndroidGLController%3A%3AProvideEGLSurface
Whiteboard: [native-crash][gfx] → [native-crash][gfx][startupcrash]
This is a topcrash in 14.0b6, but no longer seems to appear in 15 or 16.
(In reply to Chris Peterson (:cpeterson) from comment #1)
> This is a topcrash in 14.0b6
It's not a topcrasher. You mixed it with bug 763175 that has the same signature.
There are no crashes in 14.0b10.
It might be fixed by bug 750272 like bug 763175.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.