Build 911 pegging my CPU

I just installed build 911 of ReSharper on my box, and after I open up my
solution, my CPU is continuously pegged at about 25% or so. Has anyone else
seen this behavior? I don't have this problem with the release build.

Windows Server 2003
VS 2005

~Andy


5 comments
Comment actions Permalink

Hello Andy,

Could you please attach debugger to Visual Studio and see what threads are
doing what? Thanks.

Sincerely,
Ilya Ryzhenkov

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


AA> I just installed build 911 of ReSharper on my box, and after I open
AA> up my solution, my CPU is continuously pegged at about 25% or so.
AA> Has anyone else seen this behavior? I don't have this problem with
AA> the release build.
AA>
AA> Windows Server 2003
AA> VS 2005
AA> ~Andy
AA>


0
Comment actions Permalink

Hello Ilya,

I profiled Visual Studio using dotTrace and have attached the snapshot.
Let me know if it helps. Here is the scenario I took it through:

1. Started Visual Studio via dotTrace with profiling off at the beginning
2. Opened up my VS Solution
3. After the solution was completely open and all of the caches had been
updated and assemblies parsed (per the status messages in the lower right
corner), the CPU was still pegged at close to 100% even though nothing was
going on
4. I attached started profiling, and just let it sit for about 30 seconds,
the CPU continued to be pegged.
5. A got a snapshot that is now attached

Relevent metrics:
Windows Server 2003
Xeon 5160 dual core 3GHz
4 GB RAM
VS 2005
Large solution (about 20 projects including a very large web site project)
ReSharper 4.0 Build 915

Note that this problem appears to have started with build 910. Any build
910 or higher exhibits this behavior. Reverting to 909 and the problem goes
away.

Hope that helps,

~Andy


Hello Andy,

Could you please attach debugger to Visual Studio and see what threads
are doing what? Thanks.

Sincerely,
Ilya Ryzhenkov
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

AA>> I just installed build 911 of ReSharper on my box, and after I open
AA>> up my solution, my CPU is continuously pegged at about 25% or so.
AA>> Has anyone else seen this behavior? I don't have this problem with
AA>> the release build.
AA>>
AA>> Windows Server 2003
AA>> VS 2005
AA>> ~Andy


0
Comment actions Permalink

The attachment dlp file was too big. Is there an email address I can send
it to (its about 5 MB)

Hello Ilya,

I profiled Visual Studio using dotTrace and have attached the
snapshot. Let me know if it helps. Here is the scenario I took it
through:

1. Started Visual Studio via dotTrace with profiling off at the
beginning
2. Opened up my VS Solution
3. After the solution was completely open and all of the caches had
been
updated and assemblies parsed (per the status messages in the lower
right
corner), the CPU was still pegged at close to 100% even though nothing
was
going on
4. I attached started profiling, and just let it sit for about 30
seconds,
the CPU continued to be pegged.
5. A got a snapshot that is now attached
Relevent metrics:
Windows Server 2003
Xeon 5160 dual core 3GHz
4 GB RAM
VS 2005
Large solution (about 20 projects including a very large web site
project)
ReSharper 4.0 Build 915
Note that this problem appears to have started with build 910. Any
build 910 or higher exhibits this behavior. Reverting to 909 and the
problem goes away.

Hope that helps,

~Andy

>> Hello Andy,
>>
>> Could you please attach debugger to Visual Studio and see what
>> threads are doing what? Thanks.
>>
>> Sincerely,
>> Ilya Ryzhenkov
>> JetBrains, Inc
>> http://www.jetbrains.com
>> "Develop with pleasure!"
AA>>> I just installed build 911 of ReSharper on my box, and after I
AA>>> open up my solution, my CPU is continuously pegged at about 25% or
AA>>> so. Has anyone else seen this behavior? I don't have this problem
AA>>> with the release build.
AA>>>
AA>>> Windows Server 2003
AA>>> VS 2005
AA>>> ~Andy


0
Comment actions Permalink

Errr, I meant .dtc file, not dlp...

