VS2003 crashes frequently

[Lee Gillie]

I've been running VS2000 for a while. It was not completely stable,
and would occassionally lock up in the debugger. It very rarely
crashed. I never lost any work with it though.

I'm piloting into VS2003 for our team of developers, and am finding
that although it never seems to lock up, it DOES crash frequently.
Usually 10 times or more per day. It can crash when you are not
interacting with it (something running in the background?) I have
lost work several times now.

My question is: Do we know if a service pack is due out any time soon
for VS2003 and/or Framework 1.1?

Best regards - Lee Gillie - Spokane, WA

 

[Jerry Ham]

Maybe something to do with your configuration or hardware (video driver,
etc.)? I have not had it crash or lock up even once yet. I've been running
it since it released to MSDN Universal on the web (at RTM).

Jerry

 

[CT]

I'm likely to go with Jerry on this one; have you experienced any problems
with the video driver or even had memory issues?

 

[anthonyb]

i had the same problem with vs.net and Sql Server Query Analyzer.
I found a solution from a post in another newsgroup,
my video driver had a switch "(nVidia DesktopManagement) that
when i turned it off all went fine and have never had any problems
since then.
Dont ask about the connection of the problme but that was it!

anthonyb

 

[Jim Delany]

You would be surprised to discover the number of people that don't realize
that the number you put in the size for the virtual space needs to be the
sum of all of the programs you run at one time not the largest of them. If
you debug some giant app with sql server and all of the rest going at one
time mail, ie .... you need a big number. If you don't put in a big number
the symptoms are as described and usually random.

--




Jim

 

[James Shen]

I am using WinForm. VS2003 lost designs frequently. You can reproduce
by:

1. create some components and make them in one dll
2. use the components to design another form
3. Change one of the components and make one mistake in it so that the
dll would not compile.
4. compile the whole project. Then the design is lost. Even you
correct the component, then the form design is gone.


James

 

[Lee Gillie]

More on this, which is PROBABLY partially VS.NET unrelated.

System event log contains an event ID 3034 messages, with Source:
MRxSmb, and the last DWORD value in the Data section is 80090322 at
about the same time of the problem with documentation.

I see help attempts to resolve URLs such as
ms-help://MS.VSCC.2003/MS.MSDNQTR.2003FEB.1033/dndotnet/html/dotnetper
ftips.htm
to find help content. I don't know how these work, or why this would
be affected by redirector, or even worse, why this would crash the
VS.NET IDE. I wonder what HELP is doing that might be affected by
DNS? Does it return to the mothership, at times, even though I
installed all documentation to my local hard disk?

Any ideas?

- Lee