VS 2005 crashes on close

Hi all,

When I close VS 2005 (Team Edition, SP1) it crashes sometimes.
I suspect that it is related to ReSharper (3.0.2) because when I disable
it in VS plug-in menu, it stops crashing ...

Has anyone this problem too ? What should I do to provide more info ?

Thanks,

Martin

18 comments
Comment actions Permalink

Hello krumpo,

does the problem happen only with a specific solution?


Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


Hi all,

When I close VS 2005 (Team Edition, SP1) it crashes sometimes.
I suspect that it is related to ReSharper (3.0.2) because when I
disable
it in VS plug-in menu, it stops crashing ...
Has anyone this problem too ? What should I do to provide more info
?

Thanks,

Martin



0
Comment actions Permalink

Hi Dmitry,

does the problem happen only with a specific solution?


I'm not sure because I open many solutions during day but I'll try
to keep an eye on this and report back. Btw, my colleague has
(most likely) the same problem, so it is not specific to my machine.

Thanks,

Martin

0
Comment actions Permalink

Hello krumpo,

is it true that crash in your case means that VS displays its Error dialog?
Thanks.


Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


Hi Dmitry,

>> does the problem happen only with a specific solution?
>>

I'm not sure because I open many solutions during day but I'll try
to keep an eye on this and report back. Btw, my colleague has
(most likely) the same problem, so it is not specific to my machine.
Thanks,

Martin



0
Comment actions Permalink

It happens to me too. I'll notice the VS IDE becoming unresponsive and that devenv,exe is at high CPU (~50%). I'll close the solution and then I get the VS error dialog that VS has stopped responding. I get a choice to Debug or Close Program. I have not stepped into the debugger recently but as I recall I did not see anything incriminating.

Here's what the event log says:
Faulting application devenv.exe, version 8.0.50727.867, time stamp 0x45d2c842, faulting module unknown, version 0.0.0.0, time stamp 0x00000000, exception code 0xc0000005, fault offset 0x05b0cde0, process id 0x1348, application start time 0x01c7f559ad502fb1.

Which basically says that devenv.exe threw an error someplace unknown.

0
Comment actions Permalink

I've been seeing this over the past few days as well. Yesterday I had three
instances of Visual Studio 2005 open with three different projects. I closed
each instance of Visual Studio 2005 one at a time and the last instance
crashed. I haven't been able to nail it down to any one particular project
or even any particular type of project. Sometimes it crashes on a solution,
sometimes it doesn't. These are some of the entries in the event log:

Faulting application devenv.exe, version 8.0.50727.867, time stamp
0x45d2c842, faulting module unknown, version 0.0.0.0, time stamp 0x00000000,
exception code 0xc0000005, fault offset 0x026a8e4c, process id 0x1c28,
application start time 0x01c7f512fdbf7d30.

Faulting application devenv.exe, version 8.0.50727.867, time stamp
0x45d2c842, faulting module unknown, version 0.0.0.0, time stamp 0x00000000,
exception code 0xc0000005, fault offset 0x0791a468, process id 0xb04,
application start time 0x01c7f49a25385c20.

"Dmitry Shaporenkov" <dsha@jetbrains.com> wrote in message
news:c8a8a0be24078c9c377d12b8077@news.intellij.net...

Hello krumpo,

>

is it true that crash in your case means that VS displays its Error
dialog? Thanks.

>
>

Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>
>
>
>> Hi Dmitry,
>>
>>> does the problem happen only with a specific solution?
>>>
>> I'm not sure because I open many solutions during day but I'll try
>> to keep an eye on this and report back. Btw, my colleague has
>> (most likely) the same problem, so it is not specific to my machine.
>> Thanks,
>>
>> Martin
>>
>


0
Comment actions Permalink

Hi Dmitry,

is it true that crash in your case means that VS
displays its Error dialog?


Yep, that's true. Like this one :)

AppName: devenv.exe AppVer: 8.0.50727.762 AppStamp:45716759
ModName: unknown ModVer: 0.0.0.0 ModStamp:00000000
fDebug: 0 Offset: 04c6c0fc

Since I started to watch this it has occurred only twice and both
times with same smallish solution that mixes C# and C++ projects
(but this could be premature and misleading 'conclusion').

Regards,

Martin

0
Comment actions Permalink

I also encounter the same issue,

AppName: devenv.exe AppVer: 8.0.50727.762 AppStamp:45716759
ModName: unknown ModVer: 0.0.0.0 ModStamp:00000000
fDebug: 0 Offset: 0468c0ec

and I would also get

.NET Runtime version 2.0.50727.832 - Fatal Execution Engine Error (7A2B8F82) (0)

I have ReSharper 3.0.2 installed, and I think it is causing this issue, but occur very randomly. Usually when it happens when first load my solution, or after working with VS for awhile. When my mouse right click doesn't respond, and no key seems to work. VS will crash.

I have no solution, the only way that seems to fix it is to uninstall Resharper. I tried some of the EAP and it still have the same issue.

0
Comment actions Permalink

Hello Dicky,

