Comments (2)
arm64-v8a架构的有so吗?
from ffmpegvideorange2.
2023-03-27 14:25:36.314 17014-17272 FFmpeg: com.example.ffmpegvideorange2 E 释放helper
2023-03-27 14:25:36.314 17014-17272 FFmpeg: com.example.ffmpegvideorange2 E 释放kzgPlayerStatus
2023-03-27 14:25:36.314 17014-17272 FFmpeg: com.example.ffmpegvideorange2 E 释放FFmpeg 完成
2023-03-27 14:25:36.314 17014-17272 FFmpeg: com.example.ffmpegvideorange2 E 开始释放FAvFrameHelper
2023-03-27 14:25:36.314 17014-17272 FFmpeg: com.example.ffmpegvideorange2 E 释放avFormatContext
2023-03-27 14:25:36.314 17014-17238 libc com.example.ffmpegvideorange2 A FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x758f68b2a0)
2023-03-27 14:25:36.315 17014-17238 libc com.example.ffmpegvideorange2 A Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 17238 (Thread-89), pid 17014 (mpegvideorange2)
2023-03-27 14:25:36.315 17014-17272 FFmpeg: com.example.ffmpegvideorange2 E 释放helper
2023-03-27 14:25:36.315 17014-17272 FFmpeg: com.example.ffmpegvideorange2 E 释放kzgPlayerStatus
2023-03-27 14:25:36.315 17014-17272 FFmpeg: com.example.ffmpegvideorange2 E 释放FAvFrameHelper结束
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A Softversion: PD1932_A_7.9.19
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A Time: 2023-03-27 14:25:36
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A Build fingerprint: 'vivo/PD1932/PD1932:10/QP1A.190711.020/compiler11181125:user/release-keys'
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A Revision: '0'
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A ABI: 'arm64'
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A Timestamp: 2023-03-27 14:25:36+0800
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A pid: 17014, tid: 17238, name: Thread-89 >>> com.example.ffmpegvideorange2 <<<
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A uid: 10884
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A Abort message: 'FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x758f68b2a0)'
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A x0 0000000000000000 x1 0000000000004356 x2 0000000000000006 x3 000000750cff59b0
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A x4 0000000000000000 x5 0000000000000000 x6 0000000000000000 x7 0000000000000038
2023-03-27 14:25:36.394 17275-17275 DEBUG pid-17275 A x8 00000000000000f0 x9 8db53e64d76ed832 x10 0000000000000001 x11 0000000000000000
2023-03-27 14:25:36.395 17275-17275 DEBUG pid-17275 A x12 fffffff0fffffbdf x13 00000000642136e0 x14 00121ac108f7d98c x15 0000aaacd4943db3
2023-03-27 14:25:36.395 17275-17275 DEBUG pid-17275 A x16 000000761412c738 x17 000000761410af20 x18 0000007515002000 x19 0000000000004276
2023-03-27 14:25:36.395 17275-17275 DEBUG pid-17275 A x20 0000000000004356 x21 00000000ffffffff x22 000000750cff6060 x23 000000750cff5dd8
2023-03-27 14:25:36.395 17275-17275 DEBUG pid-17275 A x24 000000750cff5d50 x25 000000750cff5d50 x26 000000750cff6020 x27 00000075315e4020
2023-03-27 14:25:36.395 17275-17275 DEBUG pid-17275 A x28 00000075315e26c0 x29 000000750cff5a50
2023-03-27 14:25:36.395 17275-17275 DEBUG pid-17275 A sp 000000750cff5990 lr 00000076140bc86c pc 00000076140bc898
2023-03-27 14:25:36.395 17275-17275 DEBUG pid-17275 A
backtrace:
2023-03-27 14:25:36.395 17275-17275 DEBUG pid-17275 A #00 pc 0000000000073898 /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: 6aaa192fa70426ea767b3bcf55b19a30)
2023-03-27 14:25:36.395 17275-17275 DEBUG pid-17275 A #1 pc 00000000000d84f0 /apex/com.android.runtime/lib64/bionic/libc.so (__fortify_fatal(char const*, ...)+120) (BuildId: 6aaa192fa70426ea767b3bcf55b19a30)
2023-03-27 14:25:36.395 17275-17275 DEBUG pid-17275 A #2 pc 00000000000d7b90 /apex/com.android.runtime/lib64/bionic/libc.so (HandleUsingDestroyedMutex(pthread_mutex_t*, char const*)+52) (BuildId: 6aaa192fa70426ea767b3bcf55b19a30)
2023-03-27 14:25:36.395 17275-17275 DEBUG pid-17275 A #3 pc 00000000000d7a44 /apex/com.android.runtime/lib64/bionic/libc.so (pthread_mutex_lock+228) (BuildId: 6aaa192fa70426ea767b3bcf55b19a30)
2023-03-27 14:25:36.395 17275-17275 DEBUG pid-17275 A #4 pc 00000000000d6400 /apex/com.android.runtime/lib64/bionic/libc.so (pthread_cond_wait+72) (BuildId: 6aaa192fa70426ea767b3bcf55b19a30)
2023-03-27 14:25:36.395 17275-17275 DEBUG pid-17275 A #05 pc 000000000003f34c /data/app/com.example.ffmpegvideorange2-Srp3XjbqCE_Syk3Gxalb_g==/base.apk!libnative-lib.so (offset 0x11e0000) (SafeQueue::getAvPacket(AVPacket*)+300) (BuildId: 60c45e90ebc8a895996d33bc47eb7dcb6b7839a0)
2023-03-27 14:25:36.396 17275-17275 DEBUG pid-17275 A #06 pc 0000000000039228 /data/app/com.example.ffmpegvideorange2-Srp3XjbqCE_Syk3Gxalb_g==/base.apk!libnative-lib.so (offset 0x11e0000) (FAvFrameHelper::decodeFrameFromQueue()+184) (BuildId: 60c45e90ebc8a895996d33bc47eb7dcb6b7839a0)
2023-03-27 14:25:36.396 17275-17275 DEBUG pid-17275 A #07 pc 0000000000036640 /data/app/com.example.ffmpegvideorange2-Srp3XjbqCE_Syk3Gxalb_g==/base.apk!libnative-lib.so (offset 0x11e0000) (startGetFrame(void*)+28) (BuildId: 60c45e90ebc8a895996d33bc47eb7dcb6b7839a0)
2023-03-27 14:25:36.396 17275-17275 DEBUG pid-17275 A #08 pc 00000000000d6eb0 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+36) (BuildId: 6aaa192fa70426ea767b3bcf55b19a30)
2023-03-27 14:25:36.396 17275-17275 DEBUG pid-17275 A #09 pc 0000000000075314 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: 6aaa192fa70426ea767b3bcf55b19a30)
2023-03-27 14:25:37.121 17290-17290 mpegvideorange pid-17290 E Unknown bits set in runtime_flags: 0x8000
2023-03-27 14:25:37.259 17290-17290 kzg com.example.ffmpegvideorange2 E ******************attachBaseContext
2023-03-27 14:25:37.259 17290-17290 kzg com.example.ffmpegvideorange2 E ******************attachBaseContext
2023-03-27 14:25:37.260 17290-17290 kzg com.example.ffmpegvideorange2 E ******************通过反射调用moduleApplication的attach方法
2023-03-27 14:25:37.271 17290-17328 VPerformance com.example.ffmpegvideorange2 E Fail to get file list com.example.ffmpegvideorange2
2023-03-27 14:25:37.272 17290-17328 VPerformance com.example.ffmpegvideorange2 E Fail to get file list com.example.ffmpegvideorange2
2023-03-27 14:25:37.273 17290-17328 VPerformance com.example.ffmpegvideorange2 E Fail to get file list oat
报错,像是线程锁的问题
from ffmpegvideorange2.
Related Issues (4)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ffmpegvideorange2.