Adam Kalsey wrote: > Has anyone else noticed that PyAIMt sometimes sucks a lot of memory? > > Usually, PyAIMt and PyMSNt consume around 12M, but periodically PyAIMt > will grow to hundreds of MB in size, often getting to around 550MB. The > server has 1G of RAM, and PyAIMt's growth causes ejabberd to shut down, > apparently due to a lack of memory. > > It generally takes around 24 hours of usage for this to happen. > Currently, I have a cron that restarts the transports and ejabberd every > 12 hours. Since I implemented this last week, I haven't seen the problem > re-occur, but it's a bit of an ugly hack that I'd rather not rely on. > > I'm running Twisted 2.5 with epoll on Debian Etch. A little bit of > searching has revealed that others describe a similar issue.
How many connections do you generally have? Does it happen repeatably, where if you leave it running for around 24 hours it will do this almost every time? One interesting thing is that ejabberd, and not pyAIMt is shut down. Is it a case of Linux killing the "wrong" program? I'd be interested to see who else has this problem, and I know of at least one place where the problem may be coming from. It's something we never bothered improving because almost nobody ran into it. ~Chris _______________________________________________ py-transports mailing list py-transports@blathersource.org http://lists.modevia.com/cgi-bin/mailman/listinfo/py-transports
