Build 1227 causes Visual Studio hangup

After installing Build 1227 Visual Studio hangs while parsing the source. The first 98% of the parsing process is quite fast but then Visual Studio doesn't respond anymore. I waited around ten minutes and then killed the Visual Studio process. In the process explorer the CPU load of Visual Studio was 50% all the time.

The project i'm working on is a VB solution which was migrated from VB6. The file on which the parsing hangs is a large module file with around 10.000 lines of code (7.500 lines of it commented out).

I disabled R#, deleted the commented code and rebuild the solution. After this i reactivated R# and then the parsing runs without problems. Then i restored the original version of the module to see if the compilation of the solution had an effect. After doing this R# hangs while parsing the module (even after a rebuild before activating R#). So it seems to me that the mass of commented code causes the problem.

By the way: i deleted R#'s cache files each time before activating R#.

Regards
Klaus

5 comments
Comment actions Permalink

Hello Klaus,

Thank you for your feedback. We found a few performance issues in large VB files and fixed them in build 1230. But we can't reproduce any deadlock or hangs. Could you please try to attach debugger during such 'hangs' and to get a stacktrace? Or may be to profile this scenario with dotTrace profiler or any other .NET profiler?

0
Comment actions Permalink

unfortunately not as i have removed the commented code meanwhile. What i can try to do is to include the backup of the original source file in my project. This file has around 20.000 lines of code (meanwhile i have refactored this module, thanks to R# :-)), into several classes). But i'm not sure if i can compile it. As i have a deadline in my project i can't do this before next weekend.

Regards
Klaus

0
Comment actions Permalink

after working a while with build 1230 it seems quite stable and performant for me. There are some minor performance leaks while editing source code but i think they are caused by the background compile process and not by R# because  i noted that the error list is updated in these cases.

Regards
Klaus

0
Comment actions Permalink

Very glad to hear it. =) We still know a few small performance issues with typing in large VB files but they aren't so critical, so we plan to fix them in next versions. Anyway, it will be great, if you would find time to play with that file with 20 000 lines of code. May be a deadlock was there. Thank you one more time for your feedback.

Regards,
Olga

0
Comment actions Permalink

Meanwhile i migrated the original VB6 code of my current project another time because there where massive changes. I can'r reproduce the hangup with the release build 1231 of R#. Analyzing is very fast even for the 20.000 line module.

Regards
Klaus

0

Please sign in to leave a comment.