Freezes especially during high bitrate playback

Help and Support Vero V
1

Recently my Vero V has been freezing during playback, I’ve noticed especially when I’m watching high bitrate content, talkin like 75 Mbps (watching my 4k remuxes of hotd s02 rn over plex). When it freezes up, I notice I’m usually locked out from SSHing into it. So I have to get up my lazy behind and unplug/replug to restart it.

Anything obvious stick out in my logs? I collected these right after booting it back up.

https://paste.osmc.tv/avadinuyoj

2

Another observation is that it seems flawless over native kodi playback via nfs mount. Seems to only happen when I watch via Plex. I AM a plex boi and would really love for that to just work but I suppose with being able to fallback to nfs I’m not overly bummed either.

3

Make sure Plex isn’t transcoding.

The logs aren’t debug logs, but it looks like the buffer may be running low.

4

Thanks for the reply.

99% sure Plex is not transcoding. I have all transcoding disabled in the app settings. Everything set to Original/Direct Stream. But I’ll be sure to keep an eye on it.

I had my Plex buffer set to 512 MB. Would you recommend raising that? It says in the app not to go beyond 759 MB even though it says I’ve got like 3.3 GB free mem.

Re: the debug logs, I see that setting. Is there a way to hide the overlay though when it’s enabled? If not, I’ll still try to make do and see what I can do.

Thanks again for taking a look.

5

Check here

6

Something very strange happened when the Plex script started: The time jumped 3 hours and 15 minutes into the future.

The time was turned back to Dec 08 23:05:12 during the subsequent boot via http access to time.osmc.tv.

Dec 08 23:05:12 osmc http-time[2490]: Updated time from Sun Dec  8 06:30:30 UTC 2024 to Mon Dec  9 05:05:12 UTC 2024 using HTTP query to time.osmc.tv

@asianpianoman 3:15 time offset/jump, does this ring any bells to you in combination with your PlexPlayer usage?

Perhaps (but there is no guarantee) , we can catch some more helpful information by activating persistent kernel logs with active debug:

To activate and provide such information, please, follow the steps below:

  1. login via SSH to the OSMC device, user osmc, password osmc
  2. cd /var/log
  3. sudo journalctl --rotate
  4. sudo journalctl --vacuum-time=1s
  5. sudo mkdir journal
  6. (from now, kernel messages are written to new directories for every boot)
  7. sudo shutdown -r now (to have shortest kodi old log, do this twice or a second reboot)
  8. now reproduce the issue/event which is the problem of this topic
  9. take the appropriate setps to upload the log set as usual (grab-logs -A or MyOSMC->Log Uploader)
  10. provide the returned URLs here
  11. don’t forget to remove the created journal directory otherwise your system’s root file system gets filled after some time
    12.a) login via SSH
    12.b )cd /var/log
    12.c) sudo rm -R -f journal && sudo reboot (repeat this line if you get a ‘cannot remove’ error until it works and your ssh connection gets lost by the reboot)

My hope is that we catch anything useful in the kernel logs … but it is possible that this information is lost while a crash or whatever happens. Just to set expectations right.

7

Perhaps, you’ve had a crash/freeze just before the crash/freeze after you took the log set. That could explain the time jump when the mediacenter was already started but the time adjusted somewhat later.