首页 / 浏览问题 / 移动GIS / 问题详情
珠峰场景二次打开崩溃
25EXP 2021年08月31日
使用产品:Supermap iMobile9D 操作系统:安卓设备
数据类型: 珠峰.sxwu
问题详细描述:参照SuperMap iMobile 9D(2019)SP1 for Android.chm文档里面运行了示范程序的打开本地数据,运行了珠峰demo,但是在打开珠峰Activity之前,我又加了一个Activity(A)用来跳转到珠峰的Activity,第一次跳转打开没有问题, 然后关闭珠峰Activity,回到Activity(A),再重新跳转到珠峰Activity,就出现崩溃,下面有崩溃日志
问题重现步骤: 珠峰场景重复打开就崩溃,异常信息来源sdk

崩溃日志:2021-08-31 13:35:10.524 667-667/? E/Thermal-daemon: Report temperature: [ap] temp :36  report_threshold:1
2021-08-31 13:35:12.014 1600-2466/? E/HsmCoreServiceImpl: onTransact in code is: 103
2021-08-31 13:35:34.324 619-4854/? E/BufferQueueProducer: [SurfaceView - com.njty.sea/com.njty.sea.ui.SceneActivity] dequeueBuffer: BufferQueue has no connected producer
2021-08-31 13:35:34.325 619-1194/? E/BufferQueueProducer: [SurfaceView - com.njty.sea/com.njty.sea.ui.SceneActivity] dequeueBuffer: BufferQueue has no connected producer
2021-08-31 13:35:34.325 619-2151/? E/BufferQueueProducer: [SurfaceView - com.njty.sea/com.njty.sea.ui.SceneActivity] dequeueBuffer: BufferQueue has no connected producer
2021-08-31 13:35:34.325 619-821/? E/BufferQueueProducer: [SurfaceView - com.njty.sea/com.njty.sea.ui.SceneActivity] dequeueBuffer: BufferQueue has no connected producer
2021-08-31 13:35:36.430 1600-29484/? E/HsmCoreServiceImpl: onTransact in code is: 103
2021-08-31 13:35:36.474 9830-9996/com.njty.sea E/OGRE: OGRE EXCEPTION(2:InvalidParametersException): NativeWindowType with name '00000000' already exists in GLES2RenderSystem::_createRenderWindow at E:\AR\OGRE1.9_ES3\RenderSystems\GLES2\src\OgreGLES2RenderSystem.cpp (line 526)
2021-08-31 13:35:36.475 9830-9996/com.njty.sea A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 9996 (Thread-78)
2021-08-31 13:35:36.611 9997-9997/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
2021-08-31 13:35:36.611 9997-9997/? A/DEBUG: Build fingerprint: 'HUAWEI/BAH/HWBAH-Q:7.0/HUAWEIBAH-W09/C233B265:user/release-keys'
2021-08-31 13:35:36.611 9997-9997/? A/DEBUG: Revision: '0'
2021-08-31 13:35:36.611 9997-9997/? A/DEBUG: ABI: 'arm'
2021-08-31 13:35:36.611 9997-9997/? A/DEBUG: pid: 9830, tid: 9996, name: Thread-78  >>> com.njty.sea <<<
2021-08-31 13:35:36.611 9997-9997/? A/DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
2021-08-31 13:35:36.611 9997-9997/? A/DEBUG:     r0 00000000  r1 0000270c  r2 00000006  r3 00000008
2021-08-31 13:35:36.611 9997-9997/? A/DEBUG:     r4 c6708978  r5 00000006  r6 c6708920  r7 0000010c
2021-08-31 13:35:36.611 9997-9997/? A/DEBUG:     r8 c67073b0  r9 c1c08750  sl ce814988  fp c670733c
2021-08-31 13:35:36.611 9997-9997/? A/DEBUG:     ip 00000002  sp c67072d0  lr ef1948c7  pc ef197124  cpsr 200f0010
2021-08-31 13:35:36.666 9997-9997/? A/DEBUG: backtrace:
2021-08-31 13:35:36.666 9997-9997/? A/DEBUG:     #00 pc 0004a124  /system/lib/libc.so (tgkill+12)
2021-08-31 13:35:36.666 9997-9997/? A/DEBUG:     #01 pc 000478c3  /system/lib/libc.so (pthread_kill+34)
2021-08-31 13:35:36.666 9997-9997/? A/DEBUG:     #02 pc 0001d525  /system/lib/libc.so (raise+10)
2021-08-31 13:35:36.667 9997-9997/? A/DEBUG:     #03 pc 00019071  /system/lib/libc.so (__libc_android_abort+34)
2021-08-31 13:35:36.667 9997-9997/? A/DEBUG:     #04 pc 000170d8  /system/lib/libc.so (abort+4)
2021-08-31 13:35:36.667 9997-9997/? A/DEBUG:     #05 pc 013dd124  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN9__gnu_cxx27__verbose_terminate_handlerEv+276)
2021-08-31 13:35:36.667 9997-9997/? A/DEBUG:     #06 pc 013d8bb0  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN10__cxxabiv111__terminateEPFvvE+8)
2021-08-31 13:35:36.667 9997-9997/? A/DEBUG:     #07 pc 013d8bf4  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZSt9terminatev+20)
2021-08-31 13:35:36.667 9997-9997/? A/DEBUG:     #08 pc 013d8d7c  /data/app/com.njty.sea-2/lib/arm/libimb.so (__cxa_throw+148)
2021-08-31 13:35:36.667 9997-9997/? A/DEBUG:     #09 pc 01695a55  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN4Ogre17GLES2RenderSystem19_createRenderWindowERKSsjjbPKSt3mapISsSsSt4lessISsENS_12STLAllocatorISt4pairIS1_SsENS_22CategorisedAllocPolicyILNS_14MemoryCategoryE0EEEEEE+240)
2021-08-31 13:35:36.667 9997-9997/? A/DEBUG:     #10 pc 0178b901  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN4Ogre4Root18createRenderWindowERKSsjjbPKSt3mapISsSsSt4lessISsENS_12STLAllocatorISt4pairIS1_SsENS_22CategorisedAllocPolicyILNS_14MemoryCategoryE0EEEEEE+28)
2021-08-31 13:35:36.667 9997-9997/? A/DEBUG:     #11 pc 00c2bbaf  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN3UGC18UGOGRERenderTarget6CreateEN4OGDC17OgdcUnicodeStringExyyjPN4Ogre13OverlaySystemE+278)
2021-08-31 13:35:36.667 9997-9997/? A/DEBUG:     #12 pc 00c2341d  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN3UGC16UGGraphics3DOGRE18CreateRenderTargetExPN4OGDC8OgdcDictINS1_17OgdcUnicodeStringES3_St4lessIS3_EEE+132)
2021-08-31 13:35:36.667 9997-9997/? A/DEBUG:     #13 pc 00b4bc23  /data/app/com.njty.sea-2/lib/arm/libimb.so (_ZN3UGC8UGRoot3D11CreateSceneExx+90)
2021-08-31 13:35:36.667 9997-9997/? A/DEBUG:     #14 pc 0094abab  /data/app/com.njty.sea-2/lib/arm/libimb.so (Java_com_supermap_realspace_SceneControlNative_jni_1New+90)
2021-08-31 13:35:36.667 9997-9997/? A/DEBUG:     #15 pc 00b147b9  /data/app/com.njty.sea-2/oat/arm/base.odex (offset 0xa4e000)
2021-08-31 13:35:38.434 1600-2386/? E/HwReportTool: This is not beta user build
2021-08-31 13:35:38.484 688-1190/? E/logserver: imonitor_add_dynamic_path, path:/data/system/dropbox/SYSTEM_TOMBSTONE@1630388138328.txt.gz
2021-08-31 13:35:38.501 1600-2394/? E/HwActivityManagerService: getProcessRecordFromMTM process info is null ,mUid :9830
2021-08-31 13:35:38.501 1600-2394/? E/ProcessInfoCollector: recordProcessInfo  failed to get process record
2021-08-31 13:35:38.507 2428-2746/? E/powergenie_jni: /dev/graphics/fb0 opened failed!
2021-08-31 13:35:38.509 1600-1634/? E/HsmCoreServiceImpl: onTransact in code is: 102
2021-08-31 13:35:38.513 3248-3326/? E/HwLauncher: SettingsEx , no such field.
2021-08-31 13:35:39.159 2857-10013/? E/PTM.FileNodeInfo: getTempInfo error: null, 0
2021-08-31 13:35:39.159 2857-10013/? E/PTM.FileNodeInfo: getTempInfo error: null, 0
2021-08-31 13:35:39.159 2857-10013/? E/PTM.FileNodeInfo: getTempInfo error: null, 0
2021-08-31 13:35:39.159 2857-10013/? E/PTM.FileNodeInfo: getTempInfo error: null, 0
2021-08-31 13:35:39.159 2857-10013/? E/PTM.FileNodeInfo: getTempInfo error: null, 0

1个回答

您好,这是由于acitivity的生命周期导致的,可以使用下面的方法解决:
1.设置场景的activity的启动模式 singleInstance  2.重写场景activity的finish方法:
 

public void finish() {
   // super.finish();

    moveTaskToBack(true);//这句代码很关键
}
9,197EXP 2021年08月31日
...