视频过程中，出现系统崩溃弹窗

wanzongyong · poston 2020-8-5 11:38

我们demo中在接收到回调时执行了locationTools.stopLocation();你把这个注释了。还有看看为啥在使用内网服务时会不断回调OnPasvDialogEvent-BVCU_EVENT_DIALOG.BVCU_EVENT_DIALOG_CLOSE:-if (channelIndex == BVCU_SubDev.BVCU_SUBDEV_INDEXMAJOR_MIN_GPS && dir == 0) {

王.studio · poston 2020-8-5 11:32

wanzongyong post on2020-8-5 11:00
从日志里看并没有我们提供的库的错误信息，你的程序com.longway.xianchang:remote进程是做什么的

我之前打印的东西里有看到在使用我们的内网服务时，会不断的回调的OnPasvDialogEvent-BVCU_EVENT_DIALOG.BVCU_EVENT_DIALOG_CLOSE:-if (channelIndex == BVCU_SubDev.BVCU_SUBDEV_INDEXMAJOR_MIN_GPS && dir == 0) {

王.studio · poston 2020-8-5 11:27

wanzongyong post on2020-8-5 11:00
从日志里看并没有我们提供的库的错误信息，你的程序com.longway.xianchang:remote进程是做什么的

这个问题我之前咨询过大牛，说是远程进程出了问题。远程进程调用了native方法。他没看我的代码，猜测应该是参数传值传错了

wanzongyong · poston 2020-8-5 11:25

你把定位相关的代码注释，在接收到GPS通道关闭的通知时不做处理看看还会不会出现崩溃提示

wanzongyong · poston 2020-8-5 11:23

我们DEMO中:remote是百度地图的进程，你看看你们程序里是不是也是的，<service android:name="com.baidu.location.f" android:enabled="true" android:process=":remote">，在AndroidManifest.xml中能看到。结合你说的现象，在接收到GPS通道关闭的通知时出现崩溃提示，可能和地图有关。

王.studio · poston 2020-8-5 11:22

wanzongyong post on2020-8-5 11:00
从日志里看并没有我们提供的库的错误信息，你的程序com.longway.xianchang:remote进程是做什么的

这个remote进程是咱们的视频服务里，使用的百度定位服务

<service android:name="com.baidu.location.f" android:enabled="true" android:process=":remote">
</service>

copycode

wanzongyong · poston 2020-8-5 11:00

从日志里看并没有我们提供的库的错误信息，你的程序com.longway.xianchang:remote进程是做什么的

王.studio · poston 2020-8-5 10:57

wanzongyong post on2020-8-5 09:53
这个崩溃不是java代码的崩溃，应该是动态库的崩溃，从上面的截图里看libart.so是系统的，不知道下面没截到 ...

A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x50696271 in tid 14339 (pool-1-thread-1)
08-05 10:40:15.862 14420-14420/? A/AEE/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Hi-Target/full_tdc1609/tdc1609:6.0/MRA58K/1505979351:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 14288, tid: 14339, name: pool-1-thread-1 >>> com.longway.xianchang:remote <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x50696271
08-05 10:40:15.885 14420-14420/? A/AEE/DEBUG: r0 59767272 r1 ea3f5c00 r2 00000018 r3 50696261
r4 50696261 r5 00000028 r6 12ecb000 r7 ebc37800
r8 ebc37828 r9 00000003 sl 12ecb028 fp 12ecb000
ip 00000054 sp dee525d0 lr 00000002 pc f462b9a2 cpsr 200f0030
08-05 10:40:15.891 14420-14420/? A/AEE/DEBUG: backtrace:
08-05 10:40:15.892 14420-14420/? A/AEE/DEBUG: #00 pc 0017b9a2 /system/lib/libart.so (_ZN3art2gc9allocator8RosAlloc9RevokeRunEPNS_6ThreadEjPNS2_3RunE+225)
#01 pc 0017bbe9 /system/lib/libart.so (_ZN3art2gc9allocator8RosAlloc21RevokeThreadLocalRunsEPNS_6ThreadE+480)
#02 pc 001bc781 /system/lib/libart.so (_ZN3art2gc4Heap24RevokeThreadLocalBuffersEPNS_6ThreadE+20)
#03 pc 00337ded /system/lib/libart.so (_ZN3art6Thread7DestroyEv+1436)
#04 pc 003463a3 /system/lib/libart.so (_ZN3art10ThreadList10UnregisterEPNS_6ThreadE+118)
#05 pc 0033f301 /system/lib/libart.so (_ZN3art6Thread14CreateCallbackEPv+600)
#06 pc 0004078b /system/lib/libc.so (_ZL15__pthread_startPv+30)
#07 pc 0001a031 /system/lib/libc.so (__start_thread+6)
08-05 10:41:35.918 14425-14475/? A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x61335759 in tid 14475 (pool-1-thread-1)
08-05 10:41:35.923 14535-14535/? A/AEE/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Hi-Target/full_tdc1609/tdc1609:6.0/MRA58K/1505979351:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 14425, tid: 14475, name: pool-1-thread-1 >>> com.longway.xianchang:remote <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x61335759
08-05 10:41:35.935 14535-14535/? A/AEE/DEBUG: r0 e71a5fa8 r1 00000068 r2 e71a7bc8 r3 61335759
r4 00000000 r5 00000040 r6 00000001 r7 e71a60e0
r8 ea3f4800 r9 00000004 sl 00000004 fp 12da3000
ip 00000001 sp dee51b70 lr f462a8c9 pc f46291b2 cpsr 600f0030
08-05 10:41:35.939 14535-14535/? A/AEE/DEBUG: backtrace:
#00 pc 001791b2 /system/lib/libart.so (_ZNSt3__113__tree_removeIPNS_16__tree_node_baseIPvEEEEvT_S5_+209)
#01 pc 0017a8c5 /system/lib/libart.so (_ZN3art2gc9allocator8RosAlloc9RefillRunEPNS_6ThreadEj+560)
#02 pc 0017ac3f /system/lib/libart.so (_ZN3art2gc9allocator8RosAlloc12AllocFromRunEPNS_6ThreadEjPjS5_S5_+498)
08-05 10:41:35.940 14535-14535/? A/AEE/DEBUG: #03 pc 002a88c1 /system/lib/libart.so (_ZN3art6mirror6String21AllocFromModifiedUtf8EPNS_6ThreadEiPKc+1380)
#04 pc 0033d969 /system/lib/libart.so (_ZN3art6Thread42InternalStackTraceToStackTraceElementArrayERKNS_33ScopedObjectAccessAlreadyRunnableEP8_jobjectP13_jobjectArrayPi+368)
#05 pc 002cc371 /system/lib/libart.so (_ZN3artL29Throwable_nativeGetStackTraceEP7_JNIEnvP7_jclassP8_jobject+24)
#06 pc 023b0ca9 /system/framework/arm/boot.oat (offset 0x2381000)
--------- beginning of system[code]E/KernelCpuSpeedReader: cpu4 time_in_state not exist, is it a BUG??!!
08-05 10:53:04.571 1073-1091/? E/KernelCpuSpeedReader: cpu4 time_in_state not exist, is it a BUG??!!
08-05 10:53:04.657 1073-1089/? E/KernelCpuSpeedReader: cpu4 time_in_state not exist, is it a BUG??!!
08-05 10:53:04.661 1073-1091/? E/KernelCpuSpeedReader: cpu4 time_in_state not exist, is it a BUG??!!
08-05 10:53:05.996 1419-1419/? E/ActivityThread: Service com.android.providers.media.MtpService has leaked IntentReceiver com.android.providers.media.MtpService$3@e923629 that was originally registered here. Are you missing a call to unregisterReceiver()?
android.app.IntentReceiverLeaked: Service com.android.providers.media.MtpService has leaked IntentReceiver com.android.providers.media.MtpService$3@e923629 that was originally registered here. Are you missing a call to unregisterReceiver()?
at android.app.LoadedApk$ReceiverDispatcher.<init>(LoadedApk.java:959)
at android.app.LoadedApk.getReceiverDispatcher(LoadedApk.java:728)
at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1177)
at android.app.ContextImpl.registerReceiver(ContextImpl.java:1157)
at android.app.ContextImpl.registerReceiver(ContextImpl.java:1151)
at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:554)
at com.android.providers.media.MtpService.onCreate(MtpService.java:101)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:3026)
at android.app.ActivityThread.-wrap4(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1552)
at android.os.Handler.dispatchMessage(Handler.java:111)
at android.os.Looper.loop(Looper.java:207)
at android.app.ActivityThread.main(ActivityThread.java:5692)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:888)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:749)
08-05 10:53:13.332 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:13.333 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:14.280 319-664/? E/MAL-Daemon: ( rds_ru_3gpp_status_ind, 1421) [RDS-E][RU][EVENT_RU_DM_3GPP_STATUS_IND] Invalid u43gpp_status:0x6
08-05 10:53:14.336 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:14.337 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:15.342 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:15.343 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:15.877 3067-3067/? E/DCloudApplication: onTrimMemory
08-05 10:53:15.881 7295-7295/? E/DCloudApplication: onTrimMemory
08-05 10:53:16.558 319-686/? E/MAL-Daemon: (void* rilproxy_task_hdl(, 439) rilproxy_task_hdl(), receive event = 401
08-05 10:53:16.832 319-664/? E/MAL-Daemon: ( rds_ru_3gpp_status_ind, 1421) [RDS-E][RU][EVENT_RU_DM_3GPP_STATUS_IND] Invalid u43gpp_status:0x6
08-05 10:53:18.350 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:18.351 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:19.354 319-664/? E/MAL-Daemon: ( rds_ru_3gpp_status_ind, 1421) [RDS-E][RU][EVENT_RU_DM_3GPP_STATUS_IND] Invalid u43gpp_status:0x6
08-05 10:53:19.386 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:19.386 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:20.380 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:20.381 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:21.875 319-664/? E/MAL-Daemon: ( rds_ru_3gpp_status_ind, 1421) [RDS-E][RU][EVENT_RU_DM_3GPP_STATUS_IND] Invalid u43gpp_status:0x6
08-05 10:53:24.395 319-664/? E/MAL-Daemon: ( rds_ru_3gpp_status_ind, 1421) [RDS-E][RU][EVENT_RU_DM_3GPP_STATUS_IND] Invalid u43gpp_status:0x6
08-05 10:53:24.436 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:24.437 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:26.401 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:26.402 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:26.559 319-686/? E/MAL-Daemon: (void* rilproxy_task_hdl(, 439) rilproxy_task_hdl(), receive event = 401
08-05 10:53:26.955 319-664/? E/MAL-Daemon: ( rds_ru_3gpp_status_ind, 1421) [RDS-E][RU][EVENT_RU_DM_3GPP_STATUS_IND] Invalid u43gpp_status:0x6
08-05 10:53:29.412 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:29.428 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:29.473 319-664/? E/MAL-Daemon: ( rds_ru_3gpp_status_ind, 1421) [RDS-E][RU][EVENT_RU_DM_3GPP_STATUS_IND] Invalid u43gpp_status:0x6
08-05 10:53:30.417 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:30.419 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:31.995 319-664/? E/MAL-Daemon: ( rds_ru_3gpp_status_ind, 1421) [RDS-E][RU][EVENT_RU_DM_3GPP_STATUS_IND] Invalid u43gpp_status:0x6
08-05 10:53:34.433 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:34.434 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:34.515 319-664/? E/MAL-Daemon: ( rds_ru_3gpp_status_ind, 1421) [RDS-E][RU][EVENT_RU_DM_3GPP_STATUS_IND] Invalid u43gpp_status:0x6
08-05 10:53:35.438 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:35.456 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:36.559 319-686/? E/MAL-Daemon: (void* rilproxy_task_hdl(, 439) rilproxy_task_hdl(), receive event = 401
08-05 10:53:37.035 319-664/? E/MAL-Daemon: ( rds_ru_3gpp_status_ind, 1421) [RDS-E][RU][EVENT_RU_DM_3GPP_STATUS_IND] Invalid u43gpp_status:0x6
08-05 10:53:39.463 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:39.463 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:39.595 319-664/? E/MAL-Daemon: ( rds_ru_3gpp_status_ind, 1421) [RDS-E][RU][EVENT_RU_DM_3GPP_STATUS_IND] Invalid u43gpp_status:0x6
08-05 10:53:40.456 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
08-05 10:53:40.457 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt

copycode

[/code]

wanzongyong · poston 2020-8-5 09:53

这个崩溃不是java代码的崩溃，应该是动态库的崩溃，从上面的截图里看libart.so是系统的，不知道下面没截到的部分有没有我们提供的库，所以需要更全的日志信息

wanzongyong · poston 2020-8-5 09:50

这张图片里有崩溃信息，但是截图不全，能否截一个全的图看看，或者把日志拷贝一下

		autoLogin	forgetPW
passwd			registerNow

视频过程中，出现系统崩溃弹窗

本帖子中包含更多资源

viewedForum