This has been bugging me heaps. I have finally got codeI can send in. Ever since 3.2.x certain generally larger lambda expressions would kill visual studio without warning. Very very annoying as as generally you loose code.
Steps to Reproduce:
Somewhere after typing Replace and closing bracket it dies
var xdoc = XDocument.Parse("").XPathSelectElements("").Select();
:)
var xdoc = XDocument.Parse("").XPathSelectElements("").Select(a => a.ToString().Replace());
:(
Actual Results:
Kabooom!!!
Faulting application devenv.exe, version 9.0.30729.1, time stamp 0x488f2b50, faulting module kernel32.dll, version 6.0.6001.18000, time stamp 0x4791a81d, exception code 0xe053534f, fault offset 0x0002f35f, process id 0x13a0, application start time 0x01c9763ef1af48a2.
Fault bucket 882210388, type 1
Event Name: APPCRASH
Response: None
Cab Id: 0
Problem signature:
P1: devenv.exe
P2: 9.0.30729.1
P3: 488f2b50
P4: kernel32.dll
P5: 6.0.6001.18000
P6: 4791a81d
P7: e053534f
P8: 0002f35f
P9:
P10:
Expected Results:
World peace.
Bug Report
B132967
Visible to All Users
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Hi Bart,
Thank you for the report.
However, I'm unable to reproduce the problem you described locally. It is possible that it has already been fixed. So, I suggest that you install the latest daily build, and see whether this fixes the problem. I'll provide you with the instructions on how to download it via e-mail.
Thanks,
Vito
New build… Still happens.
Just in case I was not clear, you have to type the statment. I can happily cut a paste the line in and it continues…
Ensure you have the Xml.Linq and Xml.XPath namspaces added before typing.
As I also run resharper I turn it off an restated VS to test it…
Also this was tested on 2 different machines.
Hi Bart,
We're sorry to hear that the problem exists in the latest build.
However, I'm still unable to reproduce it locally. Can you please post here a small sample, video illustrating the issue in action? Also, it would be great if you can provide us with the problem's call stack, so that we can examine it. Please refer to the following article to learn how to capture it:
http://diditwith.net/2006/08/07/DebuggingVisualStudio.aspx
Thanks,
Vito
Attached are vids of it happening.
As you will see it seems to be very specific to the typeing order. Looks like the being a semi colon effects things too.
Believe it or not doing native stack dumps is not my favorite thing the world so please let me know if you still can't repro or the vids don't shed any light and I'll try and get one done in the next week.
Cheers
Bart
Hi Bart,
Thank you for the sample video.
I've tried to perform exactly the same steps, but I'm still unable to reproduce this crash. Attached is a sample video, illustrating the actions I tried.
So, it would be great if you can capture the problem's call stack, by debugging one VS instance under another. Hopefully, this will shed some light on this issue.
P.S. As I see from your video, you're using ReSharper along with CodeRush. It is possible that there is a conflict between these two tools. Can you please temporary disable ReSharper and check whether the problem is reproduced in this instance?
Thanks,
Vito
Hi Vitto,
>Can you please temporary disable ReSharper and check whether the problem is reproduced in this instance?
In all those demos Resharper was disabled and restarted. I've generally been checking this with all bugs that I post as I know its the first thing you guys will ask and point to. To prove that is was not Rehsharper I uninstalled completelly and after about 30 tries to repro was about to write a response that mabye it IS Resharper. Just as I sat down to write this I gave it 2 more shots and it died. So unless there is some Reshaper ghost doing this it seems to be a CR/R thing.
On a side note. The one that killed it this time i typed pretty quick.
Anyways I'll try and get a stack trace when I get a chance as this is the bug that is bugging me most.
Thanks
Bart
Hi Bart,
Thank you for the response.
We do understand that this problem is really annoying, but we need to see it in action to be able to fix it, or at least examine its call stack. So, if you can capture it, that would be great.
Thanks,
Vito
Hi,
Attached is the strack trace + plus other debug outputs of the exception that causes the crash.
devexpress-message2.jpg shows the exception popup…
NOTE : Resharper(Jetbrains) was installed but disabled. Other plugins were enabled.
NOTE : devexpress-message1.jpg occurs once the debugger connects and is probably not related but included just in case.
Good luck guys. :)
Hi Bart,
Thank you for the response, and for the call stack you provided.
However, it looks as if you didn't activate the option, and so, we can't check which CodeRush methods lead to the issue. Can you please enable this option (please right-click the "Call Stack" tool window and make the "Show External Code" option active), and re-post the call stack?
I apologize for not drawing your attention to this option previously.
Thanks,
Vito
I was thinking that is was a bit scarce. Sorry, I actually knew about the setting but didn't think to turn it on.
Attached.
Hi Bart,
Thank you for the updated call stack. We'll examine it, and will get back to you as soon as we have any results, or need any extra information on the problem. Thank you for your patience.
Thanks,
Vito
FYI.
After another time VS died I thought it may be worth while setting VS it a single CPU affinity.
Unfortunatly this it does not seem to have made a differnence. Same symptoms are present.
Hi Bart,
I have good news for you. Our developers have reproduced this problem locally, and they are currently working on it. We'll do our best to find a solution as soon as we can. Please give us additional time.
Thanks,
Vito