|
|
|
Re: #18390- 100% CPU when walking through 'Find Results'
I have to agree with Mattias on this one. I can repeat this any time I wish, in fact I have to avoid Find Usages entirely. I can not and will not move our company forward to the 2.0 release until this is resolved. Again, I'm offering my services in trying to help isolate and correct this issue. Please let me know if there is something I can do. Dave Sausville Re: #18390- 100% CPU when walking through 'Find Results'
I got the same problem with 224 (on my second Ctrl-Alt-Down). Now I know how to fix it: I start a second devenv.exe, attaches the debugger to the first process. After 1 s, the deadlock is solved and I detach. I use VS2003. Re: #18390- 100% CPU when walking through 'Find Results'
I'm running Build 246 on VS 2003. I select 'FindUsages' on an interface, I group by 'Types and Type Members' in the 'Find Results' pane and select a plus sign next to a class. This will make VS 2003 take 100% CPU. Debugging will make VS 2003 run again and the problem disappear. > jetbrains.resharper.util.dll!JetBrains.ReSharper.Util.Concurrency.NativeManualResetEvent.WaitOne(int timeout = <has no runtime value>) Line 73 C# Re: #18390- 100% CPU when walking through 'Find Results'
Here are the log files from three different lockups as a result of using the FindUsage dialog. Log files A-C are from build 245. Log files D-E is from build 247. The log files do not change once the lockup has occurred, i.e. the do not grow in size. In all cases, I am pretty sure that the node which was clicked on corresponded to a file which was not open. And when VisStudio is locked up, the file still doesn't show as open. In the case of log file D, I was trying to open the file Lava.DataSources.Options.MarketData.OptionsMarketDataDataLayerPlugin. There are no references to that file at the end of the log file. When I am successfully able to click on a node, an +OnAfterFirstDocumentLock corresponding to the file being opened appears immediately after the logged info for FindUsage. Re: #18390- 100% CPU when walking through 'Find Results'
Mattias - Are you on a multiprocessor box? Dmitry - I still haven't had a chance to do WinDbg for you guys. I'm trying to get my on project out the door right now. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Next time, please attach the debugger to the hung VS and post the stack traces of all threads with managed frame
P.S. We do use VS2005