Xibo Client Error - Please Help! -Urgent!

tur6tur6 · February 25, 2016, 4:31pm

Hi Guys,

I’m using xibo client on a 2x2 videowall but I’m frequently getting Xibo client error message as follows.
A red cross appears as the background image and an error message pops up. Only sometimes, red cross appears in the regions of the videos.

I’m using a windows 7 64 bit. with Intel core i5, 8GB ram and NVIDIA NVS510 (4 DVI outs)
Framework and drivers are all up to date.

I believe computer should be fine but I cannot understand the problem here! Help please

The layout is with 2 small videos playing on each screen usually.

Error Message pops up like this:

It says in the pop up;
Xibo Client (as topic)
Unhandled exception has occurred in your application if you click continue the application will ignore this error and attempt to continue…

In details: System out of memory excepton : our of memory … etc…

Thank you in advance

Peter · March 3, 2016, 2:37pm

It’s hard to say what exactly is causing this (other than actually lacking memory).

Could you perhaps have a look in Windows event viewer for Xibo errors?

tur6tur6 · March 8, 2016, 9:26am

Hi Peter,

So when I worked on it a little bit more and got the same error. As you suggested; I looked in to event viewer for error and this couple of errors occurred. What should I do?

**

1st ERROR

**

Log Name: Application
Source: .NET Runtime
Date: 08.03.2016 11:19:34
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xiboplayer
Description:
Application: XiboClient.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException
Stack:
at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
at System.Reflection.RuntimeMethodInfo.UnsafeInvoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)
at System.Delegate.DynamicInvokeImpl(System.Object[])
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ScrollableControl.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Form.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application.Run(System.Windows.Forms.Form)
at XiboClient.Program.RunClient()
at XiboClient.Program.Main(System.String[])

Event Xml:

1026
2
0
0x80000000000000

3588
Application
xiboplayer

Application: XiboClient.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Reflection.TargetInvocationException
Stack:
at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[])
at System.Reflection.RuntimeMethodInfo.UnsafeInvoke(System.Object, System.Reflection.BindingFlags, System.Reflection.Binder, System.Object[], System.Globalization.CultureInfo)
at System.Delegate.DynamicInvokeImpl(System.Object[])
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.ScrollableControl.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Form.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.OnMessage(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.Control+ControlNativeWindow.WndProc(System.Windows.Forms.Message ByRef)
at System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef)
at System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext)
at System.Windows.Forms.Application.Run(System.Windows.Forms.Form)
at XiboClient.Program.RunClient()
at XiboClient.Program.Main(System.String[])

**

2nd ERROR

**

Log Name: Application
Source: Application Error
Date: 08.03.2016 11:19:34
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: xiboplayer
Description:
Faulting application name: XiboClient.exe, version: 2.0.0.0, time stamp: 0x56aa14cd
Faulting module name: KERNELBASE.dll, version: 6.1.7601.19135, time stamp: 0x56a1c79e
Exception code: 0xe0434352
Fault offset: 0x0000c52f
Faulting process id: 0xf1c
Faulting application start time: 0x01d17916b6d0ce6a
Faulting application path: C:\Program Files (x86)\Xibo Player\XiboClient.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: defab3f3-e50e-11e5-a86f-3464a92fa617
Event Xml:

1000
2
100
0x80000000000000

3589
Application
xiboplayer

XiboClient.exe
2.0.0.0
56aa14cd
KERNELBASE.dll
6.1.7601.19135
56a1c79e
e0434352
0000c52f
f1c
01d17916b6d0ce6a
C:\Program Files (x86)\Xibo Player\XiboClient.exe
C:\Windows\syswow64\KERNELBASE.dll
defab3f3-e50e-11e5-a86f-3464a92fa617

alex · March 8, 2016, 9:35am

kernelbase.dll errors are normally bugs in the .net framework. Make sure you have all the updates from Windows Update (including the optional ones) installed and then reboot.

