We’ve been rolling out computer sticks that have been upgraded from Win 8 with Bing to Win 10 Home. Using XiboClient.exe 1.7.5, our content will play for a few days to a week on some of these devices and then, after an out of memory error in the Application Event Log, the program will no longer run.
The faulting module is KERNELBASE.dll
Steps taken to attempt to mitigate:
clean Xibo Library folder
disable CEF and Frame Buffering for the Display Settings > Windows profile
confirm the default.config.xml file has both of these settings (manually entered due to no launch)
applied all recent win 10 updates
applied most recent Intel HD Graphics driver updates
ran chkdisk
updated from Xibo Player 1.7.3 to 1.7.5
The only thing that seems to work is a Re-imaging of the device, in this case, an Intel Compute Stick.
Prior to becoming inoperative, we were running the display 24x7 with one web layout region that would refresh every 3 minutes. Eventually, the dreaded memory leak with, apparently, the IE embedded control, would cause a crash. During that time, double buffering was enabled.
It seems like there should be a solution for this - something has been knocked sideways on Windows 10, but I can’t tell what. Windows thinks it is all fine and happy, and we have a fresh Xibo installation.
The .NET runtime error:
Application: XiboClient.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Management.ManagementException
at System.Management.ManagementException.ThrowWithExtendedInfo(System.Management.ManagementStatus)
at System.Management.ManagementObject.Initialize(Boolean)
at System.Management.ManagementBaseObject.get_ClassName()
at System.Management.ManagementClass.GetInstances(System.Management.EnumerationOptions)
at System.Management.ManagementClass.GetInstances()
at XiboClient.HardwareKey.GetMACAddress()
at XiboClient.HardwareKey…ctor()
at XiboClient.XiboTraceListener.InitializeListener()
at XiboClient.XiboTraceListener…ctor()
at XiboClient.Program.Main(System.String[])
This is occurring on a second device as well, this one only in service for a day. It seems like it started after the system was rebooted and a slew of WMI errors occurred. Most but not all were a flavor of
Error 0x80041006 encountered when trying to load MOF C:\WINDOWS\SYSTEM32\EN-US\PSMODULEDISCOVERYPROVIDER.MFL while recovering .MOF file marked with autorecover.