Hi, On Wed, 2006-04-05 at 14:35 -0400, Joshua Tauberer wrote: > Gavin Hamill wrote: > > Having upgraded mono, recompiled > > xsp+mod_mono and restarted apache, 5 hours later RAM use is at 300M > > and I fully expect it to climb higher. > > I'm having the exact same problem, though I've been able to deal with it > by periodically restarting mod-mono-server (typically two or three times > a day). > > As Paolo reminded me this morning, we need to isolate the problem and > submit a test case.
I strongly recommend using Heap Buddy for this. We've used it very successfully in identifying problems in Beagle. Whether it's doing large, unnecessary allocations (and fragmenting the heap) or doing allocations that are never collected by the GC (like adding objects to a static hash table), it can help. You can get the source from here: http://blog.trowbridge.org/index.php?p=49 I blogged a bit about using it to identify a big leak in Mono a few weeks ago: http://joeshaw.org/2006/03/17/386 Joe _______________________________________________ Mono-list maillist - Mono-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-list
