首页 / 浏览问题 / 移动GIS / 问题详情
imobile for Android异常崩溃
25EXP 2021年11月15日
使用产品:SuperMap iMobile 9D(2019)
数据类型: .SMWU  .udb
问题详细描述:正常加载地图,然后手指不断在地图上滑动,放大,缩小,不经意间就会崩溃退出,下面是崩溃提示:

2021-10-27 21:17:00.049 2108-2108/? E/DateLunarView: mDateString is: 10月27日星期三
2021-10-27 21:17:00.050 2108-2108/? E/DateLunarView: mDateString is: 10月27日星期三
2021-10-27 21:17:03.229 2441-2773/? E/powergenie_jni: /dev/graphics/fb0 opened failed!
2021-10-27 21:17:07.204 662-662/? E/Thermal-daemon: [ap] temp_new :36  temp_old :35
2021-10-27 21:17:07.205 662-662/? E/Thermal-daemon: Report temperature: [ap] temp :36  report_threshold:1
2021-10-27 21:17:18.867 20439-20495/com.njty.sea E/Adreno-UNKNOWN: <glBindTexture:347>: GL_OUT_OF_MEMORY
2021-10-27 21:17:18.920 20439-20494/com.njty.sea A/libc: Fatal signal 11 (SIGSEGV), code 1, fault addr 0x80000035 in tid 20494 (Thread-6446)
2021-10-27 21:17:19.099 20931-20931/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2021-10-27 21:17:19.100 20931-20931/? A/DEBUG: Build fingerprint: 'HUAWEI/BAH/HWBAH-Q:7.0/HUAWEIBAH-W09/C233B265:user/release-keys'
2021-10-27 21:17:19.100 20931-20931/? A/DEBUG: Revision: '0'
2021-10-27 21:17:19.100 20931-20931/? A/DEBUG: ABI: 'arm'
2021-10-27 21:17:19.100 20931-20931/? A/DEBUG: pid: 20439, tid: 20494, name: Thread-6446  >>> com.njty.sea <<<
2021-10-27 21:17:19.100 20931-20931/? A/DEBUG: signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x80000035
2021-10-27 21:17:19.100 20931-20931/? A/DEBUG:     r0 80000001  r1 00000de1  r2 00000102  r3 80000001
2021-10-27 21:17:19.100 20931-20931/? A/DEBUG:     r4 cd1f9800  r5 cd1fbb8c  r6 00000de1  r7 00000000
2021-10-27 21:17:19.100 20931-20931/? A/DEBUG:     r8 00000102  r9 c24f6568  sl e63e3400  fp c36adf40
2021-10-27 21:17:19.100 20931-20931/? A/DEBUG:     ip f323bf54  sp d0082580  lr e28b5487  pc e28b5490  cpsr 80030030
2021-10-27 21:17:19.116 20931-20931/? A/DEBUG: backtrace:
2021-10-27 21:17:19.116 20931-20931/? A/DEBUG:     #00 pc 00013490  /vendor/lib/egl/libESXGLESv1_CM_adreno.so (glBindTexture+115)
2021-10-27 21:17:19.116 20931-20931/? A/DEBUG:     #01 pc 00b13a21  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN3UGC18UGCacheGLES10Touch11Draw_RasterEPNS_19UGGLESRender_RasterE+340)
2021-10-27 21:17:19.116 20931-20931/? A/DEBUG:     #02 pc 00b197a3  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN3UGC18UGCacheGLES10Touch14RenderTileDataEPNS_16UGGLES10TileDataEbh+298)
2021-10-27 21:17:19.116 20931-20931/? A/DEBUG:     #03 pc 00b198d5  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN3UGC18UGCacheGLES10Touch23RenderTileDataToTextureEPNS_18UGGLESThreadContexEPNS_16UGGLES10TileDataERjiih+260)
2021-10-27 21:17:19.116 20931-20931/? A/DEBUG:     #04 pc 00b1ee53  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN3UGC18UGCacheGLES10Touch21ProcessTaskRenderTileEPNS_16UGGLES10TileDataE+362)
2021-10-27 21:17:19.116 20931-20931/? A/DEBUG:     #05 pc 00b27cf9  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN3UGC18UGCacheGLES10Touch11ProcessTaskEPNS_10UGTaskBaseE+28)
2021-10-27 21:17:19.116 20931-20931/? A/DEBUG:     #06 pc 01374bcf  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN3UGC17UGTaskMessageLoop3RunEv+58)
2021-10-27 21:17:19.117 20931-20931/? A/DEBUG:     #07 pc 01374c0f  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN3UGC16UGTaskWorkThread3runEv+10)
2021-10-27 21:17:19.117 20931-20931/? A/DEBUG:     #08 pc 0136ba69  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN3UGC8UGThread7executeEPv+28)
2021-10-27 21:17:19.117 20931-20931/? A/DEBUG:     #09 pc 00047393  /system/lib/libc.so (_ZL15__pthread_startPv+22)
2021-10-27 21:17:19.117 20931-20931/? A/DEBUG:     #10 pc 00019abd  /system/lib/libc.so (__start_thread+6)
2021-10-27 21:17:20.539 1616-1653/? E/HsmCoreServiceImpl: onTransact in code is: 102
2021-10-27 21:17:20.602 2441-2773/? E/powergenie_jni: /dev/graphics/fb0 opened failed!
2021-10-27 21:17:20.650 5661-5737/? E/HwLauncher: SettingsEx , no such field.
2021-10-27 21:17:32.212 662-662/? E/Thermal-daemon: [ap] temp_new :35  temp_old :36
2021-10-27 21:17:32.213 662-662/? E/Thermal-daemon: Report temperature: [ap] temp :35  report_threshold:1
2021-10-27 21:17:37.215 662-662/? E/Thermal-daemon: [ap] temp_new :34  temp_old :35
2021-10-27 21:17:37.215 662-662/? E/Thermal-daemon: Report temperature: [ap] temp :34  report_threshold:1
2021-10-27 21:17:57.221 662-662/? E/Thermal-daemon: [ap] temp_new :33  temp_old :34
2021-10-27 21:17:57.221 662-662/? E/Thermal-daemon: Report temperature: [ap] temp :33  report_threshold:1
2021-10-27 21:18:00.025 2108-2108/? E/DateLunarView: mDateString is: 10月27日星期三
2021-10-27 21:18:00.026 2108-2108/? E/DateLunarView: mDateString is: 10月27日星期三

看不出来什么原因,知道是什么导致的么?

1个回答

您好,看报错信息是因为内存溢出导致的,你那边加载的是什么类型的地图数据呢?数据量大概有多少,不断进行地图操作是在做性能测试还是业务需求?
9,127EXP 2021年11月16日
加载的地图是图片做的影像图,里面有9张不同级别的影像图,大小总共100M左右,不断的滑动地图或者放大缩小就是测试,偶尔出现的崩溃,应用使用内存大概在500M左右。
加载的地图是图片做的影像图,里面有9张不同级别的影像图,大小总共100M左右,不断的滑动地图或者放大缩小就是测试,偶尔出现的崩溃,应用使用内存大概在500M左右。
如果可以的话您那边可以把数据私发我一下,我这边验证一下看是否会出现崩溃的情况
我感觉你们超图这个问答社区界面有很多问题啊,这个回复按钮那么靠底就算了,一半还被底部你们的超图横幅给挡住了,有时间改改吧。数据给不了的,是内存泄漏那我就再找找吧。
...