Closed
Bug 887227
Opened 11 years ago
Closed 11 years ago
crash in webrtc::videocapturemodule::DeviceInfoAndroid::NumberOfDevices
Categories
(Core :: WebRTC: Audio/Video, defect)
Tracking
()
VERIFIED
FIXED
mozilla27
People
(Reporter: scoobidiver, Assigned: gcp)
References
Details
(Keywords: crash, regression, reproducible, Whiteboard: [native-crash][getUserMedia][android-gum-])
Crash Data
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 2.6.39.4_CyanogenMod_DHD #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 Lenovo/cm_k1/k1:4.1.2/JZO54K/eng.root.20121109.230342:userdebug/test-keys 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 0 libdvm.so libdvm.so@0x4ca90 1 libxul.so _JNIEnv::GetMethodID android-ndk/platforms/android-9/arch-arm/usr/include/jni.h:605 2 libxul.so webrtc::videocapturemodule::DeviceInfoAndroid::NumberOfDevices media/webrtc/trunk/webrtc/modules/video_capture/android/device_info_android.cc:66 3 libxul.so webrtc::ViEInputManager::CreateCaptureDevice media/webrtc/trunk/webrtc/video_engine/vie_input_manager.cc:195 4 libxul.so webrtc::ViECaptureImpl::AllocateCaptureDevice media/webrtc/trunk/webrtc/video_engine/vie_capture_impl.cc:121 5 libxul.so mozilla::MediaEngineWebRTCVideoSource::Allocate content/media/webrtc/MediaEngineWebRTCVideo.cpp:245 6 libxul.so mozilla::GetUserMediaRunnable::ProcessGetUserMedia dom/media/MediaManager.cpp:740 7 libxul.so mozilla::GetUserMediaRunnable::Run dom/media/MediaManager.cpp:601 8 libxul.so nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:626 9 libxul.so NS_ProcessNextEvent obj-firefox/xpcom/build/nsThreadUtils.cpp:238 10 libxul.so nsThread::ThreadFunc xpcom/threads/nsThread.cpp:264 11 libnss3.so _pt_root nsprpub/pr/src/pthreads/ptthread.c:204 12 libc.so libc.so@0x12eb6 13 libc.so libc.so@0x1260e More reports at: https://crash-stats.mozilla.com/report/list?signature=_JNIEnv%3A%3AGetMethodID%28_jclass*%2C+char+const*%2C+char+const*%29+|+webrtc%3A%3Avideocapturemodule%3A%3ADeviceInfoAndroid%3A%3ANumberOfDevices%28%29
Updated•11 years ago
|
Whiteboard: [getUserMedia][android-gum-]
Reporter | ||
Comment 1•11 years ago
|
||
A comment says: "WebRTC Reference app crashed." Assuming it's a regression in 25.0a1/20130625, the regression range is: http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=76820c6dff7b&tochange=bc569033125a It might be a regression from bug 868405.
Keywords: regression
Whiteboard: [getUserMedia][android-gum-] → [native-crash][getUserMedia][android-gum-]
Version: Trunk → 25 Branch
Assignee | ||
Comment 2•11 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.
Reporter | ||
Updated•11 years ago
|
status-firefox24:
--- → affected
Version: 25 Branch → 24 Branch
Comment 3•11 years ago
|
||
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
Assignee | ||
Comment 4•11 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.
Comment 5•11 years ago
|
||
no URL's associated with this crash. Also note, only three crashes reported in the last 7 days
Keywords: needURLs
Updated•11 years ago
|
tracking-fennec: --- → ?
Comment 6•11 years ago
|
||
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.
Updated•11 years ago
|
tracking-fennec: ? → -
Comment 7•11 years ago
|
||
Past 7 days shows crashes from models: - GT-P7510 - Nexus 4 - Aries - L36h - GT-I9505
Comment 8•11 years ago
|
||
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
Comment 9•11 years ago
|
||
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 https://bugzilla.mozilla.org/attachment.cgi?id=799865 2. Accept permissions 3. After the page reloads, accept permissions again Result - crash seen with this stack
Keywords: steps-wanted
Updated•11 years ago
|
Keywords: reproducible
Comment 10•11 years ago
|
||
Using the attachment test-case from bug 902431 (with gUM permissions default set as enabled) - HTC One (Android 4.3, Google Play Edition) https://crash-stats.mozilla.com/report/index/633411f2-b917-4848-a6c4-83efa2130906 - Samsung Galaxy Note II (Android 4.2) https://crash-stats.mozilla.com/report/index/38ad9343-f7c5-462e-bf71-fd19c2130906 - Samsung Galaxy SII (Android 4.1.2) https://crash-stats.mozilla.com/report/index/e65d02fc-214d-479b-bdf5-b34722130906
Comment 11•11 years ago
|
||
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:
--- → ?
Comment 12•11 years ago
|
||
Confirmed also on a Galaxy S3 on Android 4.1 that the STR given in https://bugzilla.mozilla.org/show_bug.cgi?id=887227#c9 reproduces the crash consistently 100%.
Updated•11 years ago
|
status-firefox23:
--- → unaffected
Updated•11 years ago
|
tracking-fennec: ? → 24+
Updated•11 years ago
|
Assignee: nobody → gpascutto
Comment 13•11 years ago
|
||
This should be fixed by bug 902431. If it isn't, reopen the bug.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Target Milestone: --- → mozilla27
Updated•11 years ago
|
Status: RESOLVED → VERIFIED
Comment 14•11 years ago
|
||
Thanks!
Assignee | ||
Comment 15•11 years ago
|
||
Believed to be fixed by bug 902431 so mirroring flags.
You need to log in
before you can comment on or make changes to this bug.
Description
•