Hello, after updating AVG to the latest version I noticed that some applications does not run, they just quit after starting. Adding those applications as exceptions does the trick. However, since I am a develper of some of those applications I invetigated the issue.
The problem happens when the applications check for a Mutex to see if they are already running. This is a very common pattern as specified here: http://stackoverflow.com/questions/19147/what-is-the-correct-way-to-create-a-single-instance-application
However, it seems that AVG is delaying the Mutex wait, so when the program does if (mutex.WaitOne(0, true)) it returns false even if the mutex does not exist and the program thinks it is already running. However doing if (mutex.WaitOne(1000, true)) works as expected since we introduce a delay.
Please confirm this is a bug in AVG and if you are working on a fix. Please let me know if you need more information.
Hello Ari. I apologize for the inconvenience caused. Could you please let us know the AVG product you have updated on your computer? Also, we would request you to try disabling the AVG and let us know if the issue still persists. Please feel free to contact us for any further assistance. Thank you.
Hello Ari, we are sorry to know that. We request you to submit a sample for analysis ( http://avgread.me/1QPQ1KH ) so that our developers can analyze the files. Please do not hesitate to get back to us for further assistance. Thanks.
I'm an independent software vendor, and a whole bunch of my customers have this exact same problem: my product keeps exiting, as a call to Mutex.WaitOne(0, true) returns false.
It's been really hard to track down, as you don't expect something as fundamental as Mutexes to be broken by a third party app. I eventually got all affected customers to send me a list of what processes are running on their machine, and the only thing they all had in common was AVG.
A quick search for "AVG" and "Mutex" returned this result which confirmed the same exact, very specific problem.
I suspect a lot of application vendors are suffering from this problem, only they haven't tracked it back to its source yet.
Disabling AVG fixes the problem.
The product is AVG Internet Security 2015.0.6086
Virus Database version: 4392/10222
It's been really hard to track down, as you don't expect something as fundamental as Mutexes to be broken by a third party app. I eventually got all affected customers to send me a list of what processes are running on their machine, and the only thing they all had in common was AVG.
A quick search for "AVG" and "Mutex" returned this result which confirmed the same exact, very specific problem.
I suspect a lot of application vendors are suffering from this problem, only they haven't tracked it back to its source yet.
Leon, Please follow the Komal Sathish Kunmar (AVG Technologies) posting.
AVG Guru