Page 4 of 4

Re: An exception was thrown by a TaskScheduler

Posted: 11 Jun 2014 19:48
by radio42
Ohh yes that looks indeed like a similar issue the other user is having.
Look at your free memory! It is 0!!
So some other processes must eat up all your memory!
You might use the task manager and click on Show processes of All users and then try to locate the processes which use up all you 12GB of memory...

As PF and the MLS together only use 900MB there must be some other processes using the remaining 11GB!

Re: An exception was thrown by a TaskScheduler

Posted: 12 Jun 2014 08:21
by mart3223
Hi Bernd,

Quick update, after 24 hours of running at this moment Free memory is 3536MB. As attachment the running processes of all users, but seems me oké no big memory killers.
processen.png
processen.png (83.17 KiB) Viewed 13561 times

Re: An exception was thrown by a TaskScheduler

Posted: 13 Jun 2014 09:54
by mart3223
And again an update after again 24 hours. At this moment stable, but free memory only 91mb. (System at this moment 4 days and 16 hours online) But it seems that is not a problem in windows: http://serverfault.com/questions/565539 ... ce-monitor it is normal. Bernd, what do you think? PF Update solved it? Or do we need to check other things?

Re: An exception was thrown by a TaskScheduler

Posted: 13 Jun 2014 20:17
by radio42
Not at the moment but I am also looking at other things in parallel what might be causing your issues.

Re: An exception was thrown by a TaskScheduler

Posted: 17 Jun 2014 15:20
by radio42
Please update to v3.0.13.27 !

This should fix a file handle leak in the audio lib I am using under certain conditions when using overlays.
An out of memory exception might be thrown when running out of file handles.

To monitor your audio handles being used, you might open the 'About' dialog. The number of audio handles should not constantly increase over time.

Re: An exception was thrown by a TaskScheduler

Posted: 17 Jun 2014 16:02
by mart3223
Bernd,

Thanks, I have installed the update (.27) I will monitor the Audio Handles (at this moment only 18, last week I have seen them over the 500). Hope that this solve it! I will keep you up-to-date!

Re: An exception was thrown by a TaskScheduler

Posted: 18 Jun 2014 10:34
by mart3223
Hi Bernd,

At this moment the Audio Handles increased to 202 in +/- 20 hours of running version .27. I don't know what is normal?

Re: An exception was thrown by a TaskScheduler

Posted: 18 Jun 2014 15:10
by radio42
I just took a look via TV.
And yes, all is normal. You are currently using 130 audio handles, which is normal, as you are using both cartwalls with around 100 carts in total.
Each cart uses 1 audio handle, so all is normal and expected - no leaks!
There is not even an issue when using 200 or more audio handles (e.g. in case you use even more carts or the standby players)...it is just important, that the number does not increase and increase over time...but that is not the case anymore!

Re: An exception was thrown by a TaskScheduler

Posted: 18 Jun 2014 21:41
by radio42
Depends if you use the cartwalls and how many carts they use?
If I should take a look to your system via TeamViewer, just send me a PM with the details...

Re: An exception was thrown by a TaskScheduler

Posted: 19 Jun 2014 08:16
by mart3223
Thanks Bernd, wonderfull service. I hope that we are stable then! When anything happens what I think is related to the problem I will post it. But I think, everything is fine at the moment!