Xibo Player freezes after several hours connected to Sharp NEC C750Q

The Xibo Player freezes after several hours connected to a Sharp NEC C750Q from KAMRUI Essenx E2 Mini PC, 16GB RAM 512GB SSD Mini Computers,12th Alder Lake N97 running Windows 11 Enterprise 64 Bit 24H2. The digital signage is displaying pictures (Formats: PDF, JPEG, PNG) and videos (edited in Handbrake down to Fast1080p30).

The system is running:

“XiboClient.exe” “4.405.3.0” “Xibo Open Source Digital Signage” “4.405.3.0” “Xibo Digital Signage”
“XiboClientWatchdog.exe” “1.0.4.0” “XiboClientWatchdog” “1.0.4.0” “”

Here is an event log that keeps popping up the most.

Log Name: Xibo
Date: 10:04:41 am 20-Nov-25
Event ID: 0
Computer

Source: Xibo
Type: 1
User: N/A
Category: None
Description:
System.OutOfMemoryException: Insufficient memory to continue the execution of the program.
at System.Windows.Media.Composition.DUCE.Channel.SyncFlush()
at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet)
at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam)
at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)

1 Like

Looks like this is caused by a memory leak, and I cannot provide a long term fix at the moment. Still, I just want to thank you for the way you described the issue, it was exemplary.

As a temporary workaround, you can increase the virtual memory in Windows, which should delay the impact of the leak.

I increased the virtual memory as you recommended. I will wait until Monday to see if that resolves the issue. Thank you for the suggestion.

Increasing the virtual memory did not resolve the issue. However, trying different resolutions seems to fix the issue. I set the display resolution to 3840 x 2160 with a scale of 300% for the NEC M551 and C750Q models. Schweminska, thank you for your help.

1 Like