VS crash after debug

[Trapulo]

Very often my VS2005 pro crashes after a debug.
I run ASP.NET debug, and all works well. Then I stop it, and all it's also
ok. Then, when I try to edit some code, it crashes and I need to kill it,
restart, reload project, etc.

it seems that the problem is with vb compiler integration, but I'm not sure.

Is this a known problem? Is there some solution? I cannot spend all my time
to reload VS and projects!

 

[Guest]

Hi Trapulo,
I don't know if this will be of any help, but I used to have this problem
with VS 2003 and .Net 1.1

my solution in the end, was to rebuild the machine, re-install VS and then
create a Norton Ghost partition so that I'd never have to do it again
as I say maybe you thought of all this, but it helped in my case, as I never
got the problem again.

Regards

 

[Steven Cheng[MSFT]]

Thanks for Charles's input.

Hi Trapulo,

Is this the first time you encountered the error or did the IDE used to
work well and just broke after applied some certain changes? Based on my
research, there's no such known issue, so if it's the behavior ever since,
there may has something incorrect with the installation.

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Trapulo]

Thanks for Charles's input.

Hi Trapulo,

Is this the first time you encountered the error or did the IDE used to
work well and just broke after applied some certain changes? Based on my
research, there's no such known issue, so if it's the behavior ever since,
there may has something incorrect with the installation.

Hi,
Charles's solution is not very confortable

However, I had this problem since first projects with VS 2005. Recently the
problem has grow, I think as projects that I'm working on (some solutions
with some asp/dll related projects and a lot of code).

If this can help, I've this problem either with a project started with
Vs2005, than an other createn on VS2003 and now upgraded. I'm working on a
Windows Server 2003 english, with VS 2005 pro english.
I'm debugging using VS's ASP NET development integrated service.

thank you

 

[Steven Cheng[MSFT]]

Thanks for your response Trapulo,

Charles' suggestion is specific to VS 2003/.NET 1.1. Also, since you
mentioned that the problems start from the begining and you haven't applied
any changes on it, I think it is likely a installation problem. Have you
any other dev machines encountering the same problem with similiar
environment?

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Trapulo]

Thanks for your response Trapulo,

Charles' suggestion is specific to VS 2003/.NET 1.1. Also, since you
mentioned that the problems start from the begining and you haven't
applied
any changes on it, I think it is likely a installation problem. Have you
any other dev machines encountering the same problem with similiar
environment?

No, I've only this dev machine with VS 2005

 

[Steven Cheng[MSFT]]

Thanks for your response Trapulo,

That'll be a bit hard to isolate the problem. Anyway, you can try start
from the repair install, if still no lucky, we may have to consider
reinstalling it.

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

 

[Trapulo]

I noticed that this happens always when I try to edit some row on my DAL
layer. Can this help?

All layers are in same solutions, and asp.net project references them.

 

[Steven Cheng[MSFT]]

Thanks for the further followup Trapulo,

I think this can help make the reproduce process much clearer and
simplified , however, this still indicate that there is something incorrect
with the IDE's debugging component. So far we haven't any other definite
means to get the root cause from the appearance.

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

 

[Trapulo]

Can this say something?

"Unable to recover from the following error: System Error &Hc0000005&
(Visual Basic internal compiler error). Save your work and restart visual
studio."


Then I may kill it becasuse it continue to request if it can send a report
to MS. Either if I click ok or not, the request is showed an other time and
so on

 

[Steven Cheng[MSFT]]

Thanks for your further followup Trapulo,

Well, I think this error message is much more helpful. I've performed some
further check and did find some "Visual Basic internal compiler error"
related problems. So far I found some similiar issue which occurs in a
VB.NET application(developed in VS 2005) which reference another certain
assembly(class library), and since there is some code in that assembly
doesn't quite define following some certain naming convention that cause
the VB compiler broke. So is this similiar to your case? At least you're
referencing an addtional assembly(class library), yes? I think you can
first confirm that it is that particular referenced assembly make the your
main project's debugging crash, then, try isolating the code in that class
library to locate the exact code block...

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

 

[Trapulo]

Thanks for your further followup Trapulo,

Well, I think this error message is much more helpful. I've performed some
further check and did find some "Visual Basic internal compiler error"
related problems. So far I found some similiar issue which occurs in a
VB.NET application(developed in VS 2005) which reference another certain
assembly(class library), and since there is some code in that assembly
doesn't quite define following some certain naming convention that cause
the VB compiler broke. So is this similiar to your case?

I think this is very strange, because compiler compiles my application
without problem. The problem is only after (during) a debug session.

At least you're

referencing an addtional assembly(class library), yes?

Uhm, my DAL layer references MS DAAB 2.0

I think you can

first confirm that it is that particular referenced assembly make the your
main project's debugging crash, then, try isolating the code in that class
library to locate the exact code block...

How can I discover what assembly causes compiler's crash? There isn't any
stack report, log, or other useful information when the problem occurs.

I also noticed that when I may terminate VS2005, and then restart it, reopen
the project, and restart a debug, I may "clean" the solution before I can
"debug" it an other time. It takes a lot of time, recompiles all, start a
new instance of asp.net development server (either previuous is still on and
working, and I can continue to use it to debug), and then app starts without
problems).



Thanks

 

[Trapulo]

Exception Information
code: 0x8013141e
Flags: 0x00000000
Record: 0x000000000000000000
Address; 0x0000000077e55dea

 

[Steven Cheng[MSFT]]

Hi Trapulo,

Yes, of course your code can get compiled correctly since this is a runtime
issue and is caused by the combination of your custom code and the VS IDE's
debugger service. So your DAL layer is also a class library, is it possible
that you create another web application reference your DAL class library to
reproduce the crash behavior? So far we can not get which dll cause the
crash without performing some low level dump analysis. This is usually done
through the CSS product support team for urgent issue(app/server crash or
hang...). What we can do in current level is still try isolating the code
in our custom assembly to see what's the exact code period that cause the
crash.

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

 

[Trapulo]

I think I found it.

It was an old library referenced by a library that my BLL and DAL use. The
library is very simple, just a class with some methods that write to windows
event log.
I opened source project with VS2005 (it was compiled with VS2003),
recompiled it without any changes, recompiled the dll that references it,
and finally recompiled main application. Now it seems I can debug main
application without vbc and IDE crash, and it seems also that compiling
application is more fast.

Thank you

 

[Steven Cheng[MSFT]]

Cool. Glad to hear you've got it working.

Regards,

Steven Cheng
Microsoft Online Community Support


==================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

==================================================


This posting is provided "AS IS" with no warranties, and confers no rights.



Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)