CODEWITHSUNDEEP
windowsvisual-studioclrwindows-10publishing
Matas Vaitkevicius
Matas Vaitkevicius

Reputation: 61499

VS2015 when trying to Validate Connection crashes Faulting module name: clr.dll, version: 4.6.1063.1

I am using VS2015 and trying to validate connection after importing publish profile generated by winhost, when I click on Validate connection VS2015 crashes.

I have tried cleaning up and rebuilding but hat didn't help, I have also restarted machine without any luck.

enter image description here

enter image description here

I have also enabled logging by running devenv /Log but can't make any sense out of ActivityLog.xml what went wrong exactly, I have uploaded it here

What went wrong with Visual Studio 2015 and how could I fix it?

UPDATE: I also tried resetting settings devenv /resetsettings but that didn't help.

EventLog shows following Error:

Faulting application name: devenv.exe, version: 14.0.24720.0, time stamp: 0x564ea97e
Faulting module name: clr.dll, version: 4.6.1063.1, time stamp: 0x5653653c
Exception code: 0xc0000005
Fault offset: 0x0007482d
Faulting process ID: 0x13f0
Faulting application start time: 0x01d17609c3c2b002
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report ID: 2fab7a5b-6003-417f-adb3-8f45ec987a72
Faulting package full name: 
Faulting package-relative application ID:

Update2:

As per @magicandre1981 request. I ran procdump -ma -i C:\dumps from command line before doing anything else. Then ran VS2015, went to publish and clicked on Test connection when VS crashed, there was a .dmp file in C:\dumps. Here's zipped dump file

Upvotes: 0

Views: 463

Answers (1)

magicandre1981
magicandre1981

Reputation: 28826

ok, the PDB is now online and I was able to look at the dzmp with Windbg. The crash (NULL_POINTER_READ_INVALID_POINTER_READ) happens at clr!MethodTableBuilder::CreateMethodChainHash+0x8a.

I have no idea how to fix it. Submit the issue to Microsoft via connect so that Microsoft can fix it with the Update 3.

Upvotes: 1

Related Questions