[DoubleT]

I have 10 raspberry pi's running in my office - some libreelec, some raspbian.
On one of the raspbian based pi's some particular jpgs won't load - i get a black / blank screen.
These are the same jpgs (exact same remote location within the LAN) which load fine on all other pi's. raspbian or libreelec.

When the files work ok on the other boxes i get this in the log file
10:04:25.597 T:1911148544   ERROR: Error loading the next image 0: smb://FOE-SCREEN2/Pictures/gbbc-api-stats.png
10:04:25.738 T:1911148544   ERROR: Error loading the next image 1: smb://FOE-SCREEN2/Pictures/gbbc-gds-users.png
10:06:12.878 T:1911148544  NOTICE: Samba is idle. Closing the remaining connections

On the box where the images don't load i get this in the log
15:30:03.184 T:1713787648   ERROR: COMXCoreComponent::AllocInputBuffers component(OMX.broadcom.image_decode) - OMX_UseBuffer failed with omx_err(0x80001000)
15:30:03.184 T:1713787648   ERROR: COMXTexture:ecode - Error alloc buffers  (80001000)
15:30:03.184 T:1713787648  NOTICE: DecodeJpegToTexture: unable to decode to texture smb://FOE-SCREEN2/Pictures/001.jpg 1280x720
15:30:03.197 T:1713787648   ERROR: COMXCoreComponent::SetStateForComponent - OMX.broadcom.image_decode failed with omx_err(0x80001000)
15:30:05.491 T:1713787648   ERROR: Previous line repeats 1 times.
15:30:05.492 T:1713787648   ERROR: COMXCoreComponent::AllocInputBuffers component(OMX.broadcom.image_decode) - OMX_UseBuffer failed with omx_err(0x80001000)
15:30:05.492 T:1713787648   ERROR: COMXTexture:ecode - Error alloc buffers  (80001000)
15:30:05.492 T:1713787648  NOTICE: DecodeJpegToTexture: unable to decode to texture smb://FOE-SCREEN2/Pictures/002.jpg 1280x720

I don't have full debug logs yet - but can get them later in the week.
Wondering if this Pi has a missing part of installation as i know some portions of the code have been split into other packages such as PVR, but i doubt JPG use would fall into this category.
Other thought is that the broadcom GPU setting may have been switched in the config file, but i dont remember doing that - n not sure if that would affect in this way anyway.

Any thoughts?

[Klojum]

I don't have full debug logs yet - but can get them later in the week.

If you can spam your post with log entries, you might as well post the entire log file you have, VIA A TEXT UPLOAD WEBSITE, as requested just above the Post Reply button.

[DoubleT]

I don't have full debug logs yet - but can get them later in the week.

If you can spam your post with log entries, you might as well post the entire log file you have, VIA A TEXT UPLOAD WEBSITE, as requested just above the Post Reply button.

As I said, I don't have them yet, I was tailing a log file earlier and don't have access to reconnect til later this week.

I get why you say this but a few lines is hardly spamming. I'll upload full logs as usual when I can get at them. No need to be quite so efficious.

Was merely trying to see if it was something obvious that could be fixed before I managed to get back to site.

[popcornmix]

The error code is OMX_ErrorInsufficientResources.
Most likely you don't have enough gpu_mem on the Pi's that are failing.
https://www.raspberrypi.org/documentatio.../memory.md

[DoubleT]

The error code is OMX_ErrorInsufficientResources.
Most likely you don't have enough gpu_mem on the Pi's that are failing.
https://www.raspberrypi.org/documentatio.../memory.md

Ah that makes perfect sense, thanks!
Previous use of this box wasn't kodi so quite likely I missed that step when reconfiguring.