so do I understand correctly that in your case the crash occurs randomly
when you're working, and not when
you're closing VS?


Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


I also encounter the same issue,

AppName: devenv.exe AppVer: 8.0.50727.762 AppStamp:45716759
ModName: unknown ModVer: 0.0.0.0 ModStamp:00000000
fDebug: 0 Offset: 0468c0ec
and I would also get

NET Runtime version 2.0.50727.832 - Fatal Execution Engine Error
(7A2B8F82) (0)

I have ReSharper 3.0.2 installed, and I think it is causing this
issue, but occur very randomly. Usually when it happens when first
load my solution, or after working with VS for awhile. When my mouse
right click doesn't respond, and no key seems to work. VS will crash.

I have no solution, the only way that seems to fix it is to uninstall
Resharper. I tried some of the EAP and it still have the same issue.



0
Comment actions Permalink

I and at least 4 of my colleagues have been experiencing this issue as well. I am also running VSTS SP1 and ReSharper 3.0.2 (Full Edition build 3.0.517.8 on 2007-08-21T09:41:12). The problem did not occur with R# 2.5.

0
Comment actions Permalink

I too have been experiencing this issue. Any further information needed?

Cheers,

Stuart

krumpo wrote:

Hi all,

When I close VS 2005 (Team Edition, SP1) it crashes sometimes.
I suspect that it is related to ReSharper (3.0.2) because when I disable
it in VS plug-in menu, it stops crashing ...

Has anyone this problem too ? What should I do to provide more info ?

Thanks,

Martin

0
Comment actions Permalink

I too have been experiencing this issue. Any further information needed?

Cheers,

Stuart

krumpo wrote:

Hi all,

When I close VS 2005 (Team Edition, SP1) it crashes sometimes.
I suspect that it is related to ReSharper (3.0.2) because when I disable
it in VS plug-in menu, it stops crashing ...

Has anyone this problem too ? What should I do to provide more info ?

Thanks,

Martin

0
Comment actions Permalink

Hello,

I too have been experiencing this issue. Any further information
needed?


It could help to see the stack traces of the crash. You can get them by attaching
another VS to the first one before it's closed, in mixed mode (Native + .NET),
seeing it break debugging when the crash occurs, snapping the lists in the
Call Stack window for the location of the exception.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink

> ntdll.dll!7c90eb94()

user32.dll!7e4191be()
user32.dll!7e42e042()
DW20.EXE!3002a55b()
ntdll.dll!7c90e027()
ntdll.dll!7c91392e()
msvcr80.dll!78132bc6()
msvcr80.dll!78138b51()
msvcr80.dll!781323ff()
msvcr80.dll!78131731()
msvcr80.dll!78138c3d()
msvcr80.dll!78138c37()
msvcr80.dll!78132bd9()
msvcr80.dll!78138c37()
DW20.EXE!3006a2dd()
DW20.EXE!3006a346()
DW20.EXE!3006045d()
DW20.EXE!30060477()
DW20.EXE!3006a346()
DW20.EXE!3006a359()
DW20.EXE!30069df0()
kernel32.dll!7c816fd7()

0
Comment actions Permalink

Hello,

DW20.EXE!3002a55b()


I'm puzzled with Doctor Watson entries in the call stack. Seems like that's
a stack of the error message but not the crash itself …

Moreover, seems like there are no managed frames on the stack.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0
Comment actions Permalink

Serge,

I'm puzzled with Doctor Watson entries in the call stack. Seems like
that's a stack of the error message but not the crash itself …


Oops, it looks I wasn't thinking after hard day, it is really a stack
from Dr Watson dialog displaying error message about VS crash :(

Sorry, next time I'll try to do the right thing :)

Regards,

Martin

0
Comment actions Permalink

I get the same problem. At least now with VS2008 installed I can debug the crashing VS2005.
I'm running on Vista 64 bit.
The exception is "Unhandled exception at 0x77b975fc in devenv.exe: 0xC0000029: An invalid unwind target was encountered during an unwind operation."

Mini dump attached.



Attachment(s):
devenv.7z
0
Comment actions Permalink

VS 2005 used to crash every time I exited until I started using the "Collect Garbage" property option before exiting Visual Studio (Resharper/Options/General: System - Show managed memory in status bar. Right-click on the Resharper memory used status). Hasn't crashed since.

0
Comment actions Permalink

I have am having the same error with my Vista 64bit machine. Random times during the day Visual Studio 2005 will Not Respond. Once I close the application and try and re-open it will show the openning splash screan then hang.

The event view is no help and I believe everyone has already posted the events in the above threads. I started deleting the application data stored within my user profile to correct my problem. I fear this is only a temperary fix. (I am not using any plug-ins for VS2005)

deleted..
C:\Users\\AppData\Local\Microsoft\VisualStudio\8.0\ C:\Users\\AppData\Roaming\Microsoft\VisualStudio\8.0\]]>

I tried opening VS2005 after deleting each folder and only after deleting the contents of the roaming folder would VS2005 open.

0

Please sign in to leave a comment.