Application crash with error Fatal signal 11 (SIGSEGV)

HI,
Please help , Application getting crashed with following error log. using Photon-AndroidNDK-Sdk_v4-1-2-0





06-03 15:03:16.220: I/DEBUG(224): backtrace:
06-03 15:03:16.220: I/DEBUG(224): #00 pc 000818b2 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::Common::MemoryManagement::Internal::MemoryPool::dealloc(void*)+5)
06-03 15:03:16.220: I/DEBUG(224): #01 pc 0007ed21 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::Common::Object::cleanup(void const*, unsigned int)+110)
06-03 15:03:16.220: I/DEBUG(224): #02 pc 0007ee5f /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::Common::Object::~Object()+18)
06-03 15:03:16.220: I/DEBUG(224): #03 pc 0007b443 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::Common::JVector::removeAllElements()+28)
06-03 15:03:16.220: I/DEBUG(224): #04 pc 0007b52f /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::Common::JVector::~JVector()+14)
06-03 15:03:16.220: I/DEBUG(224): #05 pc 0007b559 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::Common::Hashtable::~Hashtable()+16)
06-03 15:03:16.220: I/DEBUG(224): #06 pc 0007ad43 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::Common::DictionaryBase::~DictionaryBase()+22)
06-03 15:03:16.220: I/DEBUG(224): #07 pc 0003dd0b /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::Common::Dictionary::~Dictionary()+14)
06-03 15:03:16.220: I/DEBUG(224): #08 pc 00044f89 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::LoadBalancing::Peer::opRaiseEvent(bool, ExitGames::Common::Object const&, unsigned char, ExitGames::LoadBalancing::RaiseEventOptions)+516)
06-03 15:03:16.220: I/DEBUG(224): #09 pc 0003c997 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (NetworkLogic::sendEvent(ExitGames::Common::JString&)+142)
06-03 15:03:16.220: I/DEBUG(224): #10 pc 0003d767 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (Java_com_appon_multiplyer_MultiplayerHandler_sendData+58)
06-03 15:03:16.220: I/DEBUG(224): #11 pc 00020d0c /system/lib/libdvm.so (dvmPlatformInvoke+112)
06-03 15:03:16.220: I/DEBUG(224): #12 pc 00051a67 /system/lib/libdvm.so (dvmCallJNIMethod(unsigned int const*, JValue*, Method const*, Thread*)+398)
06-03 15:03:16.220: I/DEBUG(224): #13 pc 0002a1a0 /system/lib/libdvm.so
06-03 15:03:16.220: I/DEBUG(224): #14 pc 00031650 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
06-03 15:03:16.220: I/DEBUG(224): #15 pc 0002ece8 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
06-03 15:03:16.220: I/DEBUG(224): #16 pc 00063fb5 /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+336)
06-03 15:03:16.220: I/DEBUG(224): #17 pc 00063fd9 /system/lib/libdvm.so (dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20)
06-03 15:03:16.220: I/DEBUG(224): #18 pc 00058cab /system/lib/libdvm.so
06-03 15:03:16.220: I/DEBUG(224): #19 pc 0000d298 /system/lib/libc.so (__thread_entry+72)
06-03 15:03:16.220: I/DEBUG(224): #20 pc 0000d430 /system/lib/libc.so (pthread_create+240)
06-03 15:03:16.220: I/DEBUG(224): stack:
06-03 15:03:16.220: I/DEBUG(224): 7ee288b0 00000000
06-03 15:03:16.220: I/DEBUG(224): 7ee288b4 00000000
06-03 15:03:16.220: I/DEBUG(224): 7ee288b8 00000000
06-03 15:03:16.220: I/DEBUG(224): 7ee288bc 00000000
06-03 15:03:16.220: I/DEBUG(224): 7ee288c0 00000000
06-03 15:03:16.220: I/DEBUG(224): 7ee288c4 00000000
06-03 15:03:16.220: I/DEBUG(224): 7ee288c8 00000060
06-03 15:03:16.220: I/DEBUG(224): 7ee288cc 79bc5f1c
06-03 15:03:16.220: I/DEBUG(224): 7ee288d0 00000060
06-03 15:03:16.220: I/DEBUG(224): 7ee288d4 79bc613c
06-03 15:03:16.220: I/DEBUG(224): 7ee288d8 00000018
06-03 15:03:16.220: I/DEBUG(224): 7ee288dc 79bc511c
06-03 15:03:16.220: I/DEBUG(224): 7ee288e0 7d761018
06-03 15:03:16.230: I/DEBUG(224): 7ee288e4 78b92917 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::Common::MemoryManagement::Internal::Interface::free(void*)+34)
06-03 15:03:16.230: I/DEBUG(224): 7ee288e8 79bc5124
06-03 15:03:16.230: I/DEBUG(224): 7ee288ec 78b92d25 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::Common::Object::cleanup(void const*, unsigned int)+114)
06-03 15:03:16.230: I/DEBUG(224): #00 7ee288f0 7d761018
06-03 15:03:16.230: I/DEBUG(224): ........ ........
06-03 15:03:16.230: I/DEBUG(224): #01 7ee288f0 7d761018
06-03 15:03:16.230: I/DEBUG(224): 7ee288f4 7ee28978 [stack:26821]
06-03 15:03:16.230: I/AudioTrack(235): track is underrun status. skip wait time.
06-03 15:03:16.230: I/DEBUG(224): 7ee288f8 00000028
06-03 15:03:16.230: I/DEBUG(224): 7ee288fc 726079d0
06-03 15:03:16.230: I/DEBUG(224): 7ee28900 78b81761 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::Photon::PhotonPeer::opCustom(ExitGames::Photon::OperationRequest const&, bool, unsigned char, bool))
06-03 15:03:16.230: I/DEBUG(224): 7ee28904 78baa062 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so
06-03 15:03:16.230: I/DEBUG(224): 7ee28908 00000001
06-03 15:03:16.230: I/DEBUG(224): 7ee2890c 78b92e63 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::Common::Object::~Object()+22)
06-03 15:03:16.230: I/DEBUG(224): #02 7ee28910 00000001
06-03 15:03:16.230: I/DEBUG(224): 7ee28914 78b8f445 /data/app-lib/com.appon.kitchenstory-5/libmultiplayerPhoton.so (ExitGames::Common::JVector::removeAllElements()+30)
06-03 15:03:16.230: I/DEBUG(224): memory near r0:
06-03 15:03:16.230: I/DEBUG(224): 7800626c 00485041 45504f1c 52475f4e 5f485041
06-03 15:03:16.230: I/DEBUG(224): 7800627c 41455243 4f5f4554 43454a42 454b5f54
06-03 15:03:16.230: I/DEBUG(224): 7800628c 4f090059 5f4e4550 4b4e494c 504f1100

