IE Browser Issues about xibo-dotnetclient HOT 6 CLOSED

Dan Garner commented: We had an implement ion of cefsharp in the 1.7 windows player, but it was buggy to say the least and we didn't have the time available to make it reliable enough for the sort of up-time we need.

If you can get it working and reliable then we'd be very interested in that as it would be a quick win for the Player in terms of bringing the browser capabilities inline with what is current.

Our beginnings of a WPF player uses cefsharp and we think that the memory issues are tackled. Unfortunately there are other things we need to do there to make it work - but if its useful you can find that implementation here: [https://github.com/xibosignage/xibo-windows]

from xibo-dotnetclient.

I have implemented CEF at a basic, but seemingly fully functional level. I have it loaded on a PC right now and am monitoring it with our RMM tool. Do you recall what kind of memory growth was the issue? I fired it up and made a playlist that refreshed every 2 seconds and left it running for 24 hours. I only saw about 25mb of memory growth over those 24 hours. I am by no means an expert programmer so I am going to see if a friend of mine can take a look with me and see if there is anything I can load differently to help with disposal and things.

from xibo-dotnetclient.

I am not sure if I have any examples which were a particular problem, but from memory we would get crashes after a few days of usage. This was with the standard Xibo widgets, text, weather, twitter and so on.

It may well be that cefsharp itself has moved on and is better at managing memory.

This is how we did it before, if you'd like to compare? https://github.com/xibosignage/xibo-dotnetclient/blob/release/tuttle/Media/CefWebMedia.cs

from xibo-dotnetclient.

Dan,
I have not had a chance to go extend my deployment further than basic functionality but you MIGHT want to revisit CEFSharp. I have included a memory monitor graph from my monitoring system of the XiboClient.exe This is using CEFSharp > v70. I dont recall exactly which version.

from xibo-dotnetclient.

We're going to have a look at this: #86 to see if that is a possible drop in replacement / how it works, etc.

from xibo-dotnetclient.

A possible Chromium implementation:
#87

from xibo-dotnetclient.