I was under the impression that, at some point, there were a number of places where Webware was caching things with no expiration or purging. Well, I feel fairly sure of it, but a lot of them were well-bounded: e.g., URL mappings and the like. I don't know what the state is now, but there might be some of them, under certain conditions, that could cause unbounded memory expansion (otherwise known as a leak).
If Webware itself is leaking memory -- not the Python interpreter or a C module -- then dictionaries are the most common culprit, usually when used for caching (in my experience with GCed languages). On Tue, 2002-02-12 at 08:59, Geoffrey Talvola wrote: > On Tuesday February 12, 2002 09:35 am, Greg Brondo wrote: > > I'm using Webware 0.6 final in a production environment here at work. It's > > running a rather simple but high use app. Over the course of a week it > > consumed 4.5GB of ram (thank goodness this was a Solaris box). Anyway, > > what kind of tools or what is the method I should go about searching for a > > memory leak? I've been programming in python for a while but as with most > > python guys, my apps are not persistent (they run when they need to run). > > This is the most obvious question, but which version of Python are you using? > Versions prior to 2.0 didn't have cyclic garbage collection. > > - Geoff > > _______________________________________________ > Webware-discuss mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/webware-discuss > _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
