xlb767923274

> Hi thanks for posting @xlb767923274 > We're currently investigating this bug other question ： 1. At this file(AndroidSLESMediaQueue.cpp)， the ‘m_playedWords’ are not accurate， 1.1. It has Enqueued a silense...

thanks for reply， here is the newest DEBUG9 log ： C:\Users\Administrator\Downloads\speaker_20210719-102900.log (6 hits) Line 30479: 07-19 11:40:26.333 D/AlexaSampleApp( 3268): [ 3e] 0 AudioInputProcessor:onSendCompleted:status=CLIENT_ERROR_BAD_REQUEST Line 30480: 07-19 11:40:26.333 D/AlexaSampleApp( 3268): [...

> Hello @xlb767923274 > > Is this crash reproducible? If possible could you please provide the steps required in order to reproduce this crash? build by guide doc of ubuntu...

new crash stack： Thread 45 "SampleApp" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff377fe700 (LWP 125824)] 0x00007fffef70ca07 in Curl_splaygetbest (i=..., t=0x7fff2c012cb8, removed=0x7fff377fd820) at splay.c:180 180 x->key = t->key; (gdb)...

> @xlb767923274, are you still seeing the problem? If yes, could you let me know the version of libcurl and openssl you are using? And is there a repo step?...

Log file in debug9，The file is too large and some logs have been deleted [speaker_20210826-133526.log](https://github.com/alexa/avs-device-sdk/files/7054167/speaker_20210826-133526.log)

08-26 14:37:23.501 D/AlexaSampleApp(23338): [ 44] 0 AudioPlayer:provideState:stateRequestToken=106 void AudioPlayer::provideState( const avsCommon::avs::NamespaceAndName& stateProviderName, unsigned int stateRequestToken) { ACSDK_DEBUG(LX("provideState").d("stateRequestToken", stateRequestToken)); m_executor.submit([this, stateRequestToken] { executeProvideState(true, stateRequestToken); }); } why executeProvideState() havn't been execute......

I know the problem，there is a deadlock.. In AndroidSLESMediaPlayer::configureNewRequest() std::lock_guard requestLock{m_requestMutex}; { // Use global lock to stop player and set new source id. std::lock_guard lock{m_operationMutex}; if (m_hasShutdown) { ACSDK_ERROR(LX("configureNewRequestFailed").d("name",...

When will this issue be resolved? Will there be a new release version this month? Will the new version solve this issue?

> Hi @xlb767923274 , > > Is this issue still occurring, and have you been able to reproduce this on the latest version of the SDK? Is this issue still...