Consistent AV in VS when loading a solution with an .exe in it

Consistent AV in VS when loading a solution with an .exe in it by blindahl

Closed

as Won't Fix Help for as Won't Fix

Type:	Bug
ID:	778838
Opened:	2/8/2013 9:10:27 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

i have a .sln file that has devenv.exe in it as a project, used to start VS in the debugger when attaching gives problems with watches due to optimization.

quite often (90%+?) when I load this solution, I get an AV that closes the IDE and I have to reload it.

FWIW, this seems to be ONLY on this particular computer. Doing a similar thing on other computers or in a VM doesn't show the problem.

Details (expand)

Visual Studio 2012

File | Open Project, select devenv.exe
Save the solution for future use
Restart VS and try to load the solution

English

Windows 8

English

First-chance exception at 0x646d8c0d (msenv.dll) in devenv.exe: 0xC0000005: Access violation reading location 0xfeeefeee.

>    msenv.dll!CSolution::GetProjectFromHierarchy() + 0x2d bytes
    msenv.dll!CSolution::GetVirtualProjectFlags() + 0x37 bytes
    msenv.dll!CSolutionContextsExt::GetSolutionContextFromHierarchy() + 0x8d bytes
    msenv.dll!VsSupportErrorInfoSafeInvoke<<lambda_d220c0aa19ce89074930ebefb34f2815> >() + 0x2b bytes
    msenv.dll!CSolutionContextsExt::GetSolutionContextFromHierarchy() + 0x4c bytes
    msenv.dll!CConfigurationManagerExt::get_ActiveConfiguration() - 0x16ab31 bytes
    msenv.dll!VsSupportErrorInfoSafeInvoke<<lambda_c79362d56a048ae49dc48e24ed0fc5ea> >() + 0x2b bytes
    msenv.dll!CConfigurationManagerExt::get_ActiveConfiguration() + 0x16 bytes

Project would load properly.

0 attachments

Posted by Microsoft on 2/20/2013 at 5:16 PM

Thank you for the valuable feedback. Though we will not have a chance to address this issue in Visual Studio 2012, we will consider this feedback when planning for future versions of Visual Studio. Investments in this area will be weighed against the impact of other customer reported issues.

Posted by Microsoft on 2/10/2013 at 7:02 PM

Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.

Posted by Microsoft on 2/8/2013 at 9:50 AM

Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)