| Reporter |
John W Saunders III (johnwsaundersiii)
|
|---|---|
| Created | Feb 6, 2011 6:39:27 AM |
| Updated | Jan 16, 2012 9:09:48 PM |
| Resolved | Jan 16, 2012 3:56:58 PM |
| Priority | Normal |
| Type | Bug |
| Fix versions | 6.1 |
| State | Fixed |
| Assignee | Evgeny Pasynkov (pasynkov) |
| Subsystem | Code Cleanup |
| Affected versions | No Affected versions |
| Fixed in build | 6.5.1.2465 |
After solving the previous problem, I did a "Cleanup Code" on the solution (containing only the new ASP.NET Web Application). This has been using at least one of my 2 CPUs, and the "Memory (Private Working Set)" shown in Task Manager is up to 1.6GB.
I had done this before, and had to kill the devenv.exe process. I rebooted, started Visual Studio again, let it recover two files (including the solution file), and then issued the "Cleanup Code" command. No other commands were issued in this session, though I did reposition the (empty) inspections window.
I had done this before, and had to kill the devenv.exe process. I rebooted, started Visual Studio again, let it recover two files (including the solution file), and then issued the "Cleanup Code" command. No other commands were issued in this session, though I did reposition the (empty) inspections window.