Re: Help on Memory Leak

With respect to pinpointing the cause..

How you pinpoint (and the extent to which you can pinpoint) depends upon whether the leak exists. It might not be a leak overall.. if you don't have apache configured correctly it could just be a matter of using more virtual memory than you have available -- causing the system to thrash (and struggle).

If you are certain that the leak is specific to the rails processes then you'll need to figure out which action processing is causing it.

There may be some tools out there.. I don't know though. Start by monitoring system memory levels and then try to see if there's a system memory issue.

Re: Help on Memory Leak

A common reason is eventhandlers not getting detached. Check that you are not hooking up eventhandlers that stay around, thus keeping the garbage collector from collecting memory.Btw, calling GC.Collect(); is not sufficient. It should be followed by GC.WaitForPendingFinalizers(); to properly force a collect.I noticed that the GC in Silverlight is very lazy, it it won't collect until it starts hitting the roof. That means the it will sometimes look like you have a memory leak even though you don't (however adding the above statement after .Collect() will force the collection).