VS2005 hangs for no reason - callstack included

It's been a few times my VS2005 locks up tight for no reason. At first, I thought it only occurred during ASP.NET debugging, but apparently not as it hung while being idle in a standard C# solution. It seems like it hangs occasionally after attempting to update its cache.

Here's the call stack I could retrieve before everything froze:


> mscorlib.dll!System.Threading.Monitor.Wait(object obj, int millisecondsTimeout, bool exitContext) + 0x14 bytes
JetBrains.ReSharper.Psi.dll!JetBrains.ReSharper.Psi.Impl.Caches2.CacheUpdateThread.Run() + 0x90 bytes
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context(object state) + 0x3b bytes
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x81 bytes
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x40 bytes

3 comments
Comment actions Permalink

Hello Alexandre,

unfortunately, the stack trace you've posted is quite OK, and it's not the
reason of the hung.
Could you please next time it hangs capture stack traces of other threads
in the debugger (using the 'Threads' window)?


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

It's been a few times my VS2005 locks up tight for no reason. At
first, I thought it only occurred during ASP.NET debugging, but
apparently not as it hung while being idle in a standard C# solution.
It seems like it hangs occasionally after attempting to update its
cache.

Here's the call stack I could retrieve before everything froze:


>> mscorlib.dll!System.Threading.Monitor.Wait(object obj, int
>> millisecondsTimeout, bool exitContext) + 0x14 bytes
>>


JetBrains.ReSharper.Psi.dll!JetBrains.ReSharper.Psi.Impl.Caches2.Cache
UpdateThread.Run() + 0x90 bytes

mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context(object
state) + 0x3b bytes

mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.Ex
ecutionContext executionContext, System.Threading.ContextCallback
callback, object state) + 0x81 bytes
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x40
bytes



0
Comment actions Permalink

Maybe this is the same problem as registeered under #18178. I get the hang
(with 100% CPU) on reloading a solution with, among others, web sites. I did
attach stack traces of all threads.

Regards,
Erwin Derksen

"Dmitry Shaporenkov (JetBrains)" <dsha@jetbrains.com> schreef in bericht
news:c8a894d910c5d18c8067571ec5e50@news.intellij.net...

Hello Alexandre,

>

unfortunately, the stack trace you've posted is quite OK, and it's not the
reason of the hung. Could you please next time it hangs capture stack
traces of other threads in the debugger (using the 'Threads' window)?

>
>

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

>
>> It's been a few times my VS2005 locks up tight for no reason. At
>> first, I thought it only occurred during ASP.NET debugging, but
>> apparently not as it hung while being idle in a standard C# solution.
>> It seems like it hangs occasionally after attempting to update its
>> cache.
>>
>> Here's the call stack I could retrieve before everything froze:
>>
>>
>>
>>> mscorlib.dll!System.Threading.Monitor.Wait(object obj, int
>>> millisecondsTimeout, bool exitContext) + 0x14 bytes
>>>
>>
>> JetBrains.ReSharper.Psi.dll!JetBrains.ReSharper.Psi.Impl.Caches2.Cache
>> UpdateThread.Run() + 0x90 bytes
>>
>> mscorlib.dll!System.Threading.ThreadHelper.ThreadStart_Context(object
>> state) + 0x3b bytes
>>
>> mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.Ex
>> ecutionContext executionContext, System.Threading.ContextCallback
>> callback, object state) + 0x81 bytes
>> mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x40
>> bytes
>



0
Comment actions Permalink

Dmitry Shaporenkov (JetBrains) schrieb:

Hello Alexandre,

unfortunately, the stack trace you've posted is quite OK, and it's not
the reason of the hung. Could you please next time it hangs capture
stack traces of other threads in the debugger (using the 'Threads' window)?


Having the same, other than the stacktrace already posted there is:

oops

The second VS hung up when trying to copy the stack trace as others have
already mentioned. ;-(

It hung up when I cancelled the creation of a new class.

Using R# build 219, VS 2005

;-(
Alexander

0

Please sign in to leave a comment.