The out of memory will be harder to find. You don’t say what version you’re running so if you’re not already upgraded to 1.7.6 then that’s the first job. You’ll need to run for a while with Task Manager open so you can see what in the system is using the memory and when.

So for example, does the memory slowly increase over time, or does it jump up in big steps? Is it definitely Xibo using the memory or is some other process leaking? Are the 8 videos all standard Xibo video media types? Or are they something you’re pulling in with a webpage?

tur6tur6 · March 8, 2016, 10:51am

Hi Alex!

Thank you for your quick reply.

-Windows is up to date including optional ones.
-We are using 1.7.6
-We already looked in to task manager and we didn’t observe any leakage by another sw.
-All media are uploaded. Not pulling from a webpage.

-Memory Usage

When a fullscreen video plays with a single region layout; XiboClient uses around 110.000K memory
When a multi-region layout plays, such as [8 videos, some text] or [4 videos, 4 images, some text], Xibo Client uses around 235.000K memory. Usually it fails during multi-region content.

COMPUTER PROPERTIES

Intel Core i5-4590 CPU 3.30GHz 3.30GHz
8 GB RAM
64 Bit OS
Windows installed on a 120GB SSD
NVIDIA NVS510 as graphics card. - 4 outputs( 2x2 videowall with mosaic property)

Thank you

alex · March 8, 2016, 4:43pm

It’s the progression over time that’s important though. Single snapshots don’t tell me anything.

You need to watch the memory usage and make observations, over time, based on what the Player is doing please. That’ll give us an idea what is happening.

tur6tur6 · March 8, 2016, 11:19pm

Hi Alex,

The error occurs in the few loops after we assign the layout to a player usually.
So what I mean is I’ve observed the error after few loops and I observed the memory usage when the error occurred multiple times. Thank you.

alex · March 9, 2016, 1:42pm

Right, so you start the layout running and the Player uses how much memory?

Then after it plays through once, how much memory is the Player using?

And after the second loop etc?

That’s what we need to know please.

javon27 · March 11, 2016, 10:16pm

I just got this error. I’ve been running this same campaign for a few days from my other post. The Xibo client is currently sitting at 300 MB.

