I installed the latest version of OSMC a few weeks ago on a Raspberry Pi 4 with 4 GB of memory (clean installation). The system is installed on an SSD disk connected to the Raspberry Pi 4 through one of the USB 3.0 ports. As a music source I connected OSMC to a network drive, via SAMBA, which contains my music collection.
The system also has TVHeadend installed and is connected to a DVB-T HDHomeRun receiver on the network. Record TV shows to a self-powered USB HDD, connected to the Raspberry Pi 4 via a USB 2.0 port.
The system crashed and restarted frequently.
Investigating, I discovered that the kodi.bin process was consuming more and more memory, causing the system to crash and restart when the memory consumption of the process approached 100%.
Reviewing the log files, I came to intuit that the music library had something to do with the excessive memory consumption of the kodi.bin process.
After removing the connection to the SAMBA network drive and, obviously, the connection to the music collection, the kodi.bin process has stopped consuming huge amounts of memory, limiting itself to consuming around 30% of the total system memory. And the system has stopped rebooting.
Is there any way I can connect the music collection and avoid this problem of excessive memory consumption of the kodi.bin process?
You could use an OS level mount if the issue is caused by Kodi’s SMB implementation.
See Mounting network shares with autofs (alternative to fstab) - General - OSMC for information on how to do this.
Sam
Thank’s. I’ll try it.