Intermittent crash in Unity3d on iOS
Posted: 24 Sep 2013, 21:55
Hello,
We're using Unity3d 4.2.1f4 and SFS2X_API_CSharp_v1.3.0. When running our app on iOS devices we are gettting an intermittent crash. We don't have the steps to reproduce yet but we do get a thread dump from Crashlytics:
0 TestApp m_Sfs2X_Core_Sockets_UDPSocketLayer_CloseConnection + 56
1
2 TestApp m_Sfs2X_Core_Sockets_UDPSocketLayer_HandleErrorCallback_object + 300
3 TestApp m_Sfs2X_Core_ThreadManager_ProcessItem_System_Collections_Hashtable + 392
4 TestApp m_Sfs2X_Core_ThreadManager_InThread + 108
5 TestApp m_wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr + 204
6 TestApp mono_jit_runtime_invoke + 2156
7 TestApp mono_runtime_invoke + 136
8 TestApp mono_runtime_delegate_invoke + 132
9 TestApp start_wrapper + 596
10 TestApp thread_start_routine + 288
11 TestApp GC_start_routine + 96
12 libsystem_pthread.dylib _pthread_body
13 libsystem_pthread.dylib _pthread_start
Seems to crash on closing a connection in response to an error. Still tracking down the error, but is there a way to prevent this crash and recover?
We're using Unity3d 4.2.1f4 and SFS2X_API_CSharp_v1.3.0. When running our app on iOS devices we are gettting an intermittent crash. We don't have the steps to reproduce yet but we do get a thread dump from Crashlytics:
0 TestApp m_Sfs2X_Core_Sockets_UDPSocketLayer_CloseConnection + 56
1
2 TestApp m_Sfs2X_Core_Sockets_UDPSocketLayer_HandleErrorCallback_object + 300
3 TestApp m_Sfs2X_Core_ThreadManager_ProcessItem_System_Collections_Hashtable + 392
4 TestApp m_Sfs2X_Core_ThreadManager_InThread + 108
5 TestApp m_wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr + 204
6 TestApp mono_jit_runtime_invoke + 2156
7 TestApp mono_runtime_invoke + 136
8 TestApp mono_runtime_delegate_invoke + 132
9 TestApp start_wrapper + 596
10 TestApp thread_start_routine + 288
11 TestApp GC_start_routine + 96
12 libsystem_pthread.dylib _pthread_body
13 libsystem_pthread.dylib _pthread_start
Seems to crash on closing a connection in response to an error. Still tracking down the error, but is there a way to prevent this crash and recover?