The attachment dlp file was too big. Is there an email address I can
send it to (its about 5 MB)

>> Hello Ilya,
>>
>> I profiled Visual Studio using dotTrace and have attached the
>> snapshot. Let me know if it helps. Here is the scenario I took it
>> through:
>>
>> 1. Started Visual Studio via dotTrace with profiling off at the
>> beginning
>> 2. Opened up my VS Solution
>> 3. After the solution was completely open and all of the caches had
>> been
>> updated and assemblies parsed (per the status messages in the lower
>> right
>> corner), the CPU was still pegged at close to 100% even though
>> nothing
>> was
>> going on
>> 4. I attached started profiling, and just let it sit for about 30
>> seconds,
>> the CPU continued to be pegged.
>> 5. A got a snapshot that is now attached
>> Relevent metrics:
>> Windows Server 2003
>> Xeon 5160 dual core 3GHz
>> 4 GB RAM
>> VS 2005
>> Large solution (about 20 projects including a very large web site
>> project)
>> ReSharper 4.0 Build 915
>> Note that this problem appears to have started with build 910. Any
>> build 910 or higher exhibits this behavior. Reverting to 909 and the
>> problem goes away.
>> Hope that helps,
>>
>> ~Andy
>>
>>> Hello Andy,
>>>
>>> Could you please attach debugger to Visual Studio and see what
>>> threads are doing what? Thanks.
>>>
>>> Sincerely,
>>> Ilya Ryzhenkov
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
AA>>>> I just installed build 911 of ReSharper on my box, and after I
AA>>>> open up my solution, my CPU is continuously pegged at about 25%
AA>>>> or so. Has anyone else seen this behavior? I don't have this
AA>>>> problem with the release build.
AA>>>>
AA>>>> Windows Server 2003
AA>>>> VS 2005
AA>>>> ~Andy


0
Comment actions Permalink

Hello Andy,

Thank you for your effort, I would be glad to receive the file at orangy@jetbrains.com,
thanks!

Sincerely,
Ilya Ryzhenkov

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


AA> The attachment dlp file was too big. Is there an email address I
AA> can send it to (its about 5 MB)
AA>
>> Hello Ilya,
>>
>> I profiled Visual Studio using dotTrace and have attached the
>> snapshot. Let me know if it helps. Here is the scenario I took it
>> through:
>>
>> 1. Started Visual Studio via dotTrace with profiling off at the
>> beginning
>> 2. Opened up my VS Solution
>> 3. After the solution was completely open and all of the caches had
>> been
>> updated and assemblies parsed (per the status messages in the lower
>> right
>> corner), the CPU was still pegged at close to 100% even though
>> nothing
>> was
>> going on
>> 4. I attached started profiling, and just let it sit for about 30
>> seconds,
>> the CPU continued to be pegged.
>> 5. A got a snapshot that is now attached
>> Relevent metrics:
>> Windows Server 2003
>> Xeon 5160 dual core 3GHz
>> 4 GB RAM
>> VS 2005
>> Large solution (about 20 projects including a very large web site
>> project)
>> ReSharper 4.0 Build 915
>> Note that this problem appears to have started with build 910. Any
>> build 910 or higher exhibits this behavior. Reverting to 909 and the
>> problem goes away.
>> Hope that helps,
>>
>> ~Andy
>>
>>> Hello Andy,
>>>
>>> Could you please attach debugger to Visual Studio and see what
>>> threads are doing what? Thanks.
>>>
>>> Sincerely,
>>> Ilya Ryzhenkov
>>> JetBrains, Inc
>>> http://www.jetbrains.com
>>> "Develop with pleasure!"
AA>>>> I just installed build 911 of ReSharper on my box, and after I
AA>>>> open up my solution, my CPU is continuously pegged at about 25%
AA>>>> or so. Has anyone else seen this behavior? I don't have this
AA>>>> problem with the release build.
AA>>>>
AA>>>> Windows Server 2003
AA>>>> VS 2005
AA>>>> ~Andy


0

Please sign in to leave a comment.