Re: Horrible VS 2005 crashes in generic library

Eugene,

Thanks for the fast reply. Answers inline...

1) Have you any other VS add-ons installed?


Just the TestDriven add-in, but this one shouldn't be affected by the
editor...


2) While debugging, do not run another VS, but CLR debugger instead.
And enable break on all exceptions just before you make the debugee VS crash


Also doesn't work - as soon as I type the method, I'm getting the "MS
Visual Studio has encountered a problem and needs to close" dialog
(usually) or VS just disappers suddenly (only once). When I try to start
debugging from this dialog, I've had different behaviours:

- an RS exception that was caught by the CLR debugger, but that one came
after the exception that caused VS to crash
- the opportunity to start a new VS 2005 for debugging. From there, I
landed in "alloc.c". It appears to be a Win32 exception when requiring a
block of memory from the heap.

Maybe it's my VS? - I'm lost here ;)

Cheers,
Philipp

5 comments
Comment actions Permalink

Another observation:

While typing the method name crashes VS every time, using the "this"
keyword and selecting the method in the Intellisense popup does work.

I'll try to reproduce this behaviour on another machine this afternoon
and post the results here...

0
Comment actions Permalink

Please run the CLR Debugger, attach it to the VS, and before you make the VS
crash, enable in CLR Debugger stop on all exceptions

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Philipp Sumi" <nospam@this.domain.doesnotexist.xxx> wrote in message
news:e1g1j0$36f$1@is.intellij.net...

Eugene,

>

Thanks for the fast reply. Answers inline...

>
>
>> 1) Have you any other VS add-ons installed?
>

Just the TestDriven add-in, but this one shouldn't be affected by the
editor...

>
>>
>> 2) While debugging, do not run another VS, but CLR debugger instead.
>> And enable break on all exceptions just before you make the debugee VS
>> crash
>

Also doesn't work - as soon as I type the method, I'm getting the "MS
Visual Studio has encountered a problem and needs to close" dialog
(usually) or VS just disappers suddenly (only once). When I try to start
debugging from this dialog, I've had different behaviours:

>

- an RS exception that was caught by the CLR debugger, but that one came
after the exception that caused VS to crash
- the opportunity to start a new VS 2005 for debugging. From there, I
landed in "alloc.c". It appears to be a Win32 exception when requiring a
block of memory from the heap.

>

Maybe it's my VS? - I'm lost here ;)

>

Cheers,
Philipp



0
Comment actions Permalink

Eugene Pasynkov (JetBrains) wrote:

Please run the CLR Debugger, attach it to the VS, and before you make the VS
crash, enable in CLR Debugger stop on all exceptions


That's what I did but the CLR Debugger didn't get anything but stopped
debugging once VS was gone. Unfortunately, I could reproduce this
behaviour on my notebook but not on a machine without RS.
Nevertheless, I'm not so sure anymore that it's RS related at all, could
be a coincidence...

However, I stripped down the solution and it appears the issue is
related to generics: A class library that contains just the following
class crashes as soon as "SomeMethod" ist typed within the Test method.
However, as soon as the generic type declaration "" is removed from the class declaration, VS doesn't crash anymore. Boy, I just love my IDE... using System; using System.Collections.Generic; namespace Evolve.Util.IO.LogRecorder { public class LogBuffer]]>
{

public void Test()
{
//type this method name to crash VS: SomeMethod


}



private void SomeMethod()
{
}
}
}


I'm out of test machines... Is this reproducable for you (project attached)?

Cheers,
Philipp

0
Comment actions Permalink

I can't reproduce the crash :(

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Philipp Sumi" <nospam@this.domain.doesnotexist.xxx> wrote in message
news:e1g6od$ca9$1@is.intellij.net...

Eugene Pasynkov (JetBrains) wrote:

>> Please run the CLR Debugger, attach it to the VS, and before you make the
>> VS
>> crash, enable in CLR Debugger stop on all exceptions
>>
>

That's what I did but the CLR Debugger didn't get anything but stopped
debugging once VS was gone. Unfortunately, I could reproduce this
behaviour on my notebook but not on a machine without RS.
Nevertheless, I'm not so sure anymore that it's RS related at all, could
be a coincidence...

>

However, I stripped down the solution and it appears the issue is
related to generics: A class library that contains just the following
class crashes as soon as "SomeMethod" ist typed within the Test method.
However, as soon as the generic type declaration "<T>" is removed from
the class declaration, VS doesn't crash anymore. Boy, I just love my
IDE...

>
>

using System;
using System.Collections.Generic;

>

namespace Evolve.Util.IO.LogRecorder
{
public class LogBuffer<T>
{

>

public void Test()
{
//type this method name to crash VS: SomeMethod

>
>

}

>
>
>

private void SomeMethod()
{
}
}
}

>
>

I'm out of test machines... Is this reproducable for you (project
attached)?

>

Cheers,
Philipp



0
Comment actions Permalink

Eugene Pasynkov (JetBrains) wrote:

I can't reproduce the crash :(



Good for you, bad for me ;)

I assume it's something else on my systems that causes the issue. Looks
like I'm in for a long night...

Cheers,
Philipp

0

Please sign in to leave a comment.