New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 619661 link

Starred by 1 user

Issue metadata

Status: Duplicate
Owner: ----
Closed: Jun 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 1
Type: Bug



Sign in to add a comment

MediaCodecBridge::fillInputBuffer crash

Project Member Reported by liber...@chromium.org, Jun 13 2016

Issue description


abour 650 crashes in M52 are in MediaCodecBridge::FillInputBuffer.  It's still around in M53.  About 40 out of all 63 that contain "AndroidVideoDecodeAccelerator" anywhere in the stack are this one.

M52 link:

https://crash.corp.google.com/browse?q=product.name%3D%27Chrome_Android%27%20AND%20product.version%20contains%20%2752.0.%27%20AND%20custom_data.ChromeCrashProto.ptype%3D%27gpu-process%27%20OMIT%20RECORD%20IF%20SUM(CrashedStackTrace.StackFrame.FunctionName%3D%27media%3A%3AMediaCodecBridge%3A%3AFillInputBuffer%27)%20%3D%200&ignore_case=false&enable_rewrite=false&omit_field_name=&omit_field_value=&omit_field_opt=&stbtiq=&reportid=&index=0

Thread 17 CRASHED [SIGSEGV @ 0x00000028 ] MAGIC SIGNATURE THREAD
0x0000007f6f74855c	(libmedia_jni.so + 0x0001f55c )	
0x0000007f6f74895c	(libmedia_jni.so + 0x0001f95c )	
0x0000007f6f74895c	(libmedia_jni.so + 0x0001f95c )	
0x0000007f6f7489b4	(libmedia_jni.so + 0x0001f9b4 )	
0x72a03788	(system@framework@boot.oat + 0x00bfd788 )	
0x0000007f7a98e814	(libart.so + 0x00298814 )	
0x0000007f7a9e8160	(libart.so + 0x002f2160 )	
0x0000007f7a95b064	(libart.so + 0x00265064 )	
0x0000007f59bca5a8	(libchrome.so -jni.h:636 )	_JNIEnv::CallObjectMethod
0x0000007f5aa09dac	(libchrome.so -media_codec_bridge.cc:65 )	media::MediaCodecBridge::FillInputBuffer
0x0000007f5aa1dae4	(libchrome.so -sdk_media_codec_bridge.cc:163 )	media::SdkMediaCodecBridge::QueueInputBuffer
0x0000007f5af734ec	(libchrome.so -android_video_decode_accelerator.cc:672 )	media::AndroidVideoDecodeAccelerator::QueueInput
 
Is this missing JNIEnv* env = AttachCurrentThread(); CHECK(env); ? it looks like it isn't called until after GetInputBuffer().

Comment 2 by w...@chromium.org, Jun 13 2016

This is pretty heavily weighted towards a few devices. Here's an internal bug tima opened about this: https://b.corp.google.com/u/1/issues/28751489

Comment 3 by w...@chromium.org, Jun 13 2016

Let me fix that link: http://b/28751489
Mergedinto: 610523
Status: Duplicate (was: Available)
Duplicate of issue 610523 then.

Sign in to add a comment