This project has moved. For the latest updates, please go here.
7

Closed

Access violation errors after Anniversary Update

description

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.
Closed Feb 1 at 1:13 PM by KindDragon
v2.5.1

comments

mpietras wrote Aug 3, 2016 at 4:53 PM

Faults for me now too, just after the update, and identical ntdll.dll revision. I've been using VLD for a long time but the Windows Anniversary update broke it and I must disabled it from my debug builds for them to operate now.

Tynril wrote Aug 4, 2016 at 6:32 AM

I had that same issue using the prerelease builds, and reported it there: http://vld.codeplex.com/workitem/10610

Too bad it didn't got fixed before Redstone shipped to the general public. :(

ioannise wrote Aug 7, 2016 at 11:00 PM

Can you confirm that it only happens with x64 builds and not with x86 builds ?
Thanks.

jcnhal wrote Aug 8, 2016 at 10:38 AM

I can confirm same problem with 64bit build.

Call stack prior to main:
ntdll.dll!RtlAllocateMemoryZone() Unknown
0000000000000001()  Unknown
000000d87e7ff4b0()  Unknown
000000d87e7ff030()  Unknown
ntdll.dll!LdrpInitializeNode()  Unknown
ntdll.dll!LdrpInitializeGraphRecurse()  Unknown
ntdll.dll!LdrpInitializeGraphRecurse()  Unknown
ntdll.dll!LdrpInitializeGraphRecurse()  Unknown
ntdll.dll!LdrpInitializeProcess()   Unknown
ntdll.dll!_LdrpInitialize() Unknown
ntdll.dll!LdrInitializeThunk() Unknown
32bit builds are fine.

ioannise wrote Aug 8, 2016 at 10:42 PM

Ok, thanks, i have prepared a fix for this, apparently there was a change in the x64 ntdll.dll module loader code.
I'll post the fix once sufficiently tested.

rj2Skipper wrote Aug 10, 2016 at 11:17 AM

Same issue here (x86 executable)
after commenting the #include line, my application starts ok

dependency viewer states something about Side-By-Side-Configuration invalid for vld_x86.dll

ciao Ralf

behnazak wrote Aug 29, 2016 at 5:33 PM

Hi,

Any updates on the status of this. I have the same problem.

mpietras wrote Aug 31, 2016 at 2:59 PM

hate to do a +1 comment, but, how's your change testing out? several pending changes we'd like to revert to start using this again...

ioannise wrote Aug 31, 2016 at 6:18 PM

Yeah I know its been a while, the change works reliably on Win 10 Anniversary update, but i haven't had a chance to test it on older environments. I'll try to push it later tonight on github, so you can test it as well...

ioannise wrote Sep 1, 2016 at 11:29 PM

Ok so I pushed the change
Anyone kind enough to build test and confirm ?

mpietras wrote Sep 2, 2016 at 6:11 PM

Pulled your latest and built it release 64 and can confirm that it has resolved the Win 10 Anniversary fault... thank you! Have not tested older environments at this point though...

Specialist89 wrote Sep 25, 2016 at 4:02 PM

Hello.

Is there any update, or a new installer that fixes this bug? If so, how do I get it?

Thank you!

jcnhal wrote Oct 6, 2016 at 8:10 AM

Finally got around to getting the code to build on my machine.
Using v2.5 tag and applying this patch https://github.com/ioannis-e/vld/commit/48d9fef04a3117747c594afaf3036105713323d3
I can confirm x64 works as per x86.
I also switch the platform toolset to v140 (instead of v140_xp) as v140_xp doesn't seem to be installed on my system.

FYI: Applying the patch onto the master branch resulted in new memory leaks being detected. I'm not sure they're real.

renglund wrote Feb 1 at 7:02 AM

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.

renglund wrote Feb 1 at 8:05 AM

I now tested on another machine (running windows 10 education instead of 10 home) and there the released version works and gives the same leaks.
They might be still false positives but as far as I can tell no new leaks/false positives was detected/introduced in the patch.