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

Notification

Icon
Error
Possible Memory leak in nCrunch 1.35b?
Options
Previous Topic Next Topic
rikrak
#1 Posted : Tuesday, November 15, 2011 12:22:40 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 11/15/2011(UTC)
Posts: 2
Location: Leeds, UK
Hi,

I've been using nCrunch for a few weeks now, and I think it's fab!

I'm noticing that I'm experiencing a few instances of VS2010 crashing, and it would appear to be related to an ever increasing memory usage. The failure usually occurs around the point where VS reaches ~2Gb in private bytes.

Is anyone else seeing this behaviour?

This could be specific to my installation as I'm also running Resharper 6. I suspect this is either nCrunch or ReSharper related as no one else in my team is experiencing this behaviour, and I'm currently the only one with this addins enabled.

rikrak
Back to top
MrClyfar
#2 Posted : Tuesday, November 15, 2011 10:11:26 PM(UTC)
Rank: Member

Groups: Registered
Joined: 8/6/2011(UTC)
Posts: 17

Thanks: 1 times
Was thanked: 2 time(s) in 2 post(s)
Hi rikrak.

First thing I'd try is running VS without R# 6 (I know it will be painful :) and see what the memory usage is.

If there's no change, then it could be an issue with NCrunch, but that would need further analysis.

Also have you tried the latest Resharper 6.1 EAP? http://confluence.jetbra...rper+6.1+Nightly+Builds

Give it a go and see if the memory usage improves.

Cheers.
Jas.
Back to top
rikrak
#3 Posted : Wednesday, November 16, 2011 2:40:31 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 11/15/2011(UTC)
Posts: 2
Location: Leeds, UK
Hi,

I suspended R# 6 and restarted VS2010 this morning. So far VS hasn't crashed, which is great. There is still a gradual rise in the private bytes associated with the VS process, but it is nowhere near as fast as when R# is activated.

I'd say that R#6 has been responsible for the recent crashing behaviour I've experienced, although the gradual rise in private byres is still indicative of a memory leak of some sort, so there may well be another issue to be resolved. Whether that's in nCrunch remains to be seen :-)

rikrak
Back to top
Remco
#4 Posted : Wednesday, November 16, 2011 10:26:37 PM(UTC)
Rank: NCrunch Developer

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

Thanks: 929 times
Was thanked: 1256 time(s) in 1169 post(s)
Hi rikrak,

Thanks for posting. I'm not aware of any serious memory leaks in NCrunch or in R# (though not sure about the EAP releases), though both plug-ins can be quite heavy in the areas of memory usage. NCrunch is very careful about not using too much memory in the host VS process, though it can be quite hungry in its task runners depending upon the tests you're running. There is an article in the NCrunch wiki that describes some ways of minimising this (though you will pay a price in terms of performance). I hope this helps!


Cheers,

Remco
Back to top
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