在我的应用程序中将视频作为块上传时，出现以下错误并且应用程序崩溃。我创建了一个一次性工作管理器来处理视频的分块和上传。每次到达第 152 个块时，都会发生此崩溃。我正在使用 CoroutineWorker，并且每个块响应都有数据库更新。
出于测试目的，我已将分块移至视图模型，并为每个块创建一个工作管理器。在这种情况下它不会崩溃，只有在有场景的情况下才会崩溃。
我没有在我的应用程序中执行任何与 NDK 相关的操作。尝试了其他人类似问题解决方案中看到的许多方法，但没有任何效果。任何帮助将不胜感激。
Fatal signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0x6cc2ca78a0 in tid 10169 (DefaultDispatch), pid 7121 (tionapp.staging)
2023-08-03 15:10:00.481 11906-11906 DEBUG pid-11906 A Cmdline: com.sample.myapp.staging
2023-08-03 15:10:00.481 11906-11906 DEBUG pid-11906 A pid: 7121, tid: 10169, name: DefaultDispatch >>> com.sample.myapp.staging <<<
2023-08-03 15:10:00.481 11906-11906 DEBUG pid-11906 A #22 pc 00000000001684e2 /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (okhttp3.RequestBody$Companion$asRequestBody$1.writeTo+62)
2023-08-03 15:10:00.481 11906-11906 DEBUG pid-11906 A #25 pc 0000000000162fe6 /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (okhttp3.MultipartBody.writeTo+30)
2023-08-03 15:10:00.481 11906-11906 DEBUG pid-11906 A #29 pc 000000000017a500 /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (okhttp3.internal.connection.ConnectInterceptor.intercept+100)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #36 pc 0000000000186108 /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept+164)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #43 pc 000000000000c792 /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (com.sample.myapp.network.NetworkModule$TokenInterceptor.intercept+150)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #46 pc 000000000000c5f2 /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (com.sample.myapp.network.NetworkModule$JsonResponseInterceptor.intercept+102)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #50 pc 000000000017d866 /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (okhttp3.internal.connection.RealCall.execute+94)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #52 pc 00000000002058be /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (retrofit2.OkHttpCall.execute+90)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #54 pc 000000000020ea2c /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (retrofit2.adapter.rxjava2.CallExecuteObservable.subscribeActual+84)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #56 pc 0000000000443a80 /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (io.reactivex.Observable.subscribe+64)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #58 pc 000000000020e522 /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (retrofit2.adapter.rxjava2.BodyObservable.subscribeActual+22)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #60 pc 0000000000443a80 /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (io.reactivex.Observable.subscribe+64)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #62 pc 00000000004d77b2 /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (io.reactivex.internal.operators.observable.ObservableSingleSingle.subscribeActual+26)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #64 pc 00000000004470ce /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (io.reactivex.Single.subscribe+62)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #66 pc 00000000004f2cd6 /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (io.reactivex.internal.operators.single.SingleMap.subscribeActual+26)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #68 pc 00000000004470ce /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (io.reactivex.Single.subscribe+62)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #70 pc 00000000004ef652 /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (io.reactivex.internal.operators.single.SingleDoOnError.subscribeActual+22)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #72 pc 00000000004470ce /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (io.reactivex.Single.subscribe+62)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #74 pc 00000000004f332a /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (io.reactivex.internal.operators.single.SingleOnErrorReturn.subscribeActual+22)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #76 pc 00000000004470ce /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (io.reactivex.Single.subscribe+62)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #78 pc 0000000000446e7c /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (io.reactivex.Single.subscribe+64)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #79 pc 0000000002214a0c /memfd:jit-cache (deleted) (com.sample.myapp.services.UploadVideoWorkManager.upload+2364)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #81 pc 0000000000013bee /data/app/~~EyOQK-IGM1Tjn1JUuoViFg==/com.sample.myapp.staging--XeqY505j54nitjwaSL3xA==/base.apk (com.sample.myapp.services.UploadVideoWorkManager.access$upload+22)
2023-08-03 15:10:00.482 11906-11906 DEBUG pid-11906 A #82 pc 0000000002149f8c /memfd:jit-cache (deleted) (com.sample.myapp.services.UploadVideoWorkManager$upload$1.invoke+4332)
注意：我正在使用 Jackson 将数组转换为字符串，并将字符串转换为数组以保存在数据库中。尝试将其注释掉以检查这是否是问题所在，但应用程序仍然崩溃。根据分析器内存，CPU 和能源也并不多。