mobile CCTV,mobile surveillance,police body worn cameras

标题: 视频过程中，出现系统崩溃弹窗 [打印本页]
author: 王.studio    time: 2020-7-30 17:05
标题: 视频过程中，出现系统崩溃弹窗
视频过程中 不断回调OnpasvDialogCmd 和OnPasvDialogEvent接口  回调数次后，出现程序停止运行，但实际上，程序仍在联通，pc端依然可看到移动端的视频画面。
据分析 OnpasvDialogCmd 和OnPasvDialogEvent接口  应该只在切换通道 或者开关视频时会调用  --这点需要咱们这里再核实下。 但目前会不断触发，不知道原因。如果 这些接口不被反复触发，则推测不出现系统崩溃弹窗
author: besovideo    time: 2020-7-30 17:09
MCP SDK？
author: 王.studio    time: 2020-7-30 17:12
besovideo post on2020-7-30 17:09
MCP SDK？

是demo程序 集成在了我们系统里
author: wanzongyong    time: 2020-7-30 17:18
OnpasvDialogCmd 和OnPasvDialogEvent接口回调的参数：pParam.pDialogParam.pTarget[0].iIndexMajor表示通道号，一般视频通道默认是0，iEventCode表示此处回调的动作是打开/关闭通道或切换通道状态。通过王工之前提供的日志来看,频繁回调的是GPS通道，你们程序出现的崩溃提示应该先抓到崩溃日志看看具体的崩溃原因，看看是否与这个回调有关系。
author: 王.studio    time: 2020-7-31 10:27
昨天在后续的测试中  出现了 刚刚接收到视频请求 打开视频界面，但秒断开的情况，打印代码 走了：
  1. OnSessionEvent方法的：
  2. if (iEventCode == BVCU_EventCode.BVCU_EVENT_SESSION_CLOSE) {
  3.     boolean isLogout = false;
  4.     if (iResult == BVCU_Result.BVCU_RESULT_S_OK) {
  5.         showToastByHandler("退出成功");
  6.         isLogin = false;
  7.         isLogout = true;
  8.     } else {
  9.         Log.i("ttt","-----------iResult:"+iResult);
  10.         showToastByHandler("退出失败");
  11.         isLogout = false;
  12.         //2020.7.30莫名奇妙出现问题  登陆秒退 顾添加
  13.         isLogin = false;
  14.     }
copycode
里的 else方法 今天测试依然每次都调这个。。无法正常视频
author: 王.studio    time: 2020-7-31 10:28
想问下 什么情况可能导致这个问题出现，暂时我们这块没排查出来问题产生的原因
author: wanzongyong    time: 2020-7-31 10:43
王.studio post on2020-7-31 10:28
想问下 什么情况可能导致这个问题出现，暂时我们这块没排查出来问题产生的原因

OnSessionEvent是登录状态回调，iEventCode == BVCU_EventCode.BVCU_EVENT_SESSION_CLOSE表示下线，iResult == BVCU_Result.BVCU_RESULT_S_OK表示正常手动注销下线，iResult为其他值时表示异常下线。你们根据测试现象可以确定每次异常下线都是打开视频时出现的吗，每次下线的iResult是多少，都一样吗？
author: 王.studio    time: 2020-7-31 10:46
wanzongyong post on2020-7-31 10:43
OnSessionEvent是登录状态回调，iEventCode == BVCU_EventCode.BVCU_EVENT_SESSION_CLOSE表示下线，iResu ...

-65517
基本就是一打开视频 就掉 或者 视频10s上下 就掉线 就出现了 -65517  每次都是先出现这个  然后之后 不断的回调我之前反应的关闭接口，又打印出别的值
author: wanzongyong    time: 2020-7-31 10:56
王.studio post on2020-7-31 10:46
-65517
基本就是一打开视频 就掉 或者 视频10s上下 就掉线 就出现了 -65517  每次都是先出现这个  然后 ...

每次下线后还一直回调OnPasvDialogEvent，pParam.pDialogParam.pTarget[0].iIndexMajor == BVCU_SUBDEV_INDEXMAJOR_MIN_GPS？又打印出别的值是什么意思？
author: 王.studio    time: 2020-8-5 08:59
wanzongyong post on2020-7-31 10:56
每次下线后还一直回调OnPasvDialogEvent，pParam.pDialogParam.pTarget[0].iIndexMajor == BVCU_SUBDEV_I ...

之前 一直是 先打印了 -65517  然后紧接着会不断的打印65536
author: 王.studio    time: 2020-8-5 09:01
今天我们的内网通道刚好，我测试了下 ，刚刚没有报-65517  它是不断的在回调
OnPasvDialogEvent hDialog ：14 iEventCode : 3 pParam : {"iResult":0,"pDialogParam":{"iAVStreamDir":0,"iSize":0,"iTargetCount":1,"pTarget":[{"iIndexMajor":65536,"iIndexMinor":0,"szID":""}],"pUserData":0.0}}
08-05 09:00:27.818 8805-8882/com.longway.xianchang D/ttt: DIALOG_CLOSE命令  channelIndex=65536
    (channelIndex == BVCU_SubDev.BVCU_SUBDEV_INDEXMAJOR_MIN_CHANNEL):false
    (channelIndex == BVCU_SubDev.BVCU_SUBDEV_INDEXMAJOR_MIN_GPS && dir == 0) ：true
这个gps的信息，然后会出现 很抱歉，“”已停止运行
author: 王.studio    time: 2020-8-5 09:03
我打印了下报错
author: 王.studio    time: 2020-8-5 09:09
王.studio post on2020-8-5 09:03
我打印了下报错

111111111111
author: 王.studio    time: 2020-8-5 09:23
王.studio post on2020-8-5 09:09
111111111111

直接看 verbose  打印了这些：
  1. give LatencyToken 37654, 775
  2. 08-05 09:17:33.686 8805-8805/com.longway.xianchang I/CameraFramework: handleMessage: 16
  3. 08-05 09:17:33.691 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onInputBufferFilled ID 12 w/ time 1596590253686000 eos 0 mode 1 err 0
  4. 08-05 09:17:33.700 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onOutputBufferDrained ID 12
  5. 08-05 09:17:33.702 8805-9075/com.longway.xianchang D/ACodec: give LatencyToken 37655, 1528
  6. 08-05 09:17:33.703 8805-8824/com.longway.xianchang I/art: Background sticky concurrent mark sweep GC freed 158(7KB) AllocSpace objects, 8(3MB) LOS objects, 8% free, 38MB/42MB, paused 8.666ms total 17.814ms
  7. 08-05 09:17:33.738 8805-8805/com.longway.xianchang I/CameraFramework: handleMessage: 16
  8. 08-05 09:17:33.746 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onInputBufferFilled ID 1 w/ time 1596590253740000 eos 0 mode 1 err 0
  9. 08-05 09:17:33.748 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onOutputBufferDrained ID 13
  10. 08-05 09:17:33.752 8805-9075/com.longway.xianchang D/ACodec: give LatencyToken 37656, 4797
  11. 08-05 09:17:33.774 8805-8898/com.longway.xianchang I/PUDialog: close a dialog! hDialog = 31,channelIdx = 65536
  12. 08-05 09:17:33.776 8805-8805/com.longway.xianchang I/CameraFramework: handleMessage: 16
  13. 08-05 09:17:33.780 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onInputBufferFilled ID 2 w/ time 1596590253777000 eos 0 mode 1 err 0
  14. 08-05 09:17:33.782 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onOutputBufferDrained ID 14
copycode
  1. I/CUGlobal: pMsg->iAction = 11
  2.     File:jni-r19c/../jni/CUGlobal.cpp,Func = handleThreadMsg, begin
  3. 08-05 09:17:33.784 8805-8880/com.longway.xianchang I/PUDialog: test1 SAVCodec_Close res = -65535
  4.     file = jni-r19c/../jni/PUDialog.cpp, Error line = 574,result = -65535
  5.     pID = gps dialog close**********************
  6. 08-05 09:17:33.784 8805-8880/com.longway.xianchang I/YateMsgHandler: ------------------>PostToJavaHandler prot.sm.dialog.pasv.event
  7. 08-05 09:17:33.786 8805-8880/com.longway.xianchang I/YateMsgHandler: ------------------>S_ID -> prot.sm.dialog.pasv.event
  8. 08-05 09:17:33.787 8805-9075/com.longway.xianchang D/ACodec: give LatencyToken 37657, 970
  9. 08-05 09:17:33.787 8805-8880/com.longway.xianchang I/YateMsgHandler: ------------------>S_RESULT -> {
  10.             "iResult":        0,
  11.             "pDialogParam":        {
  12.                     "iAVStreamDir":        0,
  13.                     "iTargetCount":        1,
  14.                     "pUserData":        0,
  15.                     "pTarget":        [{
  16.                                     "szID":        "",
  17.                                     "iIndexMajor":        65536,
  18.                                     "iIndexMinor":        0
  19.                             }]
  20.             }
  21.     }
  22. 08-05 09:17:33.789 8805-8880/com.longway.xianchang I/YateMsgHandler: ------------------>I_METHOD -> 3
  23. 08-05 09:17:33.804 8805-8880/com.longway.xianchang I/YateMsgHandler: ------------------>I_TOKEN -> 31
  24. 08-05 09:17:33.805 8805-8880/com.longway.xianchang I/YateMsgHandler: <------------------PostToJavaHandler
  25. 08-05 09:17:33.805 8805-8880/com.longway.xianchang I/CUGlobal: File:jni-r19c/../jni/CUGlobal.cpp,Func = handleThreadMsg, end
  26. 08-05 09:17:33.806 8805-8882/com.longway.xianchang D/callback: get it prot.sm.dialog.pasv.event
  27. 08-05 09:17:33.827 8805-8805/com.longway.xianchang I/CameraFramework: handleMessage: 16
  28. 08-05 09:17:33.838 8805-8882/com.longway.xianchang D/ttt: 被动 OnPasvDialogEvent hDialog ：31 iEventCode : 3 pParam : {"iResult":0,"pDialogParam":{"iAVStreamDir":0,"iSize":0,"iTargetCount":1,"pTarget":[{"iIndexMajor":65536,"iIndexMinor":0,"szID":""}],"pUserData":0.0}}
  29. 08-05 09:17:33.839 8805-8882/com.longway.xianchang D/ttt: DIALOG_CLOSE命令  channelIndex=65536
  30.     (channelIndex == BVCU_SubDev.BVCU_SUBDEV_INDEXMAJOR_MIN_CHANNEL):false
  31.     (channelIndex == BVCU_SubDev.BVCU_SUBDEV_INDEXMAJOR_MIN_GPS && dir == 0) ：true
  32. 08-05 09:17:33.839 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onInputBufferFilled ID 3 w/ time 1596590253833000 eos 0 mode 1 err 0
  33. 08-05 09:17:33.841 8805-8882/com.longway.xianchang I/callback: prot.sm.dialog.pasv.event
copycode
  1. [OMX.MTK.VIDEO.ENCODER.AVC] onOutputBufferDrained ID d
  2. 08-05 09:17:33.845 8805-9075/com.longway.xianchang D/ACodec: give LatencyToken 37658, 3996
  3. 08-05 09:17:33.884 8805-8805/com.longway.xianchang I/CameraFramework: handleMessage: 16
  4. 08-05 09:17:33.886 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onInputBufferFilled ID 4 w/ time 1596590253885000 eos 0 mode 1 err 0
  5. 08-05 09:17:33.888 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onOutputBufferDrained ID e
  6. 08-05 09:17:33.892 8805-9075/com.longway.xianchang D/ACodec: give LatencyToken 37659, 1058
  7. 08-05 09:17:33.940 8805-8805/com.longway.xianchang I/CameraFramework: handleMessage: 16
  8. 08-05 09:17:33.949 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onInputBufferFilled ID 5 w/ time 1596590253941000 eos 0 mode 1 err 0
  9. 08-05 09:17:33.953 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onOutputBufferDrained ID f
  10. 08-05 09:17:33.955 8805-9075/com.longway.xianchang D/ACodec: give LatencyToken 37660, 5555
  11. 08-05 09:17:34.011 8805-8805/com.longway.xianchang I/CameraFramework: handleMessage: 16
  12. 08-05 09:17:34.018 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onInputBufferFilled ID 6 w/ time 1596590254015000 eos 0 mode 1 err 0
  13. 08-05 09:17:34.026 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onOutputBufferDrained ID 10
  14. 08-05 09:17:34.026 8805-9075/com.longway.xianchang D/ACodec: give LatencyToken 37661, 1009
  15. 08-05 09:17:34.071 8805-8805/com.longway.xianchang I/CameraFramework: handleMessage: 16
  16. 08-05 09:17:34.078 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onInputBufferFilled ID 7 w/ time 1596590254072000 eos 0 mode 1 err 0
  17. 08-05 09:17:34.079 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onOutputBufferDrained ID 11
  18. 08-05 09:17:34.084 8805-9075/com.longway.xianchang D/ACodec: give LatencyToken 37662, 1710
  19. 08-05 09:17:34.109 8805-8805/com.longway.xianchang I/CameraFramework: handleMessage: 16
  20. 08-05 09:17:34.114 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onInputBufferFilled ID 8 w/ time 1596590254112000 eos 0 mode 1 err 0
  21. 08-05 09:17:34.116 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onOutputBufferDrained ID 12
  22. 08-05 09:17:34.120 8805-9075/com.longway.xianchang D/ACodec: give LatencyToken 37663, 3664
  23. 08-05 09:17:34.157 8805-8805/com.longway.xianchang I/CameraFramework: handleMessage: 16
  24. 08-05 09:17:34.161 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onInputBufferFilled ID 9 w/ time 1596590254158000 eos 0 mode 1 err 0
  25. 08-05 09:17:34.163 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onOutputBufferDrained ID 13
  26. 08-05 09:17:34.167 8805-9075/com.longway.xianchang D/ACodec: give LatencyToken 37664, 1169
  27. 08-05 09:17:34.206 8805-8805/com.longway.xianchang I/CameraFramework: handleMessage: 16
  28. 08-05 09:17:34.211 8805-8898/com.longway.xianchang I/CUGlobal: iEventCode = 1,hDialog = 32, channelIndex =65536
  29. 08-05 09:17:34.211 8805-8898/com.longway.xianchang I/YateMsgHandler: ------------------>PostToJavaHandler prot.sm.dialog.pasv.cmd
  30. 08-05 09:17:34.212 8805-8898/com.longway.xianchang I/YateMsgHandler: ------------------>S_ID -> prot.sm.dialog.pasv.cmd
  31.     ------------------>S_RESULT -> {
  32.             "iAVStreamDir":        16,
  33.             "iTargetCount":        1,
  34.             "pUserData":        0,
  35.             "pTarget":        [{
  36.                             "szID":        "UA_23018572",
  37.                             "iIndexMajor":        65536,
  38.                             "iIndexMinor":        0
  39.                     }],
  40.             "szMyselfVideo":        {
  41.                     "codec":        0,
  42.                     "iWidth":        0,
  43.                     "iHeight":        0,
  44.                     "iExtraDataSize":        0
  45.             },
  46.             "szTargetVideo":        {
  47.                     "codec":        0,
  48.                     "iWidth":        0,
  49.                     "iHeight":        0,
  50.                     "iExtraDataSize":        0
  51.             },
  52.             "szTargetAudio":        {
  53.                     "codec":        0,
  54.                     "iBitrate":        0,
  55.                     "iChannelCount":        0,
  56.                     "iSampleRate":        0,
  57.                     "eSampleFormat":        0,
  58.                     "iExtraDataSize":        0
  59.             },
  60.             "szMyselfAudio":        {
  61.                     "codec":        0,
  62.                     "iBitrate":        0,
  63.                     "iChannelCount":        0,
  64.                     "iSampleRate":        0,
  65.                     "eSampleFormat":        0,
  66.                     "iExtraDataSize":        0
  67.             }
  68.     }
  69.     ------------------>I_PERCENT -> -563846011
  70.     ------------------>I_METHOD -> 1
  71.     ------------------>I_TOKEN -> 32
  72.     <------------------PostToJavaHandler
  73. 08-05 09:17:34.213 8805-8882/com.longway.xianchang D/callback: get it prot.sm.dialog.pasv.cmd
copycode
  1. [OMX.MTK.VIDEO.ENCODER.AVC] onInputBufferFilled ID 10 w/ time 1596590254207000 eos 0 mode 1 err 0
  2. 08-05 09:17:34.223 8805-9075/com.longway.xianchang D/ACodec: give LatencyToken 37665, 7209
  3. 08-05 09:17:34.225 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onOutputBufferDrained ID 14
  4. 08-05 09:17:34.232 8805-8882/com.longway.xianchang I/ttt: OnPasvDialogCmd（） hDialog ：32 iEventCode : 1 pParam : {"iAVStreamDir":16,"iSize":0,"iTargetCount":1,"pTarget":[{"iIndexMajor":65536,"iIndexMinor":0,"szID":"UA_23018572"}],"pUserData":0.0,"szMyselfAudio":{"codec":0,"eSampleFormat":0,"iBitrate":0,"iChannelCount":0,"iExtraDataSize":0,"iSampleRate":0},"szMyselfVideo":{"codec":0,"iExtraDataSize":0,"iHeight":0,"iWidth":0},"szTargetAudio":{"codec":0,"eSampleFormat":0,"iBitrate":0,"iChannelCount":0,"iExtraDataSize":0,"iSampleRate":0},"szTargetVideo":{"codec":0,"iExtraDataSize":0,"iHeight":0,"iWidth":0}}
  5. 08-05 09:17:34.233 8805-8882/com.longway.xianchang D/ttt: OnPasvDialogCmd ------channelIndex=65536,avDir=16
  6. 08-05 09:17:34.239 8805-8882/com.longway.xianchang I/CoreSDK: ----------------->PostMessageToNative prot.sm.dialog.cmd
  7. 08-05 09:17:34.239 8805-8882/com.longway.xianchang I/CoreSDK: ----------------->S_ID -> prot.sm.dialog.cmd
  8.     ----------------->I_RESULT -> -563846011
  9. 08-05 09:17:34.239 8805-8882/com.longway.xianchang I/CoreSDK: ----------------->S_RESULT -> {"iAVStreamDir":16,"iSize":0,"iTargetCount":1,"pTarget":[{"iIndexMajor":65536,"iIndexMinor":0,"szID":"UA_23018572"}],"pUserData":0.0,"szMyselfAudio":{"codec":0,"eSampleFormat":0,"iBitrate":0,"iChannelCount":0,"iExtraDataSize":0,"iSampleRate":0},"szMyselfVideo":{"codec":0,"iExtraDataSize":0,"iHeight":0,"iWidth":0},"szTargetAudio":{"codec":0,"eSampleFormat":0,"iBitrate":0,"iChannelCount":0,"iExtraDataSize":0,"iSampleRate":0},"szTargetVideo":{"codec":0,"iExtraDataSize":0,"iHeight":0,"iWidth":0}}
  10. 08-05 09:17:34.239 8805-8882/com.longway.xianchang I/CoreSDK: ----------------->I_PERCENT -> 0
  11. 08-05 09:17:34.240 8805-8882/com.longway.xianchang I/CoreSDK: ----------------->I_METHOD -> 1
  12. 08-05 09:17:34.240 8805-8882/com.longway.xianchang I/CoreSDK: ----------------->I_TOKEN -> 32
  13. 08-05 09:17:34.240 8805-8882/com.longway.xianchang I/CoreSDK: <-----------------PostMessageToNative
  14. 08-05 09:17:34.240 8805-8882/com.longway.xianchang I/YateMsgHandler: hDialog =  32, dir = 16
  15.     0 0 0 0 0
  16.     line = 567
  17. 08-05 09:17:34.240 8805-8882/com.longway.xianchang I/CoreSDK: 2020-08-05_09:17:34.240778 <FAIL> RefObject [0xdcbf3274] destroyed with count=2
  18. 08-05 09:17:34.241 8805-8882/com.longway.xianchang I/callback: prot.sm.dialog.cmd res: 0
  19. 08-05 09:17:34.244 8805-11201/com.longway.xianchang I/PUDialog: new a dialog,hDialog = 32,channelIdx = 65536
  20.     processInviteGPS+++++++++++++++++++++++
  21. 08-05 09:17:34.249 8805-8805/com.longway.xianchang I/CameraFramework: handleMessage: 16
  22. 08-05 09:17:34.253 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onInputBufferFilled ID 11 w/ time 1596590254250000 eos 0 mode 1 err 0
  23. 08-05 09:17:34.256 8805-9075/com.longway.xianchang D/ACodec: [OMX.MTK.VIDEO.ENCODER.AVC] onOutputBufferDrained ID d
  24. 08-05 09:17:34.260 8805-9075/com.longway.xianchang D/ACodec: give LatencyToken 37666, 1276
  25. 08-05 09:17:34.297 8805-8805/com.longway.xianchang I/CameraFramework: handleMessage: 16
copycode

author: wanzongyong    time: 2020-8-5 09:50
这张图片里有崩溃信息，但是截图不全，能否截一个全的图看看，或者把日志拷贝一下
author: wanzongyong    time: 2020-8-5 09:53
这个崩溃不是java代码的崩溃，应该是动态库的崩溃，从上面的截图里看libart.so是系统的，不知道下面没截到的部分有没有我们提供的库，所以需要更全的日志信息
author: 王.studio    time: 2020-8-5 10:57
wanzongyong post on2020-8-5 09:53
这个崩溃不是java代码的崩溃，应该是动态库的崩溃，从上面的截图里看libart.so是系统的，不知道下面没截到 ...
  1. A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x50696271 in tid 14339 (pool-1-thread-1)
  2. 08-05 10:40:15.862 14420-14420/? A/AEE/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
  3.     Build fingerprint: 'Hi-Target/full_tdc1609/tdc1609:6.0/MRA58K/1505979351:user/release-keys'
  4.     Revision: '0'
  5.     ABI: 'arm'
  6.     pid: 14288, tid: 14339, name: pool-1-thread-1  >>> com.longway.xianchang:remote <<<
  7.     signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x50696271
  8. 08-05 10:40:15.885 14420-14420/? A/AEE/DEBUG:     r0 59767272  r1 ea3f5c00  r2 00000018  r3 50696261
  9.         r4 50696261  r5 00000028  r6 12ecb000  r7 ebc37800
  10.         r8 ebc37828  r9 00000003  sl 12ecb028  fp 12ecb000
  11.         ip 00000054  sp dee525d0  lr 00000002  pc f462b9a2  cpsr 200f0030
  12. 08-05 10:40:15.891 14420-14420/? A/AEE/DEBUG: backtrace:
  13. 08-05 10:40:15.892 14420-14420/? A/AEE/DEBUG:     #00 pc 0017b9a2  /system/lib/libart.so (_ZN3art2gc9allocator8RosAlloc9RevokeRunEPNS_6ThreadEjPNS2_3RunE+225)
  14.         #01 pc 0017bbe9  /system/lib/libart.so (_ZN3art2gc9allocator8RosAlloc21RevokeThreadLocalRunsEPNS_6ThreadE+480)
  15.         #02 pc 001bc781  /system/lib/libart.so (_ZN3art2gc4Heap24RevokeThreadLocalBuffersEPNS_6ThreadE+20)
  16.         #03 pc 00337ded  /system/lib/libart.so (_ZN3art6Thread7DestroyEv+1436)
  17.         #04 pc 003463a3  /system/lib/libart.so (_ZN3art10ThreadList10UnregisterEPNS_6ThreadE+118)
  18.         #05 pc 0033f301  /system/lib/libart.so (_ZN3art6Thread14CreateCallbackEPv+600)
  19.         #06 pc 0004078b  /system/lib/libc.so (_ZL15__pthread_startPv+30)
  20.         #07 pc 0001a031  /system/lib/libc.so (__start_thread+6)
  21. 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)
  22. 08-05 10:41:35.923 14535-14535/? A/AEE/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
  23.     Build fingerprint: 'Hi-Target/full_tdc1609/tdc1609:6.0/MRA58K/1505979351:user/release-keys'
  24.     Revision: '0'
  25.     ABI: 'arm'
  26.     pid: 14425, tid: 14475, name: pool-1-thread-1  >>> com.longway.xianchang:remote <<<
  27.     signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x61335759
  28. 08-05 10:41:35.935 14535-14535/? A/AEE/DEBUG:     r0 e71a5fa8  r1 00000068  r2 e71a7bc8  r3 61335759
  29.         r4 00000000  r5 00000040  r6 00000001  r7 e71a60e0
  30.         r8 ea3f4800  r9 00000004  sl 00000004  fp 12da3000
  31.         ip 00000001  sp dee51b70  lr f462a8c9  pc f46291b2  cpsr 600f0030
  32. 08-05 10:41:35.939 14535-14535/? A/AEE/DEBUG: backtrace:
  33.         #00 pc 001791b2  /system/lib/libart.so (_ZNSt3__113__tree_removeIPNS_16__tree_node_baseIPvEEEEvT_S5_+209)
  34.         #01 pc 0017a8c5  /system/lib/libart.so (_ZN3art2gc9allocator8RosAlloc9RefillRunEPNS_6ThreadEj+560)
  35.         #02 pc 0017ac3f  /system/lib/libart.so (_ZN3art2gc9allocator8RosAlloc12AllocFromRunEPNS_6ThreadEjPjS5_S5_+498)
  36. 08-05 10:41:35.940 14535-14535/? A/AEE/DEBUG:     #03 pc 002a88c1  /system/lib/libart.so (_ZN3art6mirror6String21AllocFromModifiedUtf8EPNS_6ThreadEiPKc+1380)
  37.         #04 pc 0033d969  /system/lib/libart.so (_ZN3art6Thread42InternalStackTraceToStackTraceElementArrayERKNS_33ScopedObjectAccessAlreadyRunnableEP8_jobjectP13_jobjectArrayPi+368)
  38.         #05 pc 002cc371  /system/lib/libart.so (_ZN3artL29Throwable_nativeGetStackTraceEP7_JNIEnvP7_jclassP8_jobject+24)
  39.         #06 pc 023b0ca9  /system/framework/arm/boot.oat (offset 0x2381000)
  40.    
  41.    
  42.     --------- beginning of system[code]E/KernelCpuSpeedReader: cpu4 time_in_state not exist, is it a BUG??!!
  43. 08-05 10:53:04.571 1073-1091/? E/KernelCpuSpeedReader: cpu4 time_in_state not exist, is it a BUG??!!
  44. 08-05 10:53:04.657 1073-1089/? E/KernelCpuSpeedReader: cpu4 time_in_state not exist, is it a BUG??!!
  45. 08-05 10:53:04.661 1073-1091/? E/KernelCpuSpeedReader: cpu4 time_in_state not exist, is it a BUG??!!
  46. 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()?
  47.     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()?
  48.         at android.app.LoadedApk$ReceiverDispatcher.<init>(LoadedApk.java:959)
  49.         at android.app.LoadedApk.getReceiverDispatcher(LoadedApk.java:728)
  50.         at android.app.ContextImpl.registerReceiverInternal(ContextImpl.java:1177)
  51.         at android.app.ContextImpl.registerReceiver(ContextImpl.java:1157)
  52.         at android.app.ContextImpl.registerReceiver(ContextImpl.java:1151)
  53.         at android.content.ContextWrapper.registerReceiver(ContextWrapper.java:554)
  54.         at com.android.providers.media.MtpService.onCreate(MtpService.java:101)
  55.         at android.app.ActivityThread.handleCreateService(ActivityThread.java:3026)
  56.         at android.app.ActivityThread.-wrap4(ActivityThread.java)
  57.         at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1552)
  58.         at android.os.Handler.dispatchMessage(Handler.java:111)
  59.         at android.os.Looper.loop(Looper.java:207)
  60.         at android.app.ActivityThread.main(ActivityThread.java:5692)
  61.         at java.lang.reflect.Method.invoke(Native Method)
  62.         at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:888)
  63.         at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:749)
  64. 08-05 10:53:13.332 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  65. 08-05 10:53:13.333 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  66. 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
  67. 08-05 10:53:14.336 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  68. 08-05 10:53:14.337 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  69. 08-05 10:53:15.342 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  70. 08-05 10:53:15.343 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  71. 08-05 10:53:15.877 3067-3067/? E/DCloudApplication: onTrimMemory
  72. 08-05 10:53:15.881 7295-7295/? E/DCloudApplication: onTrimMemory
  73. 08-05 10:53:16.558 319-686/? E/MAL-Daemon:  (void* rilproxy_task_hdl(,  439) rilproxy_task_hdl(), receive event = 401
  74. 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
  75. 08-05 10:53:18.350 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  76. 08-05 10:53:18.351 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  77. 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
  78. 08-05 10:53:19.386 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  79. 08-05 10:53:19.386 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  80. 08-05 10:53:20.380 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  81. 08-05 10:53:20.381 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  82. 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
  83. 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
  84. 08-05 10:53:24.436 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  85. 08-05 10:53:24.437 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  86. 08-05 10:53:26.401 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  87. 08-05 10:53:26.402 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  88. 08-05 10:53:26.559 319-686/? E/MAL-Daemon:  (void* rilproxy_task_hdl(,  439) rilproxy_task_hdl(), receive event = 401
  89. 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
  90. 08-05 10:53:29.412 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  91. 08-05 10:53:29.428 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  92. 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
  93. 08-05 10:53:30.417 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  94. 08-05 10:53:30.419 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  95. 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
  96. 08-05 10:53:34.433 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  97. 08-05 10:53:34.434 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  98. 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
  99. 08-05 10:53:35.438 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  100. 08-05 10:53:35.456 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  101. 08-05 10:53:36.559 319-686/? E/MAL-Daemon:  (void* rilproxy_task_hdl(,  439) rilproxy_task_hdl(), receive event = 401
  102. 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
  103. 08-05 10:53:39.463 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  104. 08-05 10:53:39.463 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  105. 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
  106. 08-05 10:53:40.456 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
  107. 08-05 10:53:40.457 1236-1808/? E/MPlugin: Unsupported class: com.mediatek.systemui.ext.ISystemUIStatusBarExt
copycode
[/code]
author: wanzongyong    time: 2020-8-5 11:00
从日志里看并没有我们提供的库的错误信息，你的程序com.longway.xianchang:remote进程是做什么的
author: 王.studio    time: 2020-8-5 11:22
wanzongyong post on2020-8-5 11:00
从日志里看并没有我们提供的库的错误信息，你的程序com.longway.xianchang:remote进程是做什么的

这个remote进程是咱们的视频服务里，使用的百度定位服务
  1. <service android:name="com.baidu.location.f" android:enabled="true" android:process=":remote">
  2.         </service>
copycode
author: wanzongyong    time: 2020-8-5 11:23
我们DEMO中:remote是百度地图的进程，你看看你们程序里是不是也是的，<service android:name="com.baidu.location.f" android:enabled="true" android:process=":remote">，在AndroidManifest.xml中能看到。结合你说的现象，在接收到GPS通道关闭的通知时出现崩溃提示，可能和地图有关。
author: wanzongyong    time: 2020-8-5 11:25
你把定位相关的代码注释，在接收到GPS通道关闭的通知时不做处理看看还会不会出现崩溃提示
author: 王.studio    time: 2020-8-5 11:27
wanzongyong post on2020-8-5 11:00
从日志里看并没有我们提供的库的错误信息，你的程序com.longway.xianchang:remote进程是做什么的

这个问题 我之前咨询过大牛，说是远程进程出了问题。 远程进程调用了native方法。他没看我的代码，猜测应该是参数传值传错了
author: 王.studio    time: 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) {
author: wanzongyong    time: 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) {
author: 王.studio    time: 2020-8-5 14:17
wanzongyong post on2020-8-5 11:38
我们demo中在接收到回调时执行了locationTools.stopLocation();你把这个注释了。还有看看为啥在使用内网服 ...

现在其实就是发现了这个不断回调的情况，但不知道该怎么排查这个问题。看咱们这边能不能协助分析下，可能的情况，我们这边进行相应修改 测试
author: 王.studio    time: 2020-8-5 14:17
wanzongyong post on2020-8-5 11:25
你把定位相关的代码注释，在接收到GPS通道关闭的通知时不做处理看看还会不会出现崩溃提示

我试下。。。。。。。。。。。。。。
author: 王.studio    time: 2020-8-5 14:33
wanzongyong post on2020-8-5 11:25
你把定位相关的代码注释，在接收到GPS通道关闭的通知时不做处理看看还会不会出现崩溃提示

已注释   依然崩溃
author: 王.studio    time: 2020-8-5 15:07
王.studio post on2020-8-5 14:33
已注释   依然崩溃

我把所有的定位全注释了，暂时没出现崩溃提醒
author: wanzongyong    time: 2020-8-5 15:13
王.studio post on2020-8-5 15:07
我把所有的定位全注释了，暂时没出现崩溃提醒

地图功能用的话需要申请自己程序的key，这个key是跟包名绑定的
author: 王.studio    time: 2020-8-5 15:35
wanzongyong post on2020-8-5 15:13
地图功能用的话需要申请自己程序的key，这个key是跟包名绑定的

这个是已经更改过的
author: 王.studio    time: 2020-8-5 15:35
王.studio post on2020-8-5 15:35
这个是已经更改过的

目前没有出现崩溃提醒，但是 依然不断的回调
author: wanzongyong    time: 2020-8-5 16:19
王.studio post on2020-8-5 15:35
目前没有出现崩溃提醒，但是 依然不断的回调

多测试看看都是什么情况下会出现一直回调这个接口，此时PC端做了什么操作
author: 王.studio    time: 2020-8-5 16:52
wanzongyong post on2020-8-5 16:19
多测试看看都是什么情况下会出现一直回调这个接口，此时PC端做了什么操作

现在就是正常视频中 过一会就会  pc端没有进行任何操作。
author: wanzongyong    time: 2020-8-5 17:28
王.studio post on2020-8-5 16:52
现在就是正常视频中 过一会就会  pc端没有进行任何操作。

能否在出现现象时抓包看看
author: 王.studio    time: 2020-8-6 09:15
wanzongyong post on2020-8-5 17:28
能否在出现现象时抓包看看

我用studio  抓了下 不知道是不是因为我是内网的原因。。啥也抓不到。。
author: 王.studio    time: 2020-8-6 09:16
wanzongyong post on2020-8-5 17:28
能否在出现现象时抓包看看

咱们这边也有一台我们的可以连接内网的设备，要不就我给咱们发个安装包，咱们那边也装上看看？ 看看打印？
author: wanzongyong    time: 2020-8-6 10:16
王.studio post on2020-8-6 09:16
咱们这边也有一台我们的可以连接内网的设备，要不就我给咱们发个安装包，咱们那边也装上看看？ 看看打印 ...

设备我问问同事，你先发个APK吧。主要你们是用VPN的话数据应该都是加密的，抓包不知道能不能看出什么问题
author: 王.studio    time: 2020-8-6 15:16
wanzongyong post on2020-8-6 10:16
设备我问问同事，你先发个APK吧。主要你们是用VPN的话数据应该都是加密的，抓包不知道能不能看出什么问题

apk 发不上来。在log日志里输 ttt  就能看到各种系统信息，都是解密后的数据
author: 王.studio    time: 2020-8-6 15:24
wanzongyong post on2020-8-6 10:16
设备我问问同事，你先发个APK吧。主要你们是用VPN的话数据应该都是加密的，抓包不知道能不能看出什么问题

apk我发在群里了，进入系统后 双击现场管控图标，账号：wangjin  密码：aaaa1111@ 进入后  最下方选择作业任务，点击右上角三横杠 领取作业  厂家测试，勿动。 领取之后就可以了。到时候和我说，我联系我们的内网同事，给咱们这边发视频
author: 王.studio    time: 2020-8-6 15:26
wanzongyong post on2020-8-6 10:16
设备我问问同事，你先发个APK吧。主要你们是用VPN的话数据应该都是加密的，抓包不知道能不能看出什么问题

咱们这边一边是用什么抓包？ charles那个？
author: 王.studio    time: 2020-8-17 11:24
问题反馈内容......................................
author: besovideo    time: 2020-8-17 11:27
后续建议新开一个帖子
author: wanzongyong    time: 2020-8-18 14:42
王.studio post on2020-8-17 11:24
问题反馈内容......................................

目前判断应该是VPN网络原因，之前抓包说TCP经常断开，我们协议的信令层是udp，在网络出现问题时，设备可以做到不下线，但是GPS通道是TCP所以会断开，然后网络恢复时客户端会再次打开GPS通道。



欢迎光临 mobile CCTV,mobile surveillance,police body worn cameras (http://bbs.besovideo.com:8067/) Powered by Discuz! X3.2