opened
abiswa
username_0
AttachmentReaderSource::handleReadData is blocking sometimes while calling read api
auto size = m_reader->read(info.data, info.size, &status)

 BaseStreamSource:installOnReadDataHandler:action=newSourceId,sourceId=139
2017-09-25 01:23:44.233 [  2] 9 AttachmentReaderSource:read:size=4096,status=0
2017-09-25 01:23:44.233 [  2] 9 AttachmentReaderSource:read:size=4096,status=0
2017-09-25 01:23:44.233 [  2] 9 AttachmentReaderSource:read:size=4096,status=0
2017-09-25 01:23:44.233 [  2] 9 AttachmentReaderSource:read:size=2488,status=0
2017-09-25 01:23:44.258 [  2] 9 AttachmentReaderSource:read:size=3989,status=0

BaseStreamSource:clearOnReadDataHandlerCalled:sourceId=139 was not called because AttachmentReaderSource::handleReadData hung in read operation.

We are applying a temporary work around to bypass this behavior

std::chrono::milliseconds(1000);
    auto size = m_reader->read(info.data, info.size, &status, timeoutMs);

Is there any official fix available?
AttachmentReaderSource is blocking on reading Attachment data
issue
created
scotthea-amazon
username_1
Hello username_0,

There is a fix coming for a case where MediaPlayer gets stuck because reading from a stream timed out and the stream was closed w/o closing the associated attachment writer.  However, it is not clear that that is the case you ran in to here.  You could look in your logs for "streamProgressTimedOut".  If you see that before the blockage occurs then it is likely we will push a fix for this in the next release.  If not, could you provide more complete logs leading up to this condition?

Thank you,
-SWH
comment
created
kclchan
username_2
Hi @username_0, we have just released v1.1.0, would you be able to try to see if it fixes the issue you are seeing?
comment
created
Longynus83
username_3
Hi @username_2 ,
Having a look at this issue it seems like a different scenario leads to the AttachmentReader getting stuck and never detecting the status=3. I opened a ticket yesterday, you can find it here:

[https://github.com/alexa/avs-device-sdk/issues/221](url)

I posted the DEBUG9 app log extract (all tests run on SDK v.1.1.0), starting from the "Thinking" phase until the application get stuck.

Could you please have a look? Additionally, @username_0 would you mind to cross-check whether or not the scenario I am facing is similar to yours based on log traces?

Regards
comment
created
BennyAvramson
username_4
Hi @username_0,

Is your issue similar to @username_3's issue (#221)?

Thanks,
Benny
comment
created
sanjayrd
username_5
Closing due to inactivity. Please reopen if you're still seeing this issue in our latest release.

Thanks,
Sanjay
comment
closed
sanjayrd
username_5
issue