Beta 2.0 - Out of memory exception and apperent lockup VS 2003

I have been using the 2.0 beta version for almost two weeks now and I must say I like the new features I have used and I appreciate the bug fixes from 1.5.

However, I have had several instances each of two different problems that interrupt my productivity rather than enhance it.

1. Out of memory exception - twice when editing an out of memory exception appears and the only recourse is to shut down VS. I tend to leave VS up most of the time and switch between solutions often so this may contribute to it.

2. Apparent freeze - three times VS has apparently frozen although it actually is responding, just very slowly. When I look in task manager I see devenv.exe and rdpclip.exe maxing out the processor bandwidth. Twice I killed the devenv.exe process and restarted VS. The last time I killed rdpclip.exe and VS became responsive again. I haven't rebooted since and have re-started VS several times. The rdplcip.exe process has not reappeared in the task manager list. This is the cause of the slowdown but I don't know if it is Resharper related.

Any help, words of encouragement or condolences?

Don Brocha
Calypso Medical

8 comments
Comment actions Permalink

1) Please could you download the latest build from
http://www.jetbrains.net/confluence/display/ReSharper/Download
and check it for the "OutOfMemory" exception. We've made progress over
memory utilization, and your verification would be very helpful.

2) The next time VS hang, please could you run the CLR debugger, attach it
to the hung Studio, and post the stack traces of all threads which contains
managed frames

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Don Brocha" <dbrocha@calypsomedical.com> wrote in message
news:21912318.1146857582052.JavaMail.itn@is.intellij.net...
>I have been using the 2.0 beta version for almost two weeks now and I must
>say I like the new features I have used and I appreciate the bug fixes from
>1.5.
>

However, I have had several instances each of two different problems that
interrupt my productivity rather than enhance it.

>

1. Out of memory exception - twice when editing an out of memory exception
appears and the only recourse is to shut down VS. I tend to leave VS up
most of the time and switch between solutions often so this may contribute
to it.

>

2. Apparent freeze - three times VS has apparently frozen although it
actually is responding, just very slowly. When I look in task manager I
see devenv.exe and rdpclip.exe maxing out the processor bandwidth. Twice I
killed the devenv.exe process and restarted VS. The last time I killed
rdpclip.exe and VS became responsive again. I haven't rebooted since and
have re-started VS several times. The rdplcip.exe process has not
reappeared in the task manager list. This is the cause of the slowdown but
I don't know if it is Resharper related.

>

Any help, words of encouragement or condolences?

>

Don Brocha
Calypso Medical



0
Comment actions Permalink

Yes I will do both and let you know the results. If I don't find anything in another week of use I will let you know that as well.

Don

0
Comment actions Permalink

Hello Don,

Someone, a while back now, discovered that the 'hang' was something to do
with a progress indicator or some other R# UI thing somewhere (can't remember
who or exact details) - use ]]> to 'go-to-desktop' and it 'releases'
VS from it's hung state.

Obviously it would still be useful for the bug to be fixed - but it gets
you out of a stuck position if desperate!

Ronnie

I have been using the 2.0 beta version for almost two weeks now and I
must say I like the new features I have used and I appreciate the bug
fixes from 1.5.

However, I have had several instances each of two different problems
that interrupt my productivity rather than enhance it.

1. Out of memory exception - twice when editing an out of memory
exception appears and the only recourse is to shut down VS. I tend to
leave VS up most of the time and switch between solutions often so
this may contribute to it.

2. Apparent freeze - three times VS has apparently frozen although it
actually is responding, just very slowly. When I look in task manager
I see devenv.exe and rdpclip.exe maxing out the processor bandwidth.
Twice I killed the devenv.exe process and restarted VS. The last time
I killed rdpclip.exe and VS became responsive again. I haven't
rebooted since and have re-started VS several times. The rdplcip.exe
process has not reappeared in the task manager list. This is the cause
of the slowdown but I don't know if it is Resharper related.

Any help, words of encouragement or condolences?

Don Brocha
Calypso Medical



0
Comment actions Permalink

The attachment is a screen shot of VS when hung.

Not much info, hope it helps. I got the clipboard manager shot when I did a break all. I then played around some more and it unhung before I could get shots for all the threads. I will get them all nex time this occurs.

Don



Attachment(s):
CLR_Screenshot.doc
0
Comment actions Permalink

Unfortunately, this screenshot is useless. The main interest is on the main
UI thread, which is the first in the "treads" window list

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Don Brocha" <dbrocha@calypsomedical.com> wrote in message
news:6406556.1147210707126.JavaMail.itn@is.intellij.net...

The attachment is a screen shot of VS when hung.

>

Not much info, hope it helps. I got the clipboard manager shot when I did
a break all. I then played around some more and it unhung before I could
get shots for all the threads. I will get them all nex time this occurs.

>

Don



0
Comment actions Permalink

OK, I will try again. By the first thread in the threads list what do you mean? The top thread in the list is the one the call stack is for. Which one would be the main UI thread?

Don

0
Comment actions Permalink

In VS debugger/CLR debugger, in threads window, there is a list of threads.
The very top item if the list is the primary UI thread. Nearlly all locks
are caused by locking of that thread, and it's call stack is the most
interesting

--
Eugene Pasynkov
Developer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"
"Don Brocha" <dbrocha@calypsomedical.com> wrote in message
news:13346658.1147274864734.JavaMail.itn@is.intellij.net...

OK, I will try again. By the first thread in the threads list what do you
mean? The top thread in the list is the one the call stack is for. Which
one would be the main UI thread?

>

Don



0
Comment actions Permalink

Now when I get lock ups it is devenv.exe that is maxing out but rdpclip.exe doesn't seem to be active. When I start the DbgCLR, as soon as I attach to devenv.exe it un-hangs. One common ascpect betweent he two or three times I have seen it is that I do have the Find Usages window open.

I haven't seen the out of memory or the other lockup since I last wrote.

0

Please sign in to leave a comment.