VS2008 crashes on exit

Hi, I have a new machine with Vista and VS2008 RTM. I installed Resharper (had to install via cmd prompt with admin priveledges) and whenever VS exits it crashes. I tried to disable the Resharper addin and this caused VS to crash as well. I have tried this twice from a HDD image created before VS and Resharper were installed. The version of Resharper is 3.1 RC3.

Thanks
SurfRat

12 comments
Comment actions Permalink

Hello Surf,

do I understand correctly that VS crashes even without ReSharper installed?
If so, this is probably a VS issue.


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


Hi, I have a new machine with Vista and VS2008 RTM. I installed
Resharper (had to install via cmd prompt with admin priveledges) and
whenever VS exits it crashes. I tried to disable the Resharper addin
and this caused VS to crash as well. I have tried this twice from a
HDD image created before VS and Resharper were installed. The version
of Resharper is 3.1 RC3.

Thanks SurfRat



0
Comment actions Permalink

If I uninstall R# VS is fine. I tested VS before installing R# and it was also OK. As soon as I install it I have the problem. I even tried the official release on your home page (older build)
which showed the same problem.

Thanks

SurfRat

0
Comment actions Permalink

Hello Surf,

so as far as I understand it, VS crashes even with ReSharper disabled. How
does it crash - i.e. does it show the error dialog?


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


If I uninstall R# VS is fine. I tested VS before installing R# and it
was also OK. As soon as I install it I have the problem. I even tried
the official release on your home page (older build) which showed the
same problem.

Thanks

SurfRat



0
Comment actions Permalink

I was not able to disable R# as it crashed while trying to disable it. The crash result is the standard "This program is not responding" followed by "Searching for a solution". There are no error messages. Can you suggest a way to get more info on the error?

My PC is a brand new install with all the Windows patches and very little else. I am using AVG antivirus.

Thanks

SurfRat.

0
Comment actions Permalink

Hello Surf,

I think that the best way to diagnose the problem is to attach a debugger
to the hung instance of VS (another instance of VS or the DbgCLR program
may serve as a debugger) in the managed mode
and capture stack traces of all managed threads.


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


I was not able to disable R# as it crashed while trying to disable it.
The crash result is the standard "This program is not responding"
followed by "Searching for a solution". There are no error messages.
Can you suggest a way to get more info on the error?

My PC is a brand new install with all the Windows patches and very
little else. I am using AVG antivirus.

Thanks

SurfRat.



0
Comment actions Permalink

Another recommendation would be to start devenv (VS2008's main executable)
with the /log argument. That'll log everything that occurs and you can parse
through that.

Finally, if that doesn't work out well, you can start it with /SafeMode which
will just load the default environment without plugins and such.

Good luck!

-dl

--
David R. Longnecker
http://blog.tiredstudent.com

Hello Surf,

I think that the best way to diagnose the problem is to attach a
debugger
to the hung instance of VS (another instance of VS or the DbgCLR
program
may serve as a debugger) in the managed mode
and capture stack traces of all managed threads.
Dmitry Shaporenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

>> I was not able to disable R# as it crashed while trying to disable
>> it. The crash result is the standard "This program is not
>> responding" followed by "Searching for a solution". There are no
>> error messages. Can you suggest a way to get more info on the error?
>>
>> My PC is a brand new install with all the Windows patches and very
>> little else. I am using AVG antivirus.
>>
>> Thanks
>>
>> SurfRat.
>>


0
Comment actions Permalink

Hello David,

unfortunately /Log option only records certain types of events like extension
and add-ins loading and packages inititialization. It would be very difficult
if not impossible to relate those events
to the crash point.

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


Another recommendation would be to start devenv (VS2008's main
executable) with the /log argument. That'll log everything that
occurs and you can parse through that.

Finally, if that doesn't work out well, you can start it with
/SafeMode which will just load the default environment without plugins
and such.

Good luck!

-dl

--
David R. Longnecker
http://blog.tiredstudent.com

>> Hello Surf,
>>
>> I think that the best way to diagnose the problem is to attach a
>> debugger
>> to the hung instance of VS (another instance of VS or the DbgCLR
>> program
>> may serve as a debugger) in the managed mode
>> and capture stack traces of all managed threads.
>> Dmitry Shaporenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
>>> I was not able to disable R# as it crashed while trying to disable
>>> it. The crash result is the standard "This program is not
>>> responding" followed by "Searching for a solution". There are no
>>> error messages. Can you suggest a way to get more info on the error?
>>>
>>> My PC is a brand new install with all the Windows patches and very
>>> little else. I am using AVG antivirus.
>>>
>>> Thanks
>>>
>>> SurfRat.
>>>


0
Comment actions Permalink

Hi,

I ran VS with the /safemode option and it ran OK. I then ran VS with the log option. The log is attached. I will try more indepth debugging options on the weekend.

Thanks

SurfRat.



Attachment(s):
log.txt
0
Comment actions Permalink

Hello Surf,

the only suspicious entry in the log is the one below:



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


Hi,

>

I ran VS with the /safemode option and it ran OK. I then ran VS with
the log option. The log is attached. I will try more indepth debugging
options on the weekend.

>

Thanks

>

SurfRat.

>

0
Comment actions Permalink

Hello Surf,

the only suspicious entry in the log is the one below:

10 2007/12/20 19:38:28.225 Error Microsoft Visual Studio Error checking App Path


80070005 - E_ACCESSDENIED ]]>

Could you please check if you're running VS under with administrative privileges
and, if no, does running as an administrator
make any difference? And I would still try to attach the debugger as I proposed
before.



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


Hi,

I ran VS with the /safemode option and it ran OK. I then ran VS with
the log option. The log is attached. I will try more indepth debugging
options on the weekend.

Thanks

SurfRat.



0
Comment actions Permalink

Hi,

I tried running VS as administrator but it made no difference. I then ran VS in safe mode and it exited fine with no crash. I then ran as normal but disabled all my startup items and as many services and processes that I could but I still got the crash when VS exited.

Can you please give me detailed instruction on how to attach another instance of VS to the original running VS as I tried this but could not get any meaningful results.

Thanks

SurfRat

0
Comment actions Permalink

I finally found the cause to my problem. The solution was to remove
the nVidia Network Access Manager which gets installed with the nForce 680I SLI Vista motherboard drivers. I subsequently found out that this has caused lots of problems in other areas for other users as well.

Thanks for all your help in trying to track this down

SurfRat.

Message was edited by:
Surf

0

Please sign in to leave a comment.