android开发：ndk调用yolo，再用chaquopy调用python接口时，程序运行崩溃，提示与libomp.so 库有关的。

[caiyongrt]

error reporting：
Softversion: PD1806_A_9.8.22
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A Time: 2025-01-19 16:13:30
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A Build fingerprint: 'vivo/PD1806/PD1806:10/QP1A.190711.020/compiler10141718:user/release-keys'
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A Revision: '0'
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A ABI: 'arm64'
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A Timestamp: 2025-01-19 16:13:30+0800
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A pid: 28933, tid: 28999, name: pool-2-thread-1 >>> com.tencent.yolov8ncnn <<<
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A uid: 11292
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A x0 0000000000000000 x1 0000000000007147 x2 0000000000000006 x3 0000007222b81dd0
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A x4 74616d726f666e69 x5 74616d726f666e69 x6 74616d726f666e69 x7 656c70202c6e6f69
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A x8 00000000000000f0 x9 b2c581c1c8f245ec x10 0000000000000001 x11 0000000000000000
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A x12 fffffff0fffffbdf x13 6f6d20726f46202e x14 2065726f6d20726f x15 0000007222b81690
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A x16 00000073253ab738 x17 0000007325389f20 x18 000000721185d0e8 x19 0000000000007105
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A x20 0000000000007147 x21 00000000ffffffff x22 00000071f7ea9a48 x23 00000071f16d99b6
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A x24 00000071f7ea7e4f x25 00000071f7f2f000 x26 00000071f16d99b6 x27 0000000000000000
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A x28 00000072889c6810 x29 0000007222b81e70
2025-01-19 16:13:30.459 29030-29030 DEBUG pid-29030 A sp 0000007222b81db0 lr 000000732533b86c pc 000000732533b898
2025-01-19 16:13:30.460 29030-29030 DEBUG pid-29030 A
backtrace:
2025-01-19 16:13:30.460 29030-29030 DEBUG pid-29030 A NOTE: Function names and BuildId information is missing for some frames due
2025-01-19 16:13:30.460 29030-29030 DEBUG pid-29030 A NOTE: to unreadable libraries. For unwinds of apps, only shared libraries
2025-01-19 16:13:30.460 29030-29030 DEBUG pid-29030 A NOTE: found under the lib/ directory are readable.
2025-01-19 16:13:30.460 29030-29030 DEBUG pid-29030 A #00 pc 0000000000073898 /apex/com.android.runtime/lib64/bionic/libc.so (abort+160) (BuildId: 6aaa192fa70426ea767b3bcf55b19a30)
2025-01-19 16:13:30.460 29030-29030 DEBUG pid-29030 A #1 pc 000000000003cae4 /data/data/com.tencent.yolov8ncnn/files/chaquopy/AssetFinder/requirements/chaquopy/lib/libomp.so The problem still exists after the Chaquopy interface is simplified. The interface code is as follows:
public void PythonDetectRun(Bitmap curbitmap){
ByteArrayOutputStream stream = new ByteArrayOutputStream();
curbitmap.compress(Bitmap.CompressFormat.PNG, 100, stream);
byte[] imageData = stream.toByteArray();
PyObject module = mPython.getModule("cy");
}