| Reporter |
Dave Cousineau (Sahuagin)
|
|---|---|
| Created | Oct 9, 2012 7:48:00 AM |
| Updated | Apr 23, 2018 6:44:29 PM |
| Resolved | Apr 23, 2018 6:44:29 PM |
| Subsystem | Refactorings |
| Assignee | Alisa Afonina (alisa.afonina) |
| Priority | Normal |
| State | Can't Reproduce |
| Type | Bug |
| Fix version | No Fix versions |
| Affected versions | 6.1, 6.1.1, 7.0, 7.0.1, 7.1 |
| Fixed In Version ReSharper | Undefined |
| VsVersion | VS10 (2010) |
The "Move Type To Another Namespace" works ok, except that each time I do it, an additional CPU will forever be at 100% usage. I would guess this means that the thread that performed the refactoring is stuck spinning on something.
At work I have 2 cores; performing the refactoring once, I get stuck at 50% CPU usage (since one CPU is now consumed). Performing the refactoring a second time, I get stuck at about 100% CPU usage.
At home I have 4 cores; performing the refactoring once, I get stuck at 25% CPU usage. For each additional time I use the refactoring, I get an additional 25% CPU usage.
If I continue to use the refactoring beyond this, the computer will become slower and slower with each use. Closing and reopening the solution is enough to free the CPU cycles. The CPU seems to remain consumed indefinitely unless the solution is closed, although I have not tested it beyond 10-30 mins at most.
I experienced this with Resharper 6.1, and now unfortunately also 7.0. (I may have had it with 6.0 as well, but I can't recall).
I haven't noticed this with other refactorings, but there are some that I rarely or never use, so I can't say whether this is the only refactoring with that problem.
I have experienced this on two different Windows XP Pro 32-bit computers, and one Windows 7 Pro 64-bit computer.
Everytime I have done this, it has been moving a class.
At work I have 2 cores; performing the refactoring once, I get stuck at 50% CPU usage (since one CPU is now consumed). Performing the refactoring a second time, I get stuck at about 100% CPU usage.
At home I have 4 cores; performing the refactoring once, I get stuck at 25% CPU usage. For each additional time I use the refactoring, I get an additional 25% CPU usage.
If I continue to use the refactoring beyond this, the computer will become slower and slower with each use. Closing and reopening the solution is enough to free the CPU cycles. The CPU seems to remain consumed indefinitely unless the solution is closed, although I have not tested it beyond 10-30 mins at most.
I experienced this with Resharper 6.1, and now unfortunately also 7.0. (I may have had it with 6.0 as well, but I can't recall).
I haven't noticed this with other refactorings, but there are some that I rarely or never use, so I can't say whether this is the only refactoring with that problem.
I have experienced this on two different Windows XP Pro 32-bit computers, and one Windows 7 Pro 64-bit computer.
Everytime I have done this, it has been moving a class.