crash in webrtc::videocapturemodule::DeviceInfoAndroid::NumberOfDevices

VERIFIED FIXED in Firefox 25



WebRTC: Audio/Video
4 years ago
4 years ago


(Reporter: Scoobidiver (away), Assigned: gcp)


(Blocks: 1 bug, {crash, regression, reproducible})

24 Branch
crash, regression, reproducible
Dependency tree / graph

Firefox Tracking Flags

(firefox23 unaffected, firefox24+ wontfix, firefox25+ fixed, firefox26+ fixed, fennec24+)


(Whiteboard: [native-crash][getUserMedia][android-gum-], crash signature)



4 years ago
It seems bug 863290 is not fixed or at least the _JNIEnv::GetMethodID part.
The stack trace is better this time tough because of bug 884300.

Signature 	_JNIEnv::GetMethodID(_jclass*, char const*, char const*) | webrtc::videocapturemodule::DeviceInfoAndroid::NumberOfDevices() More Reports Search
UUID	8532fd8b-9657-43b2-932c-81c102130626
Date Processed	2013-06-26 11:50:53
Uptime	22
Install Age	9.2 minutes since version was first installed.
Install Time	2013-06-26 11:41:29
Product	FennecAndroid
Version	25.0a1
Build ID	20130625031238
Release Channel	nightly
OS	Android
OS Version	0.0.0 Linux #1 SMP PREEMPT Fri Nov 9 23:21:16 PST 2012 armv7l Lenovo/cm_k1/k1:4.1.2/JZO54K/eng.root.20121109.230342:userdebug/test-keys
Build Architecture	arm
Build Architecture Info	ARMv0
Crash Reason	SIGSEGV
Crash Address	0x2c
App Notes 	
AdapterDescription: 'NVIDIA Corporation -- NVIDIA Tegra -- OpenGL ES 2.0 14.01002 -- Model: K1, Product: cm_k1, Manufacturer: Lenovo, Hardware: ventana'
GL Layers! EGL? EGL+ GL Context? GL Context+ GL Layers+ 
nothumb Build
Lenovo K1
Processor Notes 	sp-processor03_phx1_mozilla_com_3859:2012; non-integer value of "SecondsSinceLastCrash"; exploitability tool: ERROR: unable to analyze dump
EMCheckCompatibility	True
Adapter Vendor ID	NVIDIA Corporation
Adapter Device ID	NVIDIA Tegra
Device	Lenovo K1
Android API Version	16 (REL)
Android CPU ABI	armeabi-v7a

Frame 	Module 	Signature 	Source
1 	_JNIEnv::GetMethodID 	android-ndk/platforms/android-9/arch-arm/usr/include/jni.h:605
2 	webrtc::videocapturemodule::DeviceInfoAndroid::NumberOfDevices 	media/webrtc/trunk/webrtc/modules/video_capture/android/
3 	webrtc::ViEInputManager::CreateCaptureDevice 	media/webrtc/trunk/webrtc/video_engine/
4 	webrtc::ViECaptureImpl::AllocateCaptureDevice 	media/webrtc/trunk/webrtc/video_engine/
5 	mozilla::MediaEngineWebRTCVideoSource::Allocate 	content/media/webrtc/MediaEngineWebRTCVideo.cpp:245
6 	mozilla::GetUserMediaRunnable::ProcessGetUserMedia 	dom/media/MediaManager.cpp:740
7 	mozilla::GetUserMediaRunnable::Run 	dom/media/MediaManager.cpp:601
8 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:626
9 	NS_ProcessNextEvent 	obj-firefox/xpcom/build/nsThreadUtils.cpp:238
10 	nsThread::ThreadFunc 	xpcom/threads/nsThread.cpp:264
11 	_pt_root 	nsprpub/pr/src/pthreads/ptthread.c:204

More reports at:*%2C+char+const*%2C+char+const*%29+|+webrtc%3A%3Avideocapturemodule%3A%3ADeviceInfoAndroid%3A%3ANumberOfDevices%28%29


4 years ago
Whiteboard: [getUserMedia][android-gum-]

Comment 1

4 years ago
A comment says: "WebRTC Reference app crashed."

Assuming it's a regression in 25.0a1/20130625, the regression range is:
It might be a regression from bug 868405.
Keywords: regression
Whiteboard: [getUserMedia][android-gum-] → [native-crash][getUserMedia][android-gum-]
Version: Trunk → 25 Branch

Comment 2

4 years ago
This is a weird crash because the errors checking in that function seems to be OK. Will probably need steps to reproduce in order to fix.


4 years ago
status-firefox24: --- → affected
Version: 25 Branch → 24 Branch
This appears to be a crash that's becoming popular. Can we try to get URLs here and try to get STR?
Keywords: steps-wanted


4 years ago
Keywords: needURLs

Comment 4

4 years ago
Looks like this could happen if AttachAndUseAndroidDeviceInfoObjects is called before SetAndroidObjects, or after a shutdown call of same.

But that's not supposed to happen, so again steps to reproduce would be nice.
no URL's associated with this crash.  Also note, only three crashes reported in the last 7 days
Keywords: needURLs


4 years ago
tracking-fennec: --- → ?
This is the only crash prominent within the last 7 days. Appears to be common enough over the nightly/aurora train in frequency over the weeks that have passed. That gives me indication that there are definitely users hitting this in a common enough use case, so let's keep a watch out for potential STR that could cause this crash.
tracking-fennec: ? → -
Past 7 days shows crashes from models:

- GT-P7510
- Nexus 4
- Aries
- L36h
- GT-I9505
Past 7 days crashes from devices:

- Samsung Galaxy Tab - GT-P7510
- Nexus 4
- (Don't know on Aries)
- Sony Xperia Z L36H
- Samsung Galaxy S4 - GT-I9505
Confirmed to be exactly the same root cause as bug 902431. Reduced STR:

1. On a Galaxy Nexus on Android 4.2 on Nightly, go to
2. Accept permissions
3. After the page reloads, accept permissions again

Result - crash seen with this stack
Keywords: steps-wanted


4 years ago
Keywords: reproducible


4 years ago
Depends on: 902431
Using the attachment test-case from bug 902431 (with gUM permissions default set as enabled)

- HTC One (Android 4.3, Google Play Edition)

- Samsung Galaxy Note II (Android 4.2)

- Samsung Galaxy SII (Android 4.1.2)
Top webrtc crasher, now with STR 100% reproducible. Likely the same root cause as bug 902431, but I'm keeping this separate until we confirm 100% that fixing one fixes the other.
tracking-fennec: - → ?
tracking-firefox24: --- → ?
tracking-firefox25: --- → ?
tracking-firefox26: --- → ?
Confirmed also on a Galaxy S3 on Android 4.1 that the STR given in reproduces the crash consistently 100%.


4 years ago
status-firefox23: --- → unaffected
tracking-firefox24: ? → +
tracking-firefox25: ? → +
tracking-firefox26: ? → +
tracking-fennec: ? → 24+
Assignee: nobody → gpascutto
This should be fixed by bug 902431. If it isn't, reopen the bug.
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla27


4 years ago

Comment 14

4 years ago

Comment 15

4 years ago
Believed to be fixed by bug 902431 so mirroring flags.
status-firefox24: affected → wontfix
status-firefox25: affected → fixed
status-firefox26: --- → fixed
You need to log in before you can comment on or make changes to this bug.