Building a release package should use a lot of memory, due to linking.
But I can't think of any reason why stopping debugging would cause a
spike in memory or for the IDE to get really slow.
It takes a few seconds to kill things if you are stopped at a breakpoint
and click the stop debugging bu
FWIW, I am Win7 x64 also.
On Sun, Dec 18, 2011 at 6:17 PM, Tossing, Chris [via Mono for Android] <
ml-node+s1047100n5084921...@n5.nabble.com> wrote:
> We have observed this strange memory behavior (rapid cycling up above 1GB
> of usage and then back down) on Windows 7, as well (we are using Win7
We have observed this strange memory behavior (rapid cycling up above 1GB of
usage and then back down) on Windows 7, as well (we are using Win7 64-bit, in
case it matters).
Another strange IDE behavior that we have seen is a need to deploy twice before
it finally goes through (I know this has b
I get this happening from time to time but I'd wager it's more of a VS2010
issue than anything. Why do I say that?
Because I see it when trying to debug some WCF services that I attach to on
a plain-jane VS2010 install (i.e. no M4A). The only relief I seem to get is
(in this order): restarting VS
It takes the IDE (VS2010) a good while to get back to speed after stopping my
app. The IDE UI is very sluggish, if I run task mgr I see memory rapidly
going up above 1GB then quickly down to 400MB then back up in a cycle, maybe
30 seconds later it'll stop and the IDE will be back to full responsive
