After the Windows 10 Anniversary Update (1607), I get access violation errors with Visual Leak Detector.
Exception thrown at 0x00007FF8A7B97FE7 (ntdll.dll) in Axxxxxxx4_64.exe: 0xC0000005: Access violation reading location 0x00007FF8A7CD5252.
Module Information on ntdll.dll:
10.0.14393.0 (rs1_release.160715-1616)
I think, it's this line (during base member initialization):
QApplication(argc, argv)
I'm not experienced with VLD. I just started using it few days ago. But it worked fine until the Windows update, so it might be a good guess.
Comments: I've applied the patch and it now works in for our software again. Just starting and directly exiting our application did not detected any leaks. Though, when using the application it detected quite some new leaks, which most of I know is real and fixable. A few of them might be false positives. All new leaks involves new functionality in our application so it might very well real leaks.
Exception thrown at 0x00007FF8A7B97FE7 (ntdll.dll) in Axxxxxxx4_64.exe: 0xC0000005: Access violation reading location 0x00007FF8A7CD5252.
Module Information on ntdll.dll:
10.0.14393.0 (rs1_release.160715-1616)
I think, it's this line (during base member initialization):
QApplication(argc, argv)
I'm not experienced with VLD. I just started using it few days ago. But it worked fine until the Windows update, so it might be a good guess.
Comments: I've applied the patch and it now works in for our software again. Just starting and directly exiting our application did not detected any leaks. Though, when using the application it detected quite some new leaks, which most of I know is real and fixable. A few of them might be false positives. All new leaks involves new functionality in our application so it might very well real leaks.