See the screenshot below. As you can see, the layouts seem to all load except for the background image, which has been replaced by the red box with the cross in the middle.

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.OutOfMemoryException: Out of memory.
   at System.Drawing.Graphics.CheckErrorStatus(Int32 status)
   at System.Drawing.Graphics.DrawImage(Image image, Rectangle destRect, Int32 srcX, Int32 srcY, Int32 srcWidth, Int32 srcHeight, GraphicsUnit srcUnit, ImageAttributes imageAttrs, DrawImageAbort callback, IntPtr callbackData)
   at System.Drawing.Graphics.DrawImage(Image image, Rectangle destRect, Int32 srcX, Int32 srcY, Int32 srcWidth, Int32 srcHeight, GraphicsUnit srcUnit, ImageAttributes imageAttr)
   at System.Windows.Forms.ControlPaint.DrawBackgroundImage(Graphics g, Image backgroundImage, Color backColor, ImageLayout backgroundImageLayout, Rectangle bounds, Rectangle clipRect, Point scrollOffset, RightToLeft rightToLeft)
   at System.Windows.Forms.Control.PaintBackground(PaintEventArgs e, Rectangle rectangle, Color backColor, Point scrollOffset)
   at System.Windows.Forms.Control.PaintBackground(PaintEventArgs e, Rectangle rectangle)
   at System.Windows.Forms.Control.OnPaintBackground(PaintEventArgs pevent)
   at System.Windows.Forms.ScrollableControl.OnPaintBackground(PaintEventArgs e)
   at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
   at System.Windows.Forms.Control.WmPaint(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   at System.Windows.Forms.ContainerControl.WndProc(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1073.0 built by: NETFXREL3STAGE
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
XiboClient
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.0.0
    CodeBase: file:///C:/Program%20Files/Xibo%20Player/XiboClient.exe
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1038.0 built by: NETFXREL2
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1038.0 built by: NETFXREL2
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
Xilium.CefGlue
    Assembly Version: 3.0.0.0
    Win32 Version: 3.0.0.0
    CodeBase: file:///C:/Program%20Files/Xibo%20Player/Xilium.CefGlue.DLL
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1068.2 built by: NETFXREL3STAGE
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1064.2 built by: NETFXREL3STAGE
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1038.0 built by: NETFXREL2
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
XiboClient.XmlSerializers
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.0.0
    CodeBase: file:///C:/Program%20Files/Xibo%20Player/XiboClient.XmlSerializers.DLL
----------------------------------------
System.Web.Services
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1038.0 built by: NETFXREL2
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Web.Services/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Web.Services.dll
----------------------------------------
Microsoft.GeneratedCode
    Assembly Version: 1.0.0.0
    Win32 Version: 4.6.1064.2 built by: NETFXREL3STAGE
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Management
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1038.0 built by: NETFXREL2
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.6.1038.0 built by: NETFXREL2
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
Microsoft.GeneratedCode
    Assembly Version: 1.0.0.0
    Win32 Version: 4.6.1064.2 built by: NETFXREL3STAGE
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.GeneratedCode
    Assembly Version: 1.0.0.0
    Win32 Version: 4.6.1064.2 built by: NETFXREL3STAGE
    CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
BouncyCastle.Crypto
    Assembly Version: 1.7.4137.9688
    Win32 Version: 1.7.4137.9688
    CodeBase: file:///C:/Program%20Files/Xibo%20Player/BouncyCastle.Crypto.DLL
----------------------------------------
NetMQ
    Assembly Version: 3.3.2.2
    Win32 Version: 3.3.2.2
    CodeBase: file:///C:/Program%20Files/Xibo%20Player/NetMQ.DLL
----------------------------------------
Newtonsoft.Json
    Assembly Version: 7.0.0.0
    Win32 Version: 7.0.1.18622
    CodeBase: file:///C:/Program%20Files/Xibo%20Player/Newtonsoft.Json.DLL
----------------------------------------
AxInterop.WMPLib
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/Xibo%20Player/AxInterop.WMPLib.DLL
----------------------------------------
Interop.WMPLib
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/Xibo%20Player/Interop.WMPLib.DLL
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

EDIT: I should probably mention that the other display running the same campaign has not run into this error (yet). The display with the error, Display A, is running a version of the client that checks for null reference error in Media.cs. It is also running Intel graphics drivers that came with the pc. Display B, the one with no errors, is running an unaltered 1.7.6 client, and updated Intel graphics drivers. They have been running the same length of time. I will let them run over the weekend and see if it shows up on Display B as well.

tur6tur6 · March 12, 2016, 10:15am

Hi!

So I’ve tested the same layout at a different XiboClient and it didn’t give an error.

As a result I believe there’s something wrong with .Net Framework. I’ve tried to install some different versions of .Net on the PC which I’ve been receiving errors but still error occurs.

Thanks

alex · March 14, 2016, 9:19am

So it’s giving an OOM but the task manager screenshot shows the system has only used 77% RAM?

Edit: Although actually it may just be out of graphics memory judging by the call stack. I presume this computer has integrated graphics? Can you adjust the memory allocation in the bios to give it more video ram? I expect there isn’t enough for the amount of content you’re trying to show there.

alex · March 14, 2016, 9:20am

It would be worth doing a full hardware diagnostic then I think - memtest86 for a couple of full passes and then 24 hours of Prime95 to rule out any issues there before you go further.

bidaubayle · March 14, 2016, 3:02pm

I had the same problem last year, for the beginning it worked very well, but after few months there are so many files generated in xibo library folder and bigger and bigger database that it shows windows errors as described by the user above. Shrinking the database and file folder with restoring an old backup of xibo datas (database and library) seems to solve this problem and it will work well, until the next errors in few months again…

alex · March 16, 2016, 4:31pm

The database will only grow as you describe if you’re not running the maintenance script to clean out old logs and stats records. This is covered in the CMS Post Installation guide.

system · March 4, 2020, 5:04pm