Thanks for your time and effort Dan regarding this issue, I’m surprised there are no more reports of this since I see many people talking about running Intel Compute sticks and such, which are very similar HW to our clients.
Anyhow, to answer Irfan, yes we were (and are) running the maintenance script all along, from cron every 5 minutes; our CMS is Debian based.
We continue to have this happen to several (one or two, each time different) clients approximately once per day, and as suspected running the “result” filter did not catch anything due to the mentioned filter column drop/timing “problem” with the process monitor.
We will definitely implement your modified client with Handle tie-in on a couple of machines but I’d like to wait out the current setup with our test client (it’s bound to crash sooner or later :)). Filtering by [PATH contains XLF] is accumulating a manageable amount of real-time data and clearing the log once or twice a day (assuming no “crash”) is not problematic, and this will definitely catch the offender since we’re logging everything before and after the event (you’re right that saying “crash” or “freeze” may be slightly misleading as to what we’re talking about in this case).
I have no doubt that you know exactly what you’re doing but I’m slightly concerned that calling Handle after the Xibo client has already logged the error may miss the problem event if the lock is indeed some split-second thing?
Also I think we should keep in mind that either Irfans registry tweak and/or our setup of folder options regarding thumbnails have UNDOUBTEDLY reduced the frequency at which the problem occurs.
We’ll report back as soon as there’s any results.