Xibo player has stopped working

I have 3 Windows Xibo clients 1.7.5. Always after weekend have black screen with “Xibo has stopped working” on all of them.
Here is details:

Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: XiboClient.exe
Problem Signature 02: 2.0.0.0
Problem Signature 03: 5620b816
Problem Signature 04: System.Drawing
Problem Signature 05: 4.0.30319.34270
Problem Signature 06: 55adcf40
Problem Signature 07: 229
Problem Signature 08: 0
Problem Signature 09: System.OutOfMemoryException
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

What is wrong?
Thanks.

Seems like a Memory issue, we had one report of it on earlier versions, but we didn’t hear back if the new version fixed it for him or was the problem somewhere else.

Could you please tell me more about spec of your PCs?
Also are there any other applications installed on them, that could use the memory?

I am using DELL WYSE with WINDOWS 7 64-bit:
Processor - Intel Xeon CPU E5-2670, 2.60 GHz (2 processors)
RAM - 4 GB

I am also experiencing the same problem (among others). Player 1.7.7 randomly stops working, with no apparent pattern in the length of time for which it will run before it stops. Below are the errors retrieved from the Event Viewer on one of the affected machines:

Log Name:      Application
Source:        .NET Runtime
Date:          5/25/2016 1:50:33 PM
Event ID:      1026
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Xibo1
Description:
Application: XiboClient.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 6F271E99

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name=".NET Runtime" />
    <EventID Qualifiers="0">1026</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-05-25T17:50:33.000000000Z" />
    <EventRecordID>2469</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Xibo1</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Application: XiboClient.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 6F271E99
</Data>
  </EventData>
</Event>

And one second later:

Log Name:      Application
Source:        Application Error
Date:          5/25/2016 1:50:34 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Xibo1
Description:
Faulting application name: XiboClient.exe, version: 2.0.0.0, time stamp: 0x570cdd87
Faulting module name: mshtml.dll, version: 11.0.9600.18315, time stamp: 0x571af57d
Exception code: 0xc0000005
Fault offset: 0x00fd1e99
Faulting process id: 0x770
Faulting application start time: 0x01d1b6ad23420ef9
Faulting application path: C:\Program Files (x86)\Xibo Player\XiboClient.exe
Faulting module path: C:\Windows\SysWOW64\mshtml.dll
Report Id: 2e0efa59-22a1-11e6-97e8-d02788d19ba7
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2016-05-25T17:50:34.000000000Z" />
    <EventRecordID>2470</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Xibo1</Computer>
    <Security />
  </System>
  <EventData>
    <Data>XiboClient.exe</Data>
    <Data>2.0.0.0</Data>
    <Data>570cdd87</Data>
    <Data>mshtml.dll</Data>
    <Data>11.0.9600.18315</Data>
    <Data>571af57d</Data>
    <Data>c0000005</Data>
    <Data>00fd1e99</Data>
    <Data>770</Data>
    <Data>01d1b6ad23420ef9</Data>
    <Data>C:\Program Files (x86)\Xibo Player\XiboClient.exe</Data>
    <Data>C:\Windows\SysWOW64\mshtml.dll</Data>
    <Data>2e0efa59-22a1-11e6-97e8-d02788d19ba7</Data>
  </EventData>
</Event>

The affected machine is a NetTop, running the following:

Win 7 64 bit
AMD E-350 Processor 1.60 GHz
4 GB RAM

I have the following programs installed on this machine (as seen from the Programs and Features section of the Control Panel):

  • Atheros Driver Installation Program
  • Intel® PROSet/Wireless WiFi Software
  • Mircosoft .NET Framework 4.5.2 ***
  • Mozilla Firefod 46.0.1 (x86 en-US)
  • Mozilla Maintenance Service
  • Realtek Ethernet Controller Driver
  • UltraVnc
  • Xibo Player

The only program running on this computer is Xibo Player, so there shouldn’t be any problem with interference from other programs.

With regard to the .NET Framework version, I had version 4.6 installed, but the continuing problems led me to try version 4.0, which did not resolve anything, then version 4.5, which also has not resolved anything. I have attempted to gather information from the logs for the player, but they aren’t telling me much:

