Y'know, this bug report deals with running Django's test suite, which is really a worst-case scenario. The test suite loads hundreds -- even thousands -- of models into memory, and does many complicated and costly operations. It's a unit test suite, and that makes its performance characteristics relatively unrealistic.

So I wouldn't want to judge real-world performance based on the performance of the test suite.

Also, beta0 is old news at this point; I've got to imagine that the Jython folks squished all sorts of bugs between then and now. Have you given your app another try on the final?

I have not tested my app on the final version.

In my app, and in other reports of the leak, it was not the complicated stuff that caused the leak. See this report, for instance: http://markmail.org/message/wwovry6qwnezcrr2

My case was basically the same thing. I had a loop doing some processing and the memory usage just kept growing.

Hey, Jacob Kaplan-Moss, you don't have time to post replies on HN. Django 1.1 is two months late, and I still see 20 open tickets. And would a status update on the Django blog kill you? Also, while you're at it, I've been hearing a lot about the GIL on reddit and HN lately, can you fix that? Thanks.

FWIW it's actually 21 tickets at the moment. Of which 18 are either documentation (10 tickets) or updated translation files (8 tickets).