[226] High CPU Usage When Doing Nothing

Hello,

VS2005 goes to full processor usage (1 CPU on dual core machine, so
seems to be one single greedy thread).

Here are the CLR debugger stacks, the first one seeming to be the thread
causing the CPU load.

          
>     System.dll!System.Net.Sockets.Socket.ReceiveFrom(byte[] buffer =
, int offset = 0, int size = 65536,
System.Net.Sockets.SocketFlags socketFlags, ref System.Net.EndPoint
remoteEP = {System.Net.IPEndPoint}) + 0x194 bytes     
     System.dll!System.Net.Sockets.UdpClient.Receive(ref
System.Net.IPEndPoint remoteEP = null) + 0x6f bytes     
     JetBrains.ReSharper.Shell.dll!
JetBrains.ReSharper.Shell.SocketManager.PortListenerThread.Run() Line
127 + 0xd bytes     C#
     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     


          
>     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() Line 72 +
0x10 bytes     C#
     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     


Cheers,

Christian

3 comments
Comment actions Permalink

I've noticed similar behaviour too (one of two cores maxing out). It seems
to only/mainly happen when the screensaver kicks in? I have to kill VS using
Task Manager every time. Has been happening since at least build 219.

Hello,

VS2005 goes to full processor usage (1 CPU on dual core machine, so
seems to be one single greedy thread).

Here are the CLR debugger stacks, the first one seeming to be the
thread causing the CPU load.


>> System.dll!System.Net.Sockets.Socket.ReceiveFrom(byte[] buffer =
>>

, int offset = 0, int size = 65536,
System.Net.Sockets.SocketFlags socketFlags, ref System.Net.EndPoint
remoteEP = {System.Net.IPEndPoint}) + 0x194 bytes
System.dll!System.Net.Sockets.UdpClient.Receive(ref
System.Net.IPEndPoint remoteEP = null) + 0x6f bytes
JetBrains.ReSharper.Shell.dll!
JetBrains.ReSharper.Shell.SocketManager.PortListenerThread.Run() Line
127 + 0xd bytes     C#
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


>> 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() Line 72 +
0x10 bytes     C#
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

Cheers,

Christian



0
Comment actions Permalink

In article <a6939bda985fe8c817e492b52536@news.jetbrains.com>,
chris_overseasNOSPAM@hotmail.com says...

I've noticed similar behaviour too (one of two cores maxing out). It seems
to only/mainly happen when the screensaver kicks in? I have to kill VS using
Task Manager every time. Has been happening since at least build 219.

I'm forever getting this problem, certainly since build 215. Sometimes
it does not happen for a couple of hours and then it'e every few
minutes.

I have not spotted a consistent pattren but editing the using clauses
often results in a lock up.

Hello,

VS2005 goes to full processor usage (1 CPU on dual core machine, so
seems to be one single greedy thread).

Here are the CLR debugger stacks, the first one seeming to be the
thread causing the CPU load.


>> System.dll!System.Net.Sockets.Socket.ReceiveFrom(byte[] buffer =
>>

, int offset = 0, int size = 65536,
System.Net.Sockets.SocketFlags socketFlags, ref System.Net.EndPoint
remoteEP = {System.Net.IPEndPoint}) + 0x194 bytes
System.dll!System.Net.Sockets.UdpClient.Receive(ref
System.Net.IPEndPoint remoteEP = null) + 0x6f bytes
JetBrains.ReSharper.Shell.dll!
JetBrains.ReSharper.Shell.SocketManager.PortListenerThread.Run() Line
127 + 0xd bytes     C#
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


>> 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() Line 72 +
0x10 bytes     C#
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

0
Comment actions Permalink

In article <a6939bda985fe8c817e492b52536@news.jetbrains.com>,
chris_overseasNOSPAM@hotmail.com says...

I've noticed similar behaviour too (one of two cores maxing out). It seems
to only/mainly happen when the screensaver kicks in? I have to kill VS using
Task Manager every time. Has been happening since at least build 219.

I'm forever getting this problem, certainly since build 215. Sometimes
it does not happen for a couple of hours and then it'e every few
minutes.

I have not spotted a consistent pattren but editing the using clauses
often results in a lock up.

Hello,

VS2005 goes to full processor usage (1 CPU on dual core machine, so
seems to be one single greedy thread).

Here are the CLR debugger stacks, the first one seeming to be the
thread causing the CPU load.


>> System.dll!System.Net.Sockets.Socket.ReceiveFrom(byte[] buffer =
>>

, int offset = 0, int size = 65536,
System.Net.Sockets.SocketFlags socketFlags, ref System.Net.EndPoint
remoteEP = {System.Net.IPEndPoint}) + 0x194 bytes
System.dll!System.Net.Sockets.UdpClient.Receive(ref
System.Net.IPEndPoint remoteEP = null) + 0x6f bytes
JetBrains.ReSharper.Shell.dll!
JetBrains.ReSharper.Shell.SocketManager.PortListenerThread.Run() Line
127 + 0xd bytes     C#
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


>> 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() Line 72 +
0x10 bytes     C#
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

0

Please sign in to leave a comment.