bilibili / bilibili/ijkplayer

部分机型在使用ijk播放器进行RTMP流直播几分钟后发生崩溃

Open
#2,008 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
C
Stars
33.2k
Forks
8.2k
PR merge metrics
No merged PRs in 30d

Description

使用ijk播放器在酷派大神F1和三星Galaxy A5等机型设备上,播放几分钟后就很容易出现崩溃,看了日志好像是跟ACodec有关,具体这块音视频业务我不是很熟,请问有遇到这种类似问题的吗?如何解决?谢谢。具体崩溃log如下:

09-20 17:05:32.455 14708-12195/? E/IJKMEDIA: Option ijkinject-opaque not found.
09-20 17:05:33.135 236-236/? E/SMD: DCD OFF
09-20 17:05:33.565 14708-12195/? E/IJKMEDIA: csd-0[39]: 00000001
09-20 17:05:33.565 14708-12195/? E/IJKMEDIA: csd-0[39]: 6742c028
09-20 17:05:33.565 14708-12195/? E/IJKMEDIA: csd-0[39]: da01e01e
09-20 17:05:33.565 14708-12195/? E/IJKMEDIA: csd-0[39]: 69a80868
09-20 17:05:33.565 14708-12195/? E/IJKMEDIA: csd-0[39]: 0a000003
09-20 17:05:33.565 14708-12195/? E/IJKMEDIA: csd-0[39]: 00020000
09-20 17:05:33.565 14708-12195/? E/IJKMEDIA: csd-0[39]: 0300651e
09-20 17:05:33.565 14708-12195/? E/IJKMEDIA: csd-0[39]: 30654000
09-20 17:05:33.565 14708-12195/? E/IJKMEDIA: csd-0[39]: 00000168
09-20 17:05:33.565 14708-12195/? E/IJKMEDIA: csd-0[39]: ce3c8000
09-20 17:05:33.675 244-666/? E/OMX_C2D: Destroy C2D instance
09-20 17:05:33.675 244-666/? E/OMX_C2D: Destroy C2D instance
09-20 17:05:33.685 244-244/? E/OMXNodeInstance: OMX_GetExtensionIndex OMX.google.android.index.storeMetaDataInBuffers failed
09-20 17:05:33.695 14708-12195/? E/OMXMaster: A component of name 'OMX.qcom.audio.decoder.aac' already exists, ignoring this one.
09-20 17:05:33.725 14708-12195/? E/OMXNodeInstance: OMX_GetExtensionIndex OMX.google.android.index.storeMetaDataInBuffers failed
09-20 17:05:33.815 14708-12195/? E/IJKMEDIA: configure acodec:0x1d9006be format:0x1d3006ee: surface:0x1d6006ce
09-20 17:05:33.865 14708-12396/? E/BufferQueue: [unnamed-14708-13] dequeueBuffer: BufferQueue has been abandoned!
09-20 17:05:33.865 14708-12396/? E/ACodec: dequeueBuffer failed.
09-20 17:05:33.865 14708-12396/? A/ACodec: frameworks/av/media/libstagefright/ACodec.cpp:3551 CHECK_EQ( mCodec->submitOutputMetaDataBuffer(),(status_t)OK) failed: -1004 vs. 0
**09-20 17:05:33.865 14708-12396/? A/libc: Fatal signal 6 (SIGABRT) at 0x00003974 (code=-6), thread 12396 (CodecLooper)**
09-20 17:05:35.055 816-914/? E/xxxxxxbtsdcard: checkUser: useridlist=null, currentuser=0
09-20 17:05:35.055 816-914/? E/xxxxxxbtsdcard: checkUser: useridlist=null, currentuser=0
09-20 17:05:35.055 816-914/? E/xxxxxxbtsdcard: checkUser: useridlist=null, currentuser=0
09-20 17:05:35.055 816-914/? E/xxxxxxbtsdcard: checkUser: useridlist=null, currentuser=0
09-20 17:05:35.115 816-1032/? E/SmartFaceService: onReceive: android.intent.action.CONFIGURATION_CHANGED
09-20 17:05:35.115 816-1032/? E/SmartFaceService: mFolderCoverOpened: (true, true) -> true
09-20 17:05:35.125 12451-12451/? E/dalvikvm: >>>>> Normal User
09-20 17:05:35.125 12451-12451/? E/dalvikvm: >>>>> com.qualcomm.logkit [ userId:0 | appId:10106 ]
09-20 17:05:35.125 816-816/? E/Tethering: No numeric data
09-20 17:05:35.165 816-12427/? E/android.os.Debug: !@Dumpstate > dumpstate -k -t -z -d -o /data/log/dumpstate_app_error
09-20 17:05:36.135 236-236/? E/SMD: DCD OFF
09-20 17:05:37.975 244-633/? E/audio_hw_primary: enable_NXP: turn off
09-20 17:05:39.135 236-236/? E/SMD: DCD OFF
09-20 17:05:41.225 1059-1059/? E/StatusBar.NetworkController_dual: updateTelephonySignalStrength: slot2 iconLevel = 4
09-20 17:05:42.135 236-236/? E/SMD: DCD OFF
09-20 17:05:43.665 816-1182/? E/Watchdog: !@Sync 2045
09-20 17:05:45.135 236-236/? E/SMD: DCD OFF
09-20 17:05:46.575 244-641/? E/OMXNodeInstance: !!! Observer died. Quickly, do something, ... anything...
09-20 17:05:46.585 816-2180/? A/ActivityManager: Service ServiceRecord{446f21a8 u0 com.huajiao/.vrservice.VrServiceCtrl} in process ProcessRecord{42eca870 14708:com.huajiao/u0a354} not same as in map: null

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the ACodec crash location shown in frameworks/av/media/libstagefright/ACodec.cpp and the surrounding BufferQueue and MediaCodec errors in the report. Reproduce the RTMP playback failure on the named Coolpad and Samsung devices, then document a verified cause and resolution or workaround.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, c
Domain
audio-video-rtc, mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.