06-03 15:03:16.260: I/DEBUG(224): 77f44000-77f45000 r-- /data/dalvik-cache/data@app@com.appon.kitchenstory-5.apk@classes.dex
06-03 15:03:16.260: I/DEBUG(224): 77f45000-78168000 r-- /data/dalvik-cache/data@app@com.appon.kitchenstory-5.apk@classes.dex
06-03 15:03:16.260: I/DEBUG(224): 78168000-781e1000 rw- /dev/ashmem/dalvik-aux-structure (deleted)

Comments

  • Hi @Harish_Kagale.

    Could you please share the code and parameters of the opRaiseEvent() call with us, for which this is happening?
  • sendEventis method is the method that i call to send events to other client,

    This issue is not frequent but get reproduced rarely. other parameter for the method is RaseEventOPtion which is set to default in loadbalancing client

    void NetworkLogic::sendEvent(ExitGames::Common::JString& event)
    {
    mLoadBalancingClient.opRaiseEvent(true,event, 0);
    }

    Thanks
  • Kaiserludi
    Kaiserludi admin
    edited May 2016
    Hi @Harish_Kagale.

    OK - that code looks absolutely fine and not like if it could cause this issue.

    Are you by any chance accessing photon from multiple different threads?
    This is not supported yet and might lead into such issues. This would also explain the infrequency of the occurrences.

    If this is happening with single-threaded access, then please take one of our demos and modify it so that you can reproduce the same issue with it and provide us with that modified demo, so that we can debug what is causing this.
  • Hi Kaiserludi ,

    Thanks for the reply .

    There is single game thread which is accessing photon , i'll try to modify the load balancing sample and get back to you,

    I am sending events on touch (pointer pressed ) and from the game thread (ex , in game events such as generate enemy)









  • Hi @Harish_Kagale.

    I am not too familiar with the Android UI.
    Might these touch event been executed on other threads than your main game thread?
    In that case the solution would be to not send directly from within those touchs, but to only store the info that the main thread should send a certain event in the next main loop frame.
  • Hi @Kaiserludi admin ,

    Need help.
    I tried sending events only from my game thread but still the issue exists.
    Now i am saving the touch events and in firing those events in next game loop.

    Thanks


  • Hi @Harish_Kagale.

    If this is happening with single-threaded access, then please take one of our demos and modify it so that you can reproduce the same issue with it and provide us with that modified demo, so that we can debug what is causing this.
  • Hi @Kaiserludi admin ,

    May be it happens when the other clent has been left becuase of connection error.
    Ex . opponent has left and the event is sent from one client to other.
  • Hi @Harish_Kagale.

    No. That would definitely not let the remaining client crash.