N
Nitin Khobragade
Guest
We have a product in which our windows service launches an agent (watchDog) and this agent launches another agent (actual product). This product is tested successfully on windows 7, 8 and 10. But on clients location who has only windows 10 creates a strange problem. When it calls boost::filesystem::exists OR CoInitializeSecurity the call does not complete, does not throw any exception but it launches itself. The parent ID of first instance is correct, its of watchDog agent. But when problem occurs we see two entries of the actual agent, parent ID of first entry is watchDogAgent but the parent ID of second entry is process ID of first entry.
This does not happen every time, randomly it happens but at same place. If i comment out the code then agent runs flawlessly. If i comment any one of the problem code, issue occurs exactly at second place.
Please check this image where the output of wmic command is shown when issue occurred, issue occurred 8 seconds after the first instance:The second instance does not execute anything, not even first line of main. First instance i can kill from taskmanager as it is the only instance listed there. When I kill second instance using 'taskkill' command first time its successful but its entry still persist in wmic output. When i try to kill it again i get 'access denied' error. After 2 to 5 minutes the entry is removed from the wmic output automatically.
Continue reading...
This does not happen every time, randomly it happens but at same place. If i comment out the code then agent runs flawlessly. If i comment any one of the problem code, issue occurs exactly at second place.
Please check this image where the output of wmic command is shown when issue occurred, issue occurred 8 seconds after the first instance:The second instance does not execute anything, not even first line of main. First instance i can kill from taskmanager as it is the only instance listed there. When I kill second instance using 'taskkill' command first time its successful but its entry still persist in wmic output. When i try to kill it again i get 'access denied' error. After 2 to 5 minutes the entry is removed from the wmic output automatically.
Continue reading...