Hi all
Can you help us diagnose why this native crash happens? This is something that has showed up consistently in our crash logs at a relatively low rate (9k instances in last 60 days out of many millions of sessions). There doesn't seem to be any pattern in the device make/version/model, and there isn't much more information I can glean out of this native trace.
Is this something that you guys have seen before?
We are using maesdk:1.6. Here is a sample trace from google play:

Thread: Check failed: !Contains(self)
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 21232 >>> com.microsoft.skydrive <<<
backtrace:
#00 pc 0x000000000008cdd0 /apex/com.android.runtime/lib64/bionic/libc.so (abort+164)
#01 pc 0x000000000053b0a4 /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+2340)
#02 pc 0x000000000001394c /system/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_3::__invoke(char const*)+76)
#03 pc 0x00000000000130cc /system/lib64/libbase.so (android::base::LogMessage::~LogMessage()+312)
#04 pc 0x00000000005a43fc /apex/com.android.art/lib64/libart.so (art::ThreadList::Register(art::Thread*)+852)
#05 pc 0x000000000058100c /apex/com.android.art/lib64/libart.so (art::Thread::Init(art::ThreadList*, art::JavaVMExt*, art::JNIEnvExt*)+328)
#06 pc 0x0000000000583928 /apex/com.android.art/lib64/libart.so (art::Thread::Attach(char const*, bool, _jobject*, bool)+356)
#07 pc 0x0000000000539d00 /apex/com.android.art/lib64/libart.so (art::Runtime::AttachCurrentThread(char const*, bool, _jobject*, bool)+92)
#08 pc 0x0000000000379780 /apex/com.android.art/lib64/libart.so (art::JII::AttachCurrentThreadInternal(_JavaVM*, _JNIEnv**, void*, bool)+252)
#09 pc 0x0000000000153938 /data/app/~~8P1Yh6mkfUK___nNiXjZnA==/com.microsoft.skydrive-Qwn61w5I_191by3jxGONfg==/lib/arm64/libmaesdk.so (Microsoft::Applications::Events::HttpClient_Android::SendRequestAsync(Microsoft::Applications::Events::IHttpRequest*, Microsoft::Applications::Events::IHttpResponseCallback*)+112)
#10 pc 0x00000000000f6d14 /data/app/~~8P1Yh6mkfUK___nNiXjZnA==/com.microsoft.skydrive-Qwn61w5I_191by3jxGONfg==/lib/arm64/libmaesdk.so (Microsoft::Applications::Events::Packager::handleFinalizePackage(std::__ndk1::shared_ptr<Microsoft::Applications::Events::EventsUploadContext> const&)+264)
#11 pc 0x00000000000f3afc /data/app/~~8P1Yh6mkfUK___nNiXjZnA==/com.microsoft.skydrive-Qwn61w5I_191by3jxGONfg==/lib/arm64/libmaesdk.so (Microsoft::Applications::Events::StorageObserver::handleRetrieveEvents(std::__ndk1::shared_ptr<Microsoft::Applications::Events::EventsUploadContext> const&)+300)
#12 pc 0x000000000011ed40 /data/app/~~8P1Yh6mkfUK___nNiXjZnA==/com.microsoft.skydrive-Qwn61w5I_191by3jxGONfg==/lib/arm64/libmaesdk.so (Microsoft::Applications::Events::TransmissionPolicyManager::uploadAsync(Microsoft::Applications::Events::EventLatency)+580)
#13 pc 0x00000000000fbea8 /data/app/~~8P1Yh6mkfUK___nNiXjZnA==/com.microsoft.skydrive-Qwn61w5I_191by3jxGONfg==/lib/arm64/libmaesdk.so (Microsoft::Applications::Events::PlatformAbstraction::WorkerThread::threadFunc(void*)+548)
#14 pc 0x00000000000fc7ec /data/app/~~8P1Yh6mkfUK___nNiXjZnA==/com.microsoft.skydrive-Qwn61w5I_191by3jxGONfg==/lib/arm64/libmaesdk.so (void* std::__ndk1::__thread_proxy<std::__ndk1::tuple<std::__ndk1::unique_ptr<std::__ndk1::__thread_struct, std::__ndk1::default_delete<std::__ndk1::__thread_struct> >, void (*)(void*), void*> >(void*)+44)
#15 pc 0x00000000000f40c4 /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+64)
#16 pc 0x000000000008ed10 /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64)
Hi all
Can you help us diagnose why this native crash happens? This is something that has showed up consistently in our crash logs at a relatively low rate (9k instances in last 60 days out of many millions of sessions). There doesn't seem to be any pattern in the device make/version/model, and there isn't much more information I can glean out of this native trace.
Is this something that you guys have seen before?
We are using maesdk:1.6. Here is a sample trace from google play:
Thread:
Check failed: !Contains(self)