After various tests I have determined, Acquire Player V3.8 is restarting after a period of time (with the amount of time varying). I notice in Task Manager, when looking at the Processes tab with the Threads and Handles Columns displayed, AcquirePremier.exe is leaking and the Handle count slowly increases (particularly if the content changes to video files). Acquire Player then restarts and this is noted in the logs; Handle Count too high (10500). How can this be resolved?
Acquire Player will manage Memory Leaks and whilst the cause of this is not caused by Acquire Player, it can often manifest itself with it restarting once the Handle Count threshold has been reached. As the count will also steadily increase as the content plays, Acquire Player will restart even if the threshold is increased.
During substantial testing of the Hardware and Software for the problem, we isolated the issue and found the cause to be the brand of HDD being used. In this case, a Kingston SSD (Solid State Drive) Now 300. When this was replaced with an Intel SSD and system rebuilt to the same specifications as before the Resource Leak or Handle Count was no longer causing Acquire Player to restart.
Often variations in system builds can give an indication of the diagnostics you can perform, however you should also be sure to check all other aspects of the hardware and software if the symptoms are different to the example we have used above. See: How to troubleshoot a handle leak? for more information.
Additional links that you may find useful include: Debugging a GDI Resource Leak and Process Explorer
Article is closed for comments.