(My original top post can be found further below. This is a summary of what we’ve collated so far.)
At random times during playback, the sound will cut out and a few seconds later, OSMC will appear completely frozen up. In some cases the system is eventually able to recover, but CEC (remote control) is lost. Rebooting is usually the only recourse.
- This issue is probably not present in image ‘OSMC_TGT_rbp1_20150830.img’ and earlier, but it is definitely present when the kernel is upgraded to 4.3.3-3-osmc. The issue is also definitely present in image ‘OSMC_TGT_rbp1_20151027.img’.
- The issue occurs irrespective of whether the media is accessed by NFS, SMB, FTP, or on USB drive:
- The issue also occurs while under-clocked (relative to the default OSMC settings):
- This happens with the following formats (and possibly more): h264, mpeg2.
- Accessing the RPi by ssh will occasionally un-freeze OSMC, which will then fast-forward in an attempt to ‘catch up’. CEC will not be restored, though.
- Evidence is mounting that this might be a memory leak, which causes the RPi to randomly kill off various services and parts of Kodi:
(This space will be updated, as we learn more.)
This is an update (continuation?) of a previous thread, which was closed due to insufficient logging and data in people’s bug reports: Frequent random freezing
(Log file link: http://paste.osmc.io/aqacowutuv.vhdl)
At a random point during movie playback the audio will suddenly fail, and ~3 seconds later the whole system freezes up. Cycling the power appears to be the only way to ‘recover’.
I have only experienced this bug when playing movie files, but that is hardly conclusive, as movie playback is the only way I use OSMC on my RPi. I have not noticed any pattern that would indicate that the bug could be associated with any particular media files in my library.
How to reproduce
The random nature of the issue makes it hard to reproduce. Some days I have no issues, whereas other days the system will freeze several times during a movie.
I just logged this bug while viewing Spielberg’s ‘The Adventures of Tintin’ in 720p/mkv-h264/dca-5.1. In this instance the system froze during the movie’s opening credits (but an earlier attempt at catching the bug had me sitting through the entire movie without incident; a few days prior I watched the movie and got the bug 4+ times!). At this point I let the system sit for 10 minutes, just in case it was still offloading log data to the SD card. I then attempted to establish an ssh connection, but never received a response. (Update: This seems to have been a user error, though.) Pinging the RPi did work, though. I then rebooted the RPi by cycling the power, ssh’ed in and retrieved a full log of the crash via the command line: grab-logs --all --copy
The bug is therefore represented by the ‘Kodi Old Log’ entry in the log file.
Edit: This is entirely anecdotal, but it appears to me that the bug is much more likely to manifest itself when I do multiple successive skips during playback. This alone is not always enough to provoce freezing, and for this log entry I just left the system running on its own.
I’m on a RPi 2.0/B (rev. 0000e) running ‘OSMC October 2015 2015.10-1’. The system was previously clocked using the default OSMC settings, but I am currently using the default RPi settings: arm=700, sdram=400, core=250, initial_turbo=0, over_voltage=0, over_voltage_sdram=0, force_turbo=0. Even though this is considered underclocking compared to OSMC’s default values, the bug still occurs.
I’m usually running the Eminence skin, but the current log is using the standard OSMC skin.
- Logitech keyboard via USB Bluetooth dongle.
- 4 GB SanDisk Ultra SDHC card.
- Sony Bravia KDL-32EX501 TV connected via HDMI.
- Ethernet connection to a router running DD-WRT v24-sp2 (05/23/14), which also serves a NAS that holds all movie files; OSMC connects to the NAS using SAMBA.
- Power supply is a 1200 mA HNP06-050.
When did this issue begin?
Several users in this thread - Frequent random freezing - #41 by sam_nazarko - attested that the issue began somtime during September/October. I did not log when this bug began for me, but it sounds about right. Several users also reported that reverting to an August build alleviated the issue.
While trying to get a clean log of this bug, I noticed that the log files tend to terminate with the following line: “DEBUG: script.module.osmcsetting.updates : - blurp 18 - VideoFullScreen.xml”
One time, I also took a snapshot of the OSMC debug overlay immediately after the bug had frozen the system: “LOG: /home/osmc/.kodi/temp/kodi.log; MEM: 259700/362164 KB - FPS: 6.2 fps; CPU: CPU0: 54% (CPU-KODI 46.67%)” (I’d expect the fps value to be higher by an order of magnitude, but I don’t know if that is relevant here.)