| T O P I C R E V I E W |
| SergeyD |
Posted - Mar 22 2009 : 07:42:27 AM
Dear colleagues,
I have a problem with Visual Studio 2008 SP1 crashes during work with WPF projects.
Usually crash occurs when I trying to reopen the XAML file from Solution Explorer. Error message contains something like G?CanG??t read protected memoryG? and event log contains following message:
Faulting application devenv.exe, version 9.0.30729.1, stamp 488f2b50, faulting module va_x.dll, version 10.5.1715.0, stamp 497d1714, debug? 0, fault address 0x00317916.
My environment is: Windows Server 2003 R2 x64 SP2, Visual Studio 2008 Team Suite SP1, VAssist 10.5.1715.
Is any fix present for such problem?
WBR,
Sergey |
| 6 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Mar 25 2009 : 09:50:54 AM
I am glad you have found a solution  |
| SergeyD |
Posted - Mar 25 2009 : 08:46:55 AM
I'm really sorry for "false alarm" :(
It seems to me I found main reason of crashes. It is Visual Studio 2008 PowerCommands.
It looks like after installation of some .NET framework update this pack became to crash Studio.
I've removed it from my desktop and no any problem with WPF editor occur (at least till this moment). |
| feline |
Posted - Mar 23 2009 : 11:44:03 AM
Would it be possible to get a copy of a solution that is crashing for you? It would only be used for testing this problem, and would be kept private.
I understand this is often not possible, but it is worth asking.
Next time you get a crash can you please attach a new instance of the IDE and save out a mini dump file, then send us the file. Hopefully it will offer some clues.
Please submit the files via the form:
http://www.wholetomato.com/support/contact.asp
including this thread ID or URL in the description, so we can match it up. |
| SergeyD |
Posted - Mar 22 2009 : 11:27:57 AM
One more addition...
I have no "VS busy" problem. Crash effect is following: it is imposable to open xaml file for edit after crash.
One more buggy effect (in case .xaml is not in exclusion list) is a problem with redrawing of the XAML editor window. |
| SergeyD |
Posted - Mar 22 2009 : 11:23:49 AM
quote:
Originally posted by accord
Several people are reporting hangs during WPF development in vs2008 once SP1 has been installed:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=362619
A couple of workarounds (that don't solve everyone's problems) are posted here:
https://connect.microsoft.com/VisualStudio/feedback/Workaround.aspx?FeedbackID=362619
Do any of the workarounds apply to your situation?
No, I have absolutely different problem.
quote:
Can you please try to disable Visual Assist by
VAssistX -> Enable/Disable Visual Assist X
to see if the crashes are caused by VAX or not?
I did not disable VA at a whole, but I added .xaml into the exclusion list. After that no more crashes occur. However, I've got strange side-effect: automatic acronyms expansion is not working even in pure cs files :(. |
| accord |
Posted - Mar 22 2009 : 11:14:49 AM
Several people are reporting hangs during WPF development in vs2008 once SP1 has been installed:
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=362619
A couple of workarounds (that don't solve everyone's problems) are posted here:
https://connect.microsoft.com/VisualStudio/feedback/Workaround.aspx?FeedbackID=362619
Do any of the workarounds apply to your situation?
Can you please try to disable Visual Assist by
VAssistX -> Enable/Disable Visual Assist X
to see if the crashes are caused by VAX or not? |
