It will error out in about 6-8 hours. I run a forced build on a single application every 10 minutes.
There is nothing unusual about the build. It is a VS2008 solution. The dashboard is on the same server and only visualizes that server. There are only 3 people using cctray. Could it be growing large because of a large log file? Or large msbuild log? Could it be the fault of the source control integration dll? Thanks for taking a look! On Jul 23, 2:17 am, Ruben Willems <[email protected]> wrote: > Hi > > on my machine CCNet also eats up a lot of memory, but I never had this > problem (yet). > The build machines runs for months in a row without any problem. > > How long does it take to get this problem? > days, weeks, months? > > is there anything 'unusual' with your builds? > ° many exec calls > ° large xml files to be merged > ° is the dashboard on the same server > ° how many projects > ° does the dashboard visualise other build servers > ° are there many people using cctray > > this could help us in the direction where the problem is > > with kind regards > Ruben Willems > > > > On Wed, Jul 22, 2009 at 7:38 PM, jroberts <[email protected]> wrote: > > > When I run CCNet, it starts out using around 25MB of memory. After > > several hours of running builds, it grows to upwards of 400 - 600 MB > > of memory used. Eventually I recieve the following error: > > > System.AccessViolationException: Attempted to read or write protected > > memory. This is often an indication that other memory is corrupt. > > > Any advice or suggestions would be appreciated! > > > Thanks! > > jroberts
