Search

AccessViolationException bug in .NET 4.5 Beta by Clarke La Prairie

Closed
as Fixed Help for as Fixed

6
0
Sign in
 to vote
Type: Bug
ID: 737108
Opened: 4/16/2012 7:40:32 AM
Access Restriction: Public
Moderator Decision: Sent to Engineering Team for consideration
0
Workaround(s)
5
User(s) can reproduce this bug
After installing Visual Studio 11 Beta, an AccessViolationException was constantly being thrown by some programs on my box.


Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling version

.NET Framework 4.5

Steps to reproduce

I tracked down the exception and found the sufficient conditions to reproduce the bug. (See the attached C# source file to reproduce).
-with .NET 4.5 Beta installed
-with a target frame work of .NET 4.0
-with a target platform of ANY CPU or x64
-access a string property, which is set to string.Empty, in a generic abstract base class, which has a static constructor.

Product Language

English

Operating System

Windows 7

Operating System Language

English

Actual results

AccessViolationException thrown

Expected results

AccessViolationException not to be thrown
File Attachments
File Name Submitted By Submitted On File Size  
AccessViolationExceptionBug.cs Clarke La Prairie 4/16/2012 3 KB
AccessViolationExceptionBug.cs Clarke La Prairie 4/16/2012 3 KB
Sign in to post a comment.
Posted by Microsoft on 7/10/2012 at 7:58 AM
Yes, it really did get fixed in RTM. The cut-off date for bug fixes that made it into the RC without any additional effort was around the beginning on April.
Posted by DeveloperGoblin on 6/28/2012 at 2:38 PM
I believe I am having this issue with .NET 4.5 RC as well. Once I uninstalled 4.5 and reinstalled 4.0 the issue went away.
Posted by philippe lombaers on 6/1/2012 at 12:03 PM
Hi,
It doesn't appear to be solved in release candidate.
Do you plan a fix before RTM ?
Thanks
Posted by Microsoft on 4/27/2012 at 12:04 PM
Yes, the RTM version of .NET 4.5 will have the fix. As a work-around simply use the emptry string literal, rather than String.Empty inside instance constructors or instance field initializers. Sorry for not mentioning that, but I assumed you had already figured that out, due to your very detailed repro source.

Gran Richins
.NET Codegen Developer
Posted by Darren Mombourquette on 4/26/2012 at 3:06 PM
With regards to the "future version of the product" does this mean the RTM version of .net 4.5. Our concern is currently our solution built on top of .net 4.0 is broken with the presence of .net 4.5 on a system causing us to pull the beta off of our development test environments. We would like to continue using the Beta version to discover any more issues before RTM however we are blocked at the momment becuase of this issue. We also need to understand if our solution can be supported with the presence of .net 4.5 once release.

Thanks,
Darren Mombourquette
prairieFyre Software Inc.
Posted by Microsoft on 4/19/2012 at 5:07 PM
Thank you for taking the time to identify and report this issue. I have fixed the problem and the change will be reflected in a future version of the product.

Grant Richins
.NET Codegen Developer
Posted by MS-Moderator10 [Feedback Moderator] on 4/16/2012 at 10:21 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 MS-Moderator01 on 4/16/2012 at 8:46 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)
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement