Using Java SDK 100.4.0 I am experiencing inconsistent crashes. This seems to be mostly trigger on initial map load if you zoom out quickly but has happened after the application has been running for several hours. The JVM Dumps aren't consistent in their errors either but look similar and look to be due to some concurrency issue. It seems similar to the issue outlined https://community.esri.com/message/862178-re-arcgis-map-crashes-randomly?commentID=862178&et=watches... for the Android SDK. In that issue they mentioned a fix in SDK Runtime 100.5.0 but we can't update to that version since we are stuck using Java 8. Does anyone have any information on this issue or possible mitigations?
Core Dumps:
Stack: [0x00000000b91b0000,0x00000000b92b0000], sp=0x00000000b92aeaa0, free space=1018k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [runtimecore.dll+0x2d7be2]
C [runtimecore.dll+0x2d7bb0]
C [runtimecore.dll+0x39a456]
C 0x00007fff34fc9e32
C 0x00000000026f8c67
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j com.esri.arcgisruntime.internal.jni.CoreRequest.nativeGetParameters(J)J+0
J 17042 C1 com.esri.arcgisruntime.layers.ArcGISTiledLayer$2.call()Ljava/lang/Object; (5 bytes) @ 0x000000000597140c [0x0000000005971080+0x38c]
J 11912 C1 java.util.concurrent.FutureTask.run()V (126 bytes) @ 0x0000000004c4f3d4 [0x0000000004c4f180+0x254]
j java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurrent/ThreadPoolExecutor$Worker;)V+95
J 16100 C1 java.util.concurrent.ThreadPoolExecutor$Worker.run()V (9 bytes) @ 0x00000000046f408c [0x00000000046f3f80+0x10c]
J 15521 C1 java.lang.Thread.run()V (17 bytes) @ 0x00000000038fad04 [0x00000000038fabc0+0x144]
v ~StubRoutines::call_stub
Another dump:
Stack: [0x00000000b95e0000,0x00000000b96e0000], sp=0x00000000b96dee50, free space=1019k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [runtimecore.dll+0x39a354]
C [runtimecore_java.dll+0x69f27]
C 0x0000000002938d07
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j com.esri.arcgisruntime.internal.jni.CoreRequest.nativeGetURI(J)[B+0
J 16657 C1 com.esri.arcgisruntime.internal.jni.CoreRequest.f()Ljava/lang/String; (51 bytes) @ 0x00000000054aafc4 [0x00000000054aae80+0x144]
J 16700 C1 com.esri.arcgisruntime.layers.ArcGISTiledLayer$2.call()Ljava/lang/Object; (5 bytes) @ 0x000000000489fb4c [0x000000000489f980+0x1cc]
J 11520 C1 java.util.concurrent.FutureTask.run()V (126 bytes) @ 0x0000000004decaac [0x0000000004dec840+0x26c]
j java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurrent/ThreadPoolExecutor$Worker;)V+95
j java.util.concurrent.ThreadPoolExecutor$Worker.run()V+5
J 15235 C1 java.lang.Thread.run()V (17 bytes) @ 0x00000000058d52c4 [0x00000000058d5180+0x144]
v ~StubRoutines::call_stub
Thanks,
Collin
Collin,
Have you contacted our support team about this? I have alerted them that you will be in contact.
Mark
Sorry, but you've got the wrong Collin 😉
I'm trying to go through the appropriate channels to get to support currently, hoping to open a dialog soon.