2020-07-28, 22:55
I just encountered the most(?) unusual scenario...
I was watching recorded tv with Kodi and doing other stuff.
I came to run 'sudo sh -c "echo 3 > /proc/sys/vm/drop_caches"' for something I was testing and it just hung with 100% cpu usage. I couldn't even cancel it or kill it, even with -9.
I just thought it may have been a kernel issue and looked into it a little and finally opted to reboot.
As I was closing everything I had open, suddenly the echo command stopped/completed. I immediately thought of Kodi and went to test that thought right away and it turned out to be true.
The echo command worked whenever I wasn't watching (or even paused) video in Kodi.
I can only guess that the video is continually being cached while the echo command is combating with trying to empty the cache.
I'm thinking it's not so much a bug with kodi or the kernel. It's just 2 processes fighting each other.
I was watching recorded tv with Kodi and doing other stuff.
I came to run 'sudo sh -c "echo 3 > /proc/sys/vm/drop_caches"' for something I was testing and it just hung with 100% cpu usage. I couldn't even cancel it or kill it, even with -9.
I just thought it may have been a kernel issue and looked into it a little and finally opted to reboot.
As I was closing everything I had open, suddenly the echo command stopped/completed. I immediately thought of Kodi and went to test that thought right away and it turned out to be true.
The echo command worked whenever I wasn't watching (or even paused) video in Kodi.
I can only guess that the video is continually being cached while the echo command is combating with trying to empty the cache.
I'm thinking it's not so much a bug with kodi or the kernel. It's just 2 processes fighting each other.
