I had this same problem using a shared system. In my case, I think it was actually caused by subversion (run through mod_python with SSL). In particular, I noticed a problem whenever I committed changes to large binary files.
Unfortunately I never managed to narrow down the problem. However I did solve it! My solution was to move to a new shared server (within the same provider). Since that time (about two months ago), it has not appeared once. Sorry I can't help more. The only other suggestion I can offer is to test mod_python on a dedicated system, if you can, with DEBUG = False, and perhaps you can narrow down the issue a little. -rob On Feb 11, 7:49 am, "Mason Simon" <[EMAIL PROTECTED]> wrote: > I'm developing a Django project on Webfaction, and I noticed my memory > leaking. To isolate the cause, I started a fresh project. The only > things I changed in this brand new django project were the DEBUG > setting, which I set to False, and the database settings, which I > configured for a sqlite3 file. I used ab (ApacheBench) multiple times > to hit my project with a lot of queries, and in between runs of ab I > checked the memory usage of my apache processes. Each time I checked, > the memory usage went up. > > I ran the same project using Django's built-in dev server, and no > memory was leaked, so I think that narrows things down to mod_python > (maybe the handler for it). > > Can anyone else duplicate my results? Does anyone have ideas as to > what could be responsible for this memory leak? > > thanks in advance > -Mason --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
