I have the same problem on my current client site with WPF / VS2008 / XP 32bit. About 5+ times a day I get an out of memory error when compiling. Only happens after editing in xaml text editor, it has never happened after editing c# code. I have to restart VS and clean the solution. If I don't do a clean the error almost always recurs.
I don't have any addins in VS on this machine (powerpack, resharper....), which is what some people blame. On Fri, Jul 23, 2010 at 10:58 AM, <[email protected]> wrote: > Actually compile time and time to run takes a while anyway, so there is > plenty of time to do other > activities. > > T. > > > On Fri, Jul 23rd, 2010 at 10:26 AM, Steven Nagy <[email protected]> > wrote: > >> Yes but everyone's Facebook status will have been updated during that >> outage period so its not a total loss... ;) >> >> -----Original Message----- >> From: [email protected] >> [mailto:[email protected]] On Behalf Of >> [email protected] >> Sent: Friday, 23 July 2010 10:21 AM >> To: [email protected] >> Subject: Out of memory exceptions in VS2010 with Silverlight 4 >> >> Hi all, >> >> It's Friday, so I thought I would let you know about one issue in our >> team. >> >> Basically, we are running 32-bit Windows XP. The machines have anywhere >> between 2 and 4GB RAM. Everyone in the team gets System Out Of Memory >> Exceptions. When that happens, you have wasted the compile time, and then >> you have to shut down VS2010, start it up, then open up the solution. The >> solution has a significant number of projects in it. Apparently this >> problem only happens in 32-bit windows. >> >> So for the whole restart process, we have assigned 10 minutes to this >> procedure. >> >> Next we have logged the total crash time for our team of 7 developers >> (some days people were away, but it ultimately doesn't matter). >> >> The times lost are as follows: >> 14th 240 mins >> 15th 100 mins >> 18th 120 mins >> 19th 60 mins >> 20th 200 mins >> 21st 100 mins >> 22nd 140 mins >> >> we have assigned an arbitrary value against the times of $100/hour. So the >> loss of productivity is >> 16 hours @ $100/hour = $1600. >> >> Hopefully soon these figures will become a significant enough figure to >> justify an upgrade! >> >> Regards, >> Tony >> >> _______________________________________________ >> ozsilverlight mailing list >> [email protected] >> http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight >> >> _______________________________________________ >> ozsilverlight mailing list >> [email protected] >> http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight >> >> >> > > > > _______________________________________________ > ozsilverlight mailing list > [email protected] > http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight > > _______________________________________________ ozsilverlight mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
