Hi, thanks for posting!

Could you submit a bug report straight after you've had this happen to you, detailing the number of seconds NCrunch was reported as stalling the IDE for?

VS displays these messages when its internal system detects the IDE is unresponsive. It then examines the stack trace for the hanging thread, and looks for any entry in the stack that is related to another product. If it finds one, the product is immediately blamed through the yellow banner. Naturally this has huge potential for misplaced blame (and plugin developer frustations), so please do take these warnings with a grain of salt.

We also track every activity in NCrunch internally and store this in our log, so if we're responsible, I'm hopeful the bug report will identify it ... however, with the product deactivated, our level of IDE integration is very close to zero, so there's a high likelihood that there's nothing we can do in NCrunch itself to resolve this.

Thanks for sending through the report. It was very short and quite conclusive with minimal activity and no issues or bottlenecks reported. As far as I can establish right now, this one doesn't look like us.



It is entirely possible that the hangup is the result of complex interactions inside VS that may or may not involve NCrunch. If it's happening for you consistently enough, I'd suggest trying to get a debugger on it and break into the debug session when it hangs. This will give you a chance to extract the stack trace at the point of hanging and hopefully identify the source of the issue. This would involve having one instance of VS debug another one. Note that the debugger greatly degrades performance on a debugged VS instance.



I have a lot of respect for many of the people that work on VS. Given the age of the project and everything it's been through, it must be a true nightmare to keep things running much less push through new features. There are many things that I'm unhappy with in the newer versions of VS, but I have to admit it's quite a remarkable feat that it works as well as it does in most cases. I really do wish they would have thought to report the stack traces they capture when playing these blame games though. As a package developer, it's rather hard to find a constructive solution when your only symptom is a yellow bar blaming your product for something you can't pin down or explain.

Launched VS again with NCrunch Enabled.

Got the 12 second hang with yellow bar warning, have sent bug report.

My previous comment about there being no hang with NCrunch disabled was a red herring and jusy co-incidence.