[Mongrel] Memory leak with the pre-release?

Zed Shaw zedshaw at zedshaw.com
Wed Aug 16 20:16:12 EDT 2006


On Wed, 2006-08-16 at 20:10 -0400, Carl Lerche wrote:
> On Aug 16, 2006, at 7:06 PM, Ezra Zygmuntowicz wrote:
> >
> > Hey Carl-
> >
> > 	I have been seeing memory leaks with the new version of rails out
> > right now as well as edge. I don't think its mongrel related. But to
> > be sure, can you test your app with webrick and see if you still get
> > the leak? My bet is you do still get it. I haven'tbeen able to
> > pinpoint it but it is very annoying. My app runs fine in production
> > biut in dev mode with mongrel or webrick it keeps eating memory until
> > it fails to allocate with a fatal error and kills the processes.
> >
> > 	Do let me know if anyone figures out why the hell dev mode is
> > leaking again. I though this was fixed a while ago but its happening
> > again. I think it may have something to do with the new reloading
> > code in dev mode but i haven't been able to pinpoint it.
> 
> I'm running it in production mode right now and I get the memory  
> leaks. I also haven't noticed a problem with memory leaks before I  
> started using the pre-release. Maybe it's related to rails 1.1.6? I  
> just don't know.

Just a quick thought, but why don't you put:

  GC.start

Into an after filter on your application controller (the base controller
you have for all your other ones).

Simply forcing the GC this way might fix it magically.


-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
http://www.railsmachine.com/ -- Need Mongrel support?



More information about the Mongrel-users mailing list