search

opentok / opentok-android-sdk-samples

Sample applications illustrating best practices using OpenTok Android SDK.
https://tokbox.com/developer/sdks/android/
MIT License
211 stars 169 forks source link

Native thread exiting without having called DetachCurrentThread #204

Closed sohailniazai closed 5 years ago

sohailniazai commented 5 years ago

Hi, I upgraded OpenTok version from 2.14.0 to 2.15.3, after upgrading to latest version I started facing issue when stream is dropped by other user. In 2.14.0, when I receive onStreamDropped(), I use the following code to disconnect the user : if (mSubscriber.getStream().equals(stream)) { mSubscriber.destroy(); mSubscriber = null; } and it is working fine. But since I have upgraded to 2.15.3 , calling "mSubscriber.getStream().equals(stream)" this line of code results in hanging the app and in logCat I see this warning : W/art: Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?)

Please look into this issue. Currently, I have rolled back to previous version.

robjperez commented 5 years ago

Hi!,

Thanks for reporting it.

This issue will be fixed in the upcoming 2.16 release that will be released soon (we don't have a date yet).

When 2.16 is out please test it again and if you see the problem happening again, reopen this ticket.

shahalRahman commented 4 years ago

App froze after ending call. In logcat i can see this warning. W/art: Native thread exiting without having called DetachCurrentThread (maybe it's going to use a pthread_key_create destructor?): Thread[57,tid=2791,Native,Thread*=0x55974d2880,peer=0x12c75e20,"Thread-218"]

I'm using OpenTok 2.18.0.