<trace date="2016-05-25 13:49:57" category="Audit"><logdate>5/25/2016 1:49:57 PM</logdate><thread>ScheduleAgentThread</thread><method>ScheduleManager - GetScheduleXmlString</method><message>Getting the Schedule XML</message>
</trace>
<trace date="2016-05-25 13:49:58" category="Info"><logdate>5/25/2016 1:49:58 PM</logdate><thread>RegisterAgentThread</thread><method>RegisterAgent - Run</method><message>Thread Woken and Lock Obtained</message>
</trace>
<trace date="2016-05-25 13:49:58" category="Audit"><logdate>5/25/2016 1:49:58 PM</logdate><thread>LogAgent</thread><method>RegisterAgent - Run</method><message>Thread Woken and Lock Obtained</message>
</trace>
<trace date="2016-05-25 13:50:04" category="Audit"><logdate>5/25/2016 1:50:04 PM</logdate><thread>ScheduleManagerThread</thread><method>ScheduleManager - Run</method><message>Schedule Timer Ticked</message>
</trace>
<trace date="2016-05-25 13:50:08" category="Audit"><logdate>5/25/2016 1:50:08 PM</logdate><thread>UI Thread</thread><method>Media - SignalElapsedEvent</method><message>Media Complete</message>
</trace>
<trace date="2016-05-25 13:50:08" category="Audit"><logdate>5/25/2016 1:50:08 PM</logdate><thread>UI Thread</thread><method>Region - DurationElapsedEvent</method><message>Media Elapsed: http%3A%2F%2Fwww.accuweather.com%2Fen%2Fus%2Falbany-ny%2F12210%2Fhourly-weather-forecast%2F329673</message>
</trace>
<trace date="2016-05-25 13:50:08" category="Audit"><logdate>5/25/2016 1:50:08 PM</logdate><thread>UI Thread</thread><method>Region - SetNextMediaNode</method><message>New media detected image</message>
</trace>
<trace date="2016-05-25 13:50:08" category="Audit"><logdate>5/25/2016 1:50:08 PM</logdate><thread>UI Thread</thread><method>Region - CreateNextMediaNode</method><message>Creating new media: image, 20</message>
</trace>
<trace date="2016-05-25 13:50:08" category="Audit"><logdate>5/25/2016 1:50:08 PM</logdate><thread>UI Thread</thread><method>Region - StartMedia</method><message>Starting media</message>
</trace>
<trace date="2016-05-25 13:50:08" category="Audit"><logdate>5/25/2016 1:50:08 PM</logdate><thread>UI Thread</thread><method>Region - Stop Media</method><message>Stopping media</message>
</trace>
<trace date="2016-05-25 13:50:11" category="Audit"><logdate>5/25/2016 1:50:11 PM</logdate><thread>UI Thread</thread><method>Media - SignalElapsedEvent</method><message>Media Complete</message>
</trace> 

When I attempted to check the logs on the CMS, I could only see the following, which is from ~30 minutes prior:

156869 	2016-05-25 13:19:54 	Client 	[ScheduleManagerThread] ScheduleManager - Run 	Schedule Timer Ticked
156868 	2016-05-25 13:19:44 	Client 	[ScheduleManagerThread] ScheduleManager - Run 	Schedule Timer Ticked
156867 	2016-05-25 13:19:36 	Client 	[UI Thread] Region - SetNextMediaNode 	New media detected text
156866 	2016-05-25 13:19:36 	Client 	[UI Thread] MainForm - DurationElapsedEvent 	Region Elapsed
156865 	2016-05-25 13:19:36 	Client 	[UI Thread] Region - SetNextMediaNode 	Media Expired:(524,44,556,756,text,) . Reached the end of the sequence. Starting from the beginning.

I checked through the forum, and it seems that I need to be using IE 11, so I checked, and that is, indeed, the version I have. I found a post (Enabling HTML5 in the Windows .net Player) that seemed to indicate a need to make changes to the registry, so I took that step, as well, but that hasn’t fixed anything, either.

I am truly bewildered as to what may be happening, and I’m hoping that someone can point me in the right direction.

Thank you!

Chris

Yours is probably a different issue - mshtml.dll in your message is the thing causing Xibo to crash. That is the core dll for the webbrowser control Xibo uses to show text/web content.

The exception code: 0xc0000005 usually indicates some memory issue, not necessarily running out of memory, but accessing some memory it shouldn’t access.

There are some reports of this being due to an incorrectly registered javascript dll - which you could try to reregister:

C:\Windows\System32\regsvr32.exe C:\Windows\System32\jscript.dll
C:\Windows\SysWOW64\regsvr32.exe C:\Windows\SysWOW64\jscript.dll

The unfortunate fact of the matter is that when mshtml does go, there is very little we can do to stop it taking out the rest of the application. Setting aside any dll related issues, it is most likely to be something on a webpage you are displaying causing the problem.

We have been making some improvements to tighten the integration with the Xibo watchdog, which we will release with 1.7.8. These improvements should help get Xibo started up again. A plaster/bandaid rather than a cure.


Edit: I forgot to say that the very first thing to do (before the above) is to open Internet Explorer (32bit mode) and disable any browser add-ons installed.