XiboClient Memory Growing, Causes Issues

I should add I am now using 1.4.2, and still have the same problem. This is running on Windows XP 32bit.

As a work-around, perhaps you can schedule a shell command to restart the unit in the wee hours of the morning. Open a cmd box in Windows, and type shutdown /?

Yes, I could do this, and sure this isn't pretty, but I would really like to understand what is actually happening and help resolve it if I could. Is anyone else seeing this?

Most likely candidate is IE.

The only way to be sure is to setup a client to only show a single image in a single region with no background image. Do you then see the same leak?

If not, then introduce a video. Does it leak then?

If not, introduce a website etc

Alex

I currently have a single region with single image (which happens to be black), with no image in background, colour is set to black. Memory slowly grows with each transition.

I have tried using same region setup with videos, videos play, and the memory slowly grows also.

I have not tried to introduce a website into the mix, as I had no application for a website.

Is there a way to know if its IE? Any logging I can turn on?

In that case it needs to be run through a Visual Studio debugger to see why that's happening.

I'll ask Dan to take a look when he can

Hi Alex,
do you happen to know if Dan has had a chance to run the debugger on the XiboClient to look at the memory leak?

If he had there would be some feedback on the question.

We're extremely busy at present. When there's time to look at this we will.

Ok no worries, would like to leave the question unanswered for now if that's ok. Thanks.

Hi,

Just a short feedback: With Xibo client 1.4.2 on WinXP, with my layout it takes 1-3 hours to get the OutOfMemory error.
I'm looking forward to your findings.

Sabine

Hi, sorry for the delay - as Alex says we are both extremely busy at the moment. I have run the client through a debugger for quite some time showing a single image and cannot recreate the problem you are experiencing.

What log level have you configured in options?
Are you sure there is only a single layout scheduled (can you confirm this using the client information screen)
What is the duration on your image?

This question was expired because it remained in the 'Needs information' state without activity for the last 15 days.

Hi,

Meanwhile we have September. Is there any outlook to this issue? I meanwhile installed a scheduled task that kills and restarts the Xibo client every 30 minutes.
I would love to stop that.... :-/

Hi,

I have the same problem. The old Xibo client 1.2 was oke and now I updated to 1.4.2, the memory grow. It is not explorer because in de old situation was it oke. It is now september and how to fix this problem for everybody who have the problem?
It is a very big problem what I see now!

Just wanted to add I have this problem occasionally and it seems to be associated with the RSS TICKER module - seems like certain feeds will bring up the unhandled exception -

I would suggest removing all the feeds and them putting them back in one at a time to see which one is the culprit

Now this question is marked as Expired - but I still have to restart my client every 30-60 minutes.

Do you have any news regarding this topic?

I'd like to add to this thread. I'm a new Xibo user and have finished rolling out Xibo 1.4.2 to 20 client computers. It exists on a mix of XP and Win7. It's been a full two weeks running since roll-out and already I've seen where the XiboClient.exe has started to grow in memory and then crash the computer (makes it lock up). Now because Xibo is so new to me still, I don't know if this issue affects all my clients. I'd log into the boxes now to check, but I don't want customers seeing me move around the screen checking processes during business hours.

I could write a script to stop and restart the process (I have to do this with SpiceWorks.exe on other boxes already), but I hate this solution.

Any new news?

Thanks.

No new news, because as previously discussed, it's IE that leaks the memory
and Microsoft haven't fixed it.

We've taken all possible mitigations for it. It's as good as it's going to
get without Microsoft fixing the source of the issue.

Thanks for your reply Alex, and I'd just like to mention that I really appreciate your work on this terrific open-source product.

I'm just throwing this out there, if it's any help at all. I have a "Test" client that runs Windows 7 sp1 32 bit with all patches up-to-date and running IE 10 and it appears it is not affected by this memory leak. When I watch the memory usage for XiboClient.exe, it starts at 36 MB and climbs to 44 MB over a couple of minutes and then goes back to 36 MB. Perhaps Microsoft has resolved the issue in newer patches or IE versions. However, this won't help with my clients running XP which can only go up to version IE 8.

Thank you.

Just an update to my last comment, I spoke too soon. Doesn't seem to matter the version of IE, xiboclient.exe just eats memory.

Alex, after much Googling, I can't accept your answer that it's a Microsoft IE issue that they have to solve. There is a person who wrote in the Xibo Forums that explains he doesn't even have IE installed and the client still eats memory... And the new client version 1.5 hasn't fixed it either.
https://answers.launchpad.net/xibo/+question/244518

Let's hope some version of 1.6 will stop the leak.

Has anyone tried this .net fix

http://support.microsoft.com/kb/912884

We think we have fixed the memory leak now - https://bugs.launchpad.net/xibo/+bug/1362705 and will be trying to put it in a 1.6.4 release.

1.7.0-alpha also replaces IE as the rendering control, so no more IE (unless you have powerpoint). Hopefully patching the other IE leak.