Xibo Unknown Exception Error

[aramo]

Hello!

We have CMS version 4.0.14, and Windows players running version 403.

Every so often, we run into this error message about some kind of unknown exception, and it freezes up our machines, requiring us to have to remote into it and reboot it every time. At first, I thought it may be because of some memory leak somewhere in the Xibo player software, but we have other similarly spec’ed machines with Windows 11 running the same layout as the ones that are encountering errors, but never have this issue. See screenshot of the error below.

Any suggestions or ideas as to what may be causing this?

Thanks!

[pitoco02]

This is a problem I’ve been facing for years.
It is caused by the embedded browser for Xibo Windows (CefSharp).
Occasionally, content loads incorrectly for any reason, and this error pops up on the screen.

I created some mechanisms to deal with this automatically, such as maintenance scripts that restart the software when it identifies that there has been a software failure.
However, it is a “solution” that only disguises the problem, but does not solve it.

The only way I was able to permanently reduce the incidence of this error was by upgrading my Windows computers to at least 8GB RAM.

Another solution for Xibo to be able to use another embedded browser would be to encourage the correction of WebView2’s WPF controls in this GitHub topic. But I’ve already given up. It’s an age-old problem that it seems will never correct, which at the moment makes us “hostage” to the use of CefSharp as a browser embedded in Xibo for Windows.

This thread here in the community may give you some alternative solutions as well.

Windows Client - Option to use WebView2 (Edge) as the primary rendering engine

I would like to request an option in the device configuration profile that allows us to use WebView2 (Edge) as the main rendering engine instead of CefSharp. The reason behind this request is that over the past few years, I have encountered recurring errors with CefSharp appearing on the screen, and despite upgrading processors or increasing RAM, this issue continues to persist. On the other hand, I have never experienced such problems when layouts are rendered using Edge. I am aware that ther…

[aramo]

Thanks so much for your reply! Super helpful! Our machines have at least 8GB of RAM, but it looks like they were at at least 75% RAM usage or higher. We will try a RAM upgrade and see if that resolves the issue for us.

Here’s hoping we will be able to use Webview2 at some point in the near (or maybe distant) future

[pitoco02]

@aramo

Our machines have at least 8GB of RAM, but it looks like they were at at least 75% RAM usage or higher.

This makes sense.
I upgraded to at least 8GB RAM, however my devices are Windows 10.
Win 11 actually consumes more RAM. So I think the RAM upgrade would be valid at this point