HI,
I am attempting to setup up the new VeroV to replace the 4K+ that I have. It seems though, the system crashes when I attempt to connect my MariaDB and load the movie posters. It seems to only happen when I am using the Estuary Skin. It seems to work fine with the OSMC skin. Is there someway I can increase the cache size for the system?
I have reinstalled the OS and am currently using the 2024-08 version as a test but it happened with the current version too.
That’s interesting.
The Vero 4K+ has 2GB of RAM and Vero V has 4GB so this shouldn’t happen if it doesn’t on the former device.
Are you using the same version of OSMC and Kodi on the 4K+ with the same library?
Sam
It’s done this ever since I got it. The 4K+ is on 21.1 (2025.04) and the V is on 21.2 (2025.05). Both are connected to the same MariaDB.
Is it normal to have memory usage above 3.3GB? The memory usage starts at over 3GB and then decreases to around 1.5GB before the failure. Here is a video capture of the event the logs are based off of.
This is a known issue.
Is everything okay if you use the OSMC skin?
It works fine with the OSMC skin. Is the Estuary skin only broken on the VeroV? It seems everything else is working well. I don’t want to replace my 4K with the V until this problem is resolved.
this is a bug that has been around for 6 months or so. There is a workaround posted here.
That must be a somewhat intermittent bug then, as I have a Vero V, am running Estuary, have that setting enabled, and haven’t had any problems with the memory on my Vero V. Right now it’s sitting at 403MB of memory used at idle.
The problem has been reported by many people now, common link seems to be new installs or full rebuild of artwork, for some reason only affecting Estuary. Of course if the workaround doesn’t work for the OP then it’s a different issue.
I have played with those settings, and they are never persistent. Whenever the device reboots, they default back to true. Right now, I am in the OSMC skin and rebooted. I have waited 1hr and the memory usage is 3.4GB. This is where it was when I first turned on debugging right after a reboot.