Emby AndroidTV 1.8.28g Stops Working on 2019 Shield Pro

[Netfool 20]

Emby's AndroidTV app version 1.8.28g fails to play some files.  The first frame of the file is flashed on the screen, the buffering ring reappears and then the "too many errors" message appears.   These files play normally on Emby Web 4.5.2.0. 

Once the AndroidTV app gets into this state, nothing will play until the app is restarted. (In the latest case by "sleeping" the shield and re-selecting the Emby app.)
After re-entering the Emby app on the Shield the files played normally.
To me this smells like a memory leak.

Relevant log files from the server attached.  An AndroidTV log was sent: User RAM at 11:02 AM Pacific (14:02 Eastern).
Screenshot of the Dashboard Logs page included to establish the timeline for the various ffmpeg-directstream logs.

Wouldn't it be more useful to have the ending (or starting) timestamp as part of the log name rather than 40 characters of apparently random hex?

embyserver.txt ffmpeg-directstream-1a091431-a63c-4ffc-af36-330cfc5d2520_1.txt ffmpeg-directstream-8cda74c2-b9e0-417d-9f09-68ed7b4bf168_1.txt ffmpeg-directstream-32c95d1e-a713-47a8-8dec-42c83cbf92e7_1.txt ffmpeg-directstream-496e315f-1d63-464e-8d87-9a3011dd8959_1.txt ffmpeg-directstream-42493a61-d92a-45a0-a82a-fb239994674f_1.txt ffmpeg-directstream-db806afa-645d-4edb-b18b-9668e7144de0_1.txt ffmpeg-transcode-0ebe4dbb-0387-4622-9677-65169fc13462_1.txt ffmpeg-transcode-88aef408-144d-4a89-8b6e-8c15c868293e_1.txt ffmpeg-transcode-650b7b8a-05fb-4d1e-85b4-0ff8baa0d658_1.txt

[ebr 16182]

I think you are right that this is a memory issue but it is probably something in the firmware or OS level.  I also suspect it is related to a particular item.  Is it possible for you to isolate it to happening only after attempting playback of something specific?

[Netfool 20]

6 hours ago, ebr said:

I think you are right that this is a memory issue but it is probably something in the firmware or OS level.  I also suspect it is related to a particular item.  Is it possible for you to isolate it to happening only after attempting playback of something specific?

I don't know how to trigger the event.  My wife has run into it 3 or 4 times.  Usually watching MSNBC files acquired through an M3U interface.  Once the Emby app is restarted, the problem file plays flawlessly and repeatedly. 

One interesting detail:  Emby WebClient and VideoSpec seem to disagree as to the frame rate of this video.