Analysis of Visual Studio 2017 solution order of magnitude slower

Hi Remco,

Thank you for trying.

I did a text search on the solution for "NCrunch.Framework" and didn't get any results.

I've changed the settings "Allow parallel test execution" and "Allow tests to run in parallel with themselves" to false and this hasn't stopped the engine from becoming unresponsive.

"Tests to execute on this machine" is set to "When True".

I tried to create a sample solution reproducing the problem by:
1. Creating a new solution
2. Adding existing project LibBase
3. Adding existing project TestFastLibBase

However, the unresponsiveness then did not occur!

I am wondering if there is something strange in my original solution file that could be causing ncrunch confusion? Should I try deleting the original solution file and creating a new one?

Kind regards,
Craig.

Hi Craig,

I may have found an issue with the "Allow tests to run in parallel with themselves" setting. Does changing this to TRUE improve things?

I think the trigger here is configuration related. Wiping your NCrunch configuration for the solution (in a reversible way) might be very interesting.

Hi Remco,

Changing the "Allow tests to run in parallel with themselves" setting back to true does not fix the problem.

How do I wipe the NCrunch configuration for the solution?

donners77 wrote:
How do I wipe the NCrunch configuration for the solution?

The best way to do this without losing the configuration (so you can still go back) is to make a copy of the entire solution, then remove all the NCrunch derived files. You can find a list of all the files here - http://www.ncrunch.net/documentation/considerations-and-constraints_using-ncrunch-with-source-control. The hard part will be all the project config files. You can probably just find these using Windows Explorer's search for files feature or a recursive wildcard in a terminal window.

Note that it's important to have the IDE closed when you do this, otherwise NCrunch may have in-memory copies of these files and they won't be reset.

Don't forget to also reset the global config file. You can just rename it if you want.

If resetting the configuration solves the hanging issue, then you'll be able to start switching your configuration slowly back over to what it was before (one setting at a time), and in doing so, find the setting responsible for the problem. Then I should hopefully be able to fix it :)

Hi Remco,

I deleted any file in the solution folder that Windows explorer found matching *crunch*

I'm afraid it didn't fix the problem.

Do you, by chance, have a performance profiler on your machine? If so, would it be possible to get a profiling run of the NCrunch engine process? I expect there will likely be a clear stack trace behind what is taking up all the CPU time.

Hi.
I downloaded and installed dotTrace.
I did 2 snapshots during the unresponsive period and I've uploaded them by your Contact Us page with the following subjects:
- ncrunch engine unresponsive - profile snapshot 1
- ncrunch engine unresponsive - profile snapshot 2 (zipped)

Awesome, thanks! Did the upload finish ok? I haven't had anything come through. I understand the snapshots can be quite large. Even just knowing the stack trace of the area of the hang should be a huge help to me.

BTW: I just wanted to add that I really appreciate how patient you've been with this problem. We will figure this out.

The upload percentage indicator seemed to get to 100% for both.
But after that it said "Sorry! The page you tried to access does not exist. Click here to return to the home page of NCrunch.NET."
The file sizes were 20,105 KB and 6,887 KB.

Do you have any other way to share these files with me? Or any way to copy/paste the most relevant pieces of information?

Could you email me from my forum registration email address and then I could reply with the zipped file as an attachment?

donners77 wrote:Could you email me from my forum registration email address and then I could reply with the zipped file as an attachment?

Done.

I've replied with files attached.

Thanks Craig. Would you be interested in trying the build below? I hope this will resolve the issue:

NCrunch_Console_3.15.0.1.msi
NCrunch_Console_3.15.0.1.zip
NCrunch_GridNodeServer_3.15.0.1.msi
NCrunch_GridNodeServer_3.15.0.1.zip
NCrunch_LicenseServer_3.15.0.1.zip
NCrunch_VS2008_3.15.0.1.msi
NCrunch_VS2010_3.15.0.1.msi
NCrunch_VS2010_3.15.0.1.zip
NCrunch_VS2012_3.15.0.1.msi
NCrunch_VS2012_3.15.0.1.zip
NCrunch_VS2013_3.15.0.1.msi
NCrunch_VS2013_3.15.0.1.zip
NCrunch_VS2015_3.15.0.1.msi
NCrunch_VS2015_3.15.0.1.zip
NCrunch_VS2017_3.15.0.1.msi
NCrunch_VS2017_3.15.0.1.zip


Note: I'm aware this build has the same revision number as the last build I published. It's not the same build. We're doing some work on our build system at the moment, and somehow v3.15.0.1 has ended up being released 3 times with different binaries ... I guess at least this isn't a full release..

Fantastic. It is fixed! Analysis time is back down to around 20 seconds.
Thank you.

Excellent! Thanks for all your help and patience on this one. We got there in the end :)