Debugging in VS 2010 with 5.1.1 takes over 1 minute to go from Pending to Running

When I attempt to debug an NUnit (2.5.5.10112) test in Visual Studio 2010 Professsional, it sits there with a pending status on the Unit Test Sessions window.  After a minute or two, it will actually start running.

What's interesting is there is no problem 'Running' the tests and they start up just fine.  I make sure I build before hand to speed up the process, but that doesn't seem to help either.

Any thoughts?

Thanks!

9 comments
Comment actions Permalink

Hello Bryan,

Does this happen with any test (even if you create a new class library project
with an empty test in it)? Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

When I attempt to debug an NUnit (2.5.5.10112) test in Visual Studio
2010 Professsional, it sits there with a pending status on the Unit
Test Sessions window.  After a minute or two, it will actually start
running.

What's interesting is there is no problem 'Running' the tests and they
start up just fine.  I make sure I build before hand to speed up the
process, but that doesn't seem to help either.

Any thoughts?

Thanks!

---
Original message URL:
http://devnet.jetbrains.net/message/5275667#5275667



0
Comment actions Permalink

Good question.  It does not take forever.

1. Added new project as a class library
2. Referenced NUnit library
3. Created one test that simply outputs to the console
4. Runs just fine (Run mode and Debug mode).

So, not really sure what to do with that.  Does ReSharper load up NUnit addon's just like NUnit does when loading it through the GUI, now that NUnit is "native"?  When I load the assembly through the NUnit Gui, it takes roughly 20 seconds, whereas running debug mode through ReSharper in the IDE takes over a minute.

0
Comment actions Permalink

Hello Bryan,

Could you please follow the instructions at http://confluence.jetbrains.net/display/ReSharper/ReSharperPerformanceProfiling+Instructions
to capture a snapshot of the moment when ReSharper is in 'Pending' state
and upload it to ftp://ftp.intellij.net/.uploads? This would really help
us to find out why it takes so much time. Thank you!

Andrey Serebryansky
Senior Support Engineer
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

Good question.  It does not take forever.

1. Added new project as a class library
2. Referenced NUnit library
3. Created one test that simply outputs to the console
4. Runs just fine (Run mode and Debug mode).
So, not really sure what to do with that.  Does ReSharper load up
NUnit addon's just like NUnit does when loading it through the GUI,
now that NUnit is "native"?  When I load the assembly through the
NUnit Gui, it takes roughly 20 seconds, whereas running debug mode
through ReSharper in the IDE takes over a minute.

---
Original message URL:
http://devnet.jetbrains.net/message/5275819#5275819



0
Comment actions Permalink

Thanks for the advice.

I have followed your instructions and uploaded the file to the ftp site provided.  It was about 333 MB.  File name was : ReSharper-DebugLoadSlowness.dtp.

Let me know if you did not receive it.  Thanks!

0
Comment actions Permalink

Andrey,

I was just curious to know if any improvement or discover has been found with the file I uploaded a while back.  The slowness for us continues and by reading some posts on the forum, I don't seem to be the only one.  I do admit having some large automation suites that we manage.  However, when I used resharper in the past (4.x version), it was never this slow when loading up debug.

I am on Build 5.1.1753.4.  No custom plugins are installed.  I'm running on Visual Studio 10.0.30319.1.

Should I install the latest version of R#?

Thanks for your help.

0
Comment actions Permalink

Hi Bryan,

we're investigating this issue. Thanks for providing snapshot!

0
Comment actions Permalink

I had a strange experience like that myself. One day debugging was working fine, the next day when I came in, it was painfully slow to start debugging a test. I could see in the Output window that each assembly was taking a huge amount of time to load.

Anyway, I eventually tracked down the cause: In VS, I had [Tools -> Options -> Debugging -> Symbols -> "Microsoft Symbol Server"] ticked on. Unticked it, and everything went back to normal speed

I was speculating that VS was doing a version check (going to the MS symbols server) while loading each assembly, and there was a temporary problem with the communication. But, if you are consistently experiencing the issue, then my theory doesn't really hold :)

Anyway, hopefully this will be of some help to someone else

0
Comment actions Permalink

That's something good to note for the future.  Mine was unchecked, but I'll keep an eye on it.

Thanks.

0
Comment actions Permalink

You might also check the NTSYMBOL_PATH in the environment. I ran into the
same problem last week and I did not have the symbol server configured in
Tools | Options, but I did have NTSYMBOL_PATH in the environment for
windbg.

"Andrew Smith"  wrote in message
news:19081853.785391297257128455.JavaMail.devnet@domU-12-31-39-18-36-57.compute-1.internal...

I had a strange experience like that myself. One day debugging was working
fine, the next day when I came in, it was painfully slow to start debugging
a test. I could see in the Output window that each assembly was taking a
huge amount of time to load.

Anyway, I eventually tracked down the cause: In VS, I had [Tools ->
Options -> Debugging -> Symbols -> "Microsoft Symbol Server"] ticked on.
Unticked it, and everything went back to normal speed

I was speculating that VS was doing a version check (going to the MS symbols
server) while loading each assembly, and there was a temporary problem with
the communication. But, if you are consistently experiencing the issue, then
my theory doesn't really hold

Anyway, hopefully this will be of some help to someone else

---
Original message URL: http://devnet.jetbrains.net/message/5285932#5285932

0

Please sign in to leave a comment.