Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
devenv.exe high CPU usage
Options
Previous Topic Next Topic
plillevold
#1 Posted : Friday, February 1, 2013 12:04:35 PM(UTC)
Rank: Member

Groups: Registered
Joined: 2/1/2013(UTC)
Posts: 11
Location: Norway

Thanks: 6 times
Was thanked: 1 time(s) in 1 post(s)
Hi!

After using NCrunch some time I now experience constant 80-100% CPU usage on the devenv.exe process.
This is regardless of NCrunch being enabled or disabled for the current project.

Anyone else experiencing this?

Since NCrunch is not a "true" VS add-in I'm not sure the "Disable NCrunch" operation actually disables it completely, like I'm able to with other add-ins in the Add-In Manager.
So is there anything else I can do to make sure NCrunch is not doing stuff in the background?

FYI: the only additions to NCrunch is TestDriven.Net and ReSharper, both latest versions.

- Peter
Back to top
 |  Edit by user
Remco
#2 Posted : Friday, February 1, 2013 11:09:56 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,964

Thanks: 929 times
Was thanked: 1255 time(s) in 1168 post(s)
Hi Peter,

Thanks for posting!

This is the first time this problem has been reported for any recent release of NCrunch. It's true that disabling NCrunch does not shut off the entire add-in (about 10% of it is still in operation). If you haven't already, try uninstalling NCrunch entirely to see if this makes any difference with the CPU consumption. If it does, let me know and I'll try talking you through a few things we can check.


Cheers,

Remco
Back to top
plillevold
#3 Posted : Saturday, February 16, 2013 9:28:40 PM(UTC)
Rank: Member

Groups: Registered
Joined: 2/1/2013(UTC)
Posts: 11
Location: Norway

Thanks: 6 times
Was thanked: 1 time(s) in 1 post(s)
Hi,
thanks for the quick reply, and sorry for the late followup :)

I followed your advice and uninstalled NCrunch, and I'm sorry to say that VS seems to behave nicely now.

- Peter
Back to top
Remco
#4 Posted : Saturday, February 16, 2013 10:46:32 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,964

Thanks: 929 times
Was thanked: 1255 time(s) in 1168 post(s)
Thanks Peter,

This does confirm that it's likely to be NCrunch causing the CPU usage. The next step is understanding why ...

I'm wondering if you'd be able to help with answering the following questions. This will help me understand a bit more about your setup:

- How CPUs or CPU cores does your machine have and what is the processor model?
- Does the high CPU usage coincide with high memory usage and/or heavy I/O?
- Do you have this problem on all solutions?
- If this problem only seems to affect a certain solution, how many projects are in this solution?
- How many editor windows do you have open (roughly) at one time?
- If you are operating with NCrunch as part of a team, do your colleagues experience this problem with NCrunch?


Thanks!

Remco
Back to top
1 user thanked Remco for this useful post.
plillevold on 2/19/2013(UTC)
plillevold
#5 Posted : Tuesday, February 19, 2013 12:19:40 PM(UTC)
Rank: Member

Groups: Registered
Joined: 2/1/2013(UTC)
Posts: 11
Location: Norway

Thanks: 6 times
Was thanked: 1 time(s) in 1 post(s)
Hm, after reinstalling NCrunch.Net I no longer see the excessive CPU usage. I consider the case closed :)

For the record, here's my answers to those questions

- How CPUs or CPU cores does your machine have and what is the processor model?
Intel Core2 Duo 2.8GHz with 8GB memory and a 256GB SSD drive.

- Does the high CPU usage coincide with high memory usage and/or heavy I/O?
My VS processes usually consumes 500-900 MB of memory. The CPU load occured even when VS was sitting idle when I was working in other applications

- Do you have this problem on all solutions?
Yes, the problem occured regardless of solution.

- If this problem only seems to affect a certain solution, how many projects are in this solution?
n/a

- How many editor windows do you have open (roughly) at one time?
0 - 15 maybe, it varies.

- If you are operating with NCrunch as part of a team, do your colleagues experience this problem with NCrunch?
Currently, I'm the only user on my team


Thanks!

- Peter
Back to top
Remco
#6 Posted : Tuesday, February 19, 2013 10:04:15 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,964

Thanks: 929 times
Was thanked: 1255 time(s) in 1168 post(s)
Thanks for the info Peter! The answers you've given above exclude certain areas of the tool that I would have suspected could cause this problem, so my theory is that it may have been caused by a clash between multiple plugins or a bug in VS that was cleared when the package cache was cleared. If it happens to you again, please do let me know and we'll try to narrow it down further.
Back to top
1 user thanked Remco for this useful post.
plillevold on 2/21/2013(UTC)
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.042 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download