My vstudio 2012 choked cpu for some minutes or so and was unresponsive (I was focusing on some web stuff and only noticed it when I toggled back to vstudio). The below stack trace shows the cpu consumption used.
Is this expected behavior?
Quote:
> System.dll!System.Net.Sockets.Socket.Receive(byte[] buffer, int offset, int size, System.Net.Sockets.SocketFlags socketFlags, out System.Net.Sockets.SocketError errorCode) + 0xbd bytes
System.dll!System.Net.Sockets.Socket.Receive(byte[] buffer, int offset, int size, System.Net.Sockets.SocketFlags socketFlags) + 0x1d bytes
System.dll!System.Net.Sockets.NetworkStream.Read(byte[] buffer, int offset, int size) + 0x83 bytes
nCrunch.Core.dll!nCrunch.Core.Grid.Connectivity.DecryptorStream.Read(byte[] buffer, int offset, int count) + 0x423 bytes
nCrunch.Core.dll!nCrunch.Core.Grid.Connectivity.BidirectionalStream.Read(byte[] buffer, int offset, int count) + 0x28 bytes
nCrunch.Core.dll!#=qlV9H37gAKJQt6nX32$2ZFhXN_5XywDtXl4ovYfq$PgDFz0GQhPucyrYnvEGhXJa42SBIqICLxI1aIwYBbFXhfg==.Read(byte[] #=qVJGyH8HuhnhyZetms_Cv_A==, int #=qI3Es5zlEy_LnzD8HyYmPSg==, int #=q3jy1T54ovl$cKOaAmVHlTg==) + 0x155 bytes
nCrunch.Core.dll!nCrunch.Core.Grid.Connectivity.Zlib.DeflateStream.Read(byte[] buffer, int offset, int count) + 0x39 bytes
nCrunch.Core.dll!nCrunch.Core.Grid.Connectivity.BidirectionalStream.Read(byte[] buffer, int offset, int count) + 0x28 bytes
mscorlib.dll!System.IO.Stream.BeginReadInternal.AnonymousMethod__a(object param0) + 0x3c bytes
mscorlib.dll!System.Threading.Tasks.Task<int>.InnerInvoke() + 0x49 bytes
mscorlib.dll!System.Threading.Tasks.Task.Execute() + 0x2e bytes
mscorlib.dll!System.Threading.Tasks.Task.ExecutionContextCallback(object obj) + 0x15 bytes
mscorlib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx) + 0xa7 bytes
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx) + 0x16 bytes
mscorlib.dll!System.Threading.Tasks.Task.ExecuteWithThreadLocal(ref System.Threading.Tasks.Task currentTaskSlot) + 0xcb bytes
mscorlib.dll!System.Threading.Tasks.Task.ExecuteEntry(bool bPreventDoubleExecution) + 0xb3 bytes
mscorlib.dll!System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() + 0x7 bytes
mscorlib.dll!System.Threading.ThreadPoolWorkQueue.Dispatch() + 0x149 bytes
mscorlib.dll!System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() + 0x5 bytes
Submitted a bug report since errors were displayed in output when devstudio became responsive again; "Ceasing to send messages because of an error (was the connection closed?): nCrunch.Core.Grid.Connectivity.Zlib.ZlibException: Something is fishy. [stream error]"
(I was attached to the process so maybe this error is due to internal timeout or similar while having processed paused in other debugger?)
