2016-08-21, 23:16
(2016-08-21, 22:55)Milhouse Wrote:(2016-08-20, 16:20)pyrodex Wrote:(2016-08-20, 01:42)Milhouse Wrote: Is Kodi actually crashing? If so you'll have a crashlog (see note #4 in first post).
Knowing the exact build when this problem started could also help.
@Milhouse
I was able to spend some time rolling back from #814 to the version it is working and then broken in this morning. It seems AFTER #806 the issue occurs so maybe it has something to do with the ffmpeg bump in #807.
Unfortunately I was unable to get the system to crash no matter what I tried and only way I could recover was WAITING for an extremely LONG time or Hard rebooting the system. It is so bad that during the issue the system doesn't respond to SSH all the time and when I did get in and check TOP kodi is driving the CPU up greatly.
However here are logs from #806 and #807:
#806 - Working - http://sprunge.us/DbaI
#807 - NOT Working - http://sprunge.us/WTXH
Yes, this sounds like the same passthrough/seek/OOM problem introduced in #0806 that we see in the RPi builds - if you disable passthrough does the problem still happen?
@Milhouse
Yup! Disabled passthrough and updated to #819, worked as expected with skipping ahead.
Debug log if needed - http://sprunge.us/BKUQ
Let me know if you need me to test future stuff with it enabled as a fix.