Didn't you see my reply? His problem wasn't memory leak at all. It was just a case of django (on debug mode) filling up list with debugging info, which could fill up when many sql queries being done in a single request/response cycle.
Jason Huggins wrote:
I don't know what is wrong in this particular scenario.. but all I have to say is.... Memory leaks should be taken very seriously and should be hunted down and exterminated with extreme prejudice.
