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

Notification

Icon
Error

VS 2013 crashes
gareththackeray
#1 Posted : Friday, February 7, 2014 4:14:41 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 2/11/2013(UTC)
Posts: 4
Location: United Kingdom

Thanks: 1 times
Was thanked: 1 time(s) in 1 post(s)
Hi,

I find VS 2013 crashes repeatedly while I have NCrunch enabled. I just upgraded to 2.4 and this has not helped.

Any ideas?

Thanks,

Gaz
yanglee
#2 Posted : Friday, February 7, 2014 10:16:27 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 6/25/2012(UTC)
Posts: 89
Location: China

Thanks: 23 times
Was thanked: 19 time(s) in 18 post(s)
Hello,

I probably never experienced this issue before (Have NCrunch installed on 2 machines and several virtual machines with VS 2013). I guess probably one of your VS extensions not compatible with NCrunch.

I'd advise you to disable other extensions then try again.
Remco
#3 Posted : Saturday, February 8, 2014 12:19:10 AM(UTC)
Rank: NCrunch Developer

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

Thanks: 931 times
Was thanked: 1257 time(s) in 1170 post(s)
Hi Gaz -

Thanks for sharing this issue. Can you describe the nature of the crash? Is it a typical windows exception dialog that then tears down the whole process?

NCrunch is fairly resilient in its handling of exceptions - it will catch them and report them in the Output window when they occur, rather than taking down the process. It's been a long time since I've seen NCrunch take down the VS process, although NCrunch does increase memory utilisation within the VS process, which can sometimes cause instability in other extensions.

It can often be difficult to diagnose issues such as this. With VS being a process shared by many tools usually from different vendors, it's often difficult to know which tool is actually responsible. The complexity involved means that sometimes installing one tool can make another become unstable.

I would recommend stripping down your Visual Studio by removing any other 3rd party extensions to see if this makes any difference. It may be worth reinstalling Visual Studio to be certain that you have a clean slate to run from.


Cheers,

Remco
gareththackeray
#4 Posted : Monday, February 10, 2014 2:21:21 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 2/11/2013(UTC)
Posts: 4
Location: United Kingdom

Thanks: 1 times
Was thanked: 1 time(s) in 1 post(s)
OK thanks Remco. It is indeed a standard Windows exception box (Visual Studio has stopped...)

I have wondered whether it's a memory thing - I shall try to keep an eye out.
1 user thanked gareththackeray for this useful post.
Remco on 2/10/2014(UTC)
gareththackeray
#5 Posted : Tuesday, February 11, 2014 2:22:32 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 2/11/2013(UTC)
Posts: 4
Location: United Kingdom

Thanks: 1 times
Was thanked: 1 time(s) in 1 post(s)
Looks like it was memory - I allocated more to the VM where I run VS and it has been stable. Thanks.
Remco
#6 Posted : Tuesday, February 11, 2014 10:05:03 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 931 times
Was thanked: 1257 time(s) in 1170 post(s)
Great! Thanks for letting me know :)
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.037 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download