InteliSense crashes VS2008 - by pm-intelisea

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


1
0
Sign in
to vote
ID 782001 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 3/24/2013 5:30:19 PM
Access Restriction Public

Description

I have both VS2012 and VS2008 installed on my Win7 SP1 32 bit machine.  As soon as I installed VS2012, VS2008 would crash anytime I started entering text in the source editor (VB or C#).  If I key only one character in a new line and then wait for a few seconds, InteliSnese seems to get its wits about itself and does not crash VS2008.  However, if a start a new line and forget to wait after the first character, then boom.  This behavior does not happen when editing in VS2012 nor does it happen when editing in VS2008 when VS2012 is also running with an open project.   
Sign in to post a comment.
Posted by Ala [MSFT] on 4/4/2013 at 6:44 AM
Thanks for the update. We recommend re-installing VS2008 now that VS2012 is uninstalled. There are too many open variables that makes it difficult for us to pinpoint the problem with the crash in such a scenario.

If the problem resurfaces, please reactivate or create a new Connect bug with the relevant steps.

Thanks,
Language Experience Team
Posted by pm-intelisea on 4/2/2013 at 11:41 AM
Update - - - I have now uninstalled VS2012 in an attempt to become productive with VS2008 (that's the version I use for production coding). I was hoping to get back to where I was before this problem started. However, the crashing problem remains.
Posted by Microsoft on 4/2/2013 at 2:43 AM
Hi pm-intelisea, thanks for your response. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by pm-intelisea on 3/29/2013 at 8:22 PM
Crash dump sent per instructions.
Posted by Microsoft on 3/28/2013 at 5:25 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting a 32 bits dump file. We look forward to hearing from you with this information.
If the dump file is too large to attach, please upload it into the following workspace.
************************************************************
Please zip the file and use "FeedbackID-782001" as prefix of the file name.
************************************************************
You can use the following workspace to upload the file by IE: https://sftemea.one.microsoft.com/choosetransfer.aspx?key=4714c7a4-1646-49f2-8e2c-91f818cdd165
Password: g#8EJcuGOqrKZ8N
Thanks again for your efforts and we look forward to hearing from you.
Microsoft Visual Studio Connect Support Team
Posted by Helen [MSFT] on 3/24/2013 at 5:52 PM
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)