Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Enabling Ncrunch on any new project causes hang and crash
NeilMacMullen
#1 Posted : Friday, April 2, 2021 11:43:20 AM(UTC)
Rank: Member

Groups: Registered
Joined: 12/15/2016(UTC)
Posts: 29
Location: United Kingdom

Thanks: 16 times
Was thanked: 5 time(s) in 5 post(s)
I'm pretty sure this must be a local configuration issue. Somehow NCrunch has got itself into a state where clicking on the "Next" button in the "Parallel Test Execution" dialog (for "First Time Crunch") causes it to hang and then crash Visual Studio.

This occurs for _any_ project/solution but existing projects run fine.

If I copy the .ncrunchsolution and .ncrunchsolution.user files from another solution, or edit .ncrunchsolution to set SolutionConfigured to True, then Ncrunch can run.


The problem has persisted over several Ncrunch version upgrades.

It may also be relevant that it's impossible to exit the "First Time Crunch" flow once it's been started. Clicking on 'Cancel' or the exit button on the "New Solution To Crunch" dialog just results in the dialog closing and immediately reopening.

I've tried running as admin and also disabling extensions (Resharper, Ncrunch) but haven't yet found an obvious culprit.
Remco
#2 Posted : Friday, April 2, 2021 11:16:57 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,422

Thanks: 839 times
Was thanked: 1137 time(s) in 1062 post(s)
Hi, thanks for sharing this problem.

I'm willing to bet something has gone wrong in your global config file. Delete the contents of C:\Users\USER\AppData\Roaming\NCrunch while the IDE is closed. This should reset your global configuration and hopefully resolve the issue.
1 user thanked Remco for this useful post.
NeilMacMullen on 4/3/2021(UTC)
NeilMacMullen
#3 Posted : Saturday, April 3, 2021 11:13:19 AM(UTC)
Rank: Member

Groups: Registered
Joined: 12/15/2016(UTC)
Posts: 29
Location: United Kingdom

Thanks: 16 times
Was thanked: 5 time(s) in 5 post(s)
Thanks Remco - that was a good tip. After some digging I realised the issue was this line where somehow I'd managed to insert a point instead of a comma between the 2&3. I notice the current configuration dialog prevents the user from getting this wrong but perhaps it was left older from a change in an earlier version or perhaps (less likely) I edited the config file manually some time in the past.

<CPUCoresAssignedToVisualStudio>2.3,4,5,6,7</CPUCoresAssignedToVisualStudio>
Remco
#4 Posted : Saturday, April 3, 2021 11:45:35 AM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 6,422

Thanks: 839 times
Was thanked: 1137 time(s) in 1062 post(s)
Thanks letting me know what the cause was. We'll get a fix put in so it doesn't bother anyone else :)
1 user thanked Remco for this useful post.
NeilMacMullen on 4/6/2021(UTC)
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.196 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download