Just confirming that this fixed the memory leak problem for us. Thanks again :)
On Friday, March 22, 2013 3:07:02 PM UTC+13, Craig de Stigter wrote: > > Karen Tracey saves the day! > > Thanks so much, seems likely that's it :) > > Craig de Stigter > > On Friday, March 22, 2013 2:25:04 PM UTC+13, Karen Tracey wrote: >> >> On Thu, Mar 21, 2013 at 9:00 PM, Craig de Stigter <crai...@gmail.com>wrote: >> >>> Hi everyone >>> >>> (cross-posted because this seems relevant to both django-users and >>> developers, and both might have experienced this problem) >>> >>> We've noticed a gradual increase in memory usage for our apache >>> processes since upgrading to django 1.5. >>> >>> Here is a graph <http://i.imgur.com/cBsUx52.png> showing memory usage >>> before and after we upgraded to django 1.5 on our web server. (the upgrade >>> occurs at 12:30 on the graph). >>> >>> I'm hoping someone else has noticed a similar thing and is able to >>> provide some insight. >>> >> >> https://code.djangoproject.com/ticket/19895#comment:6 >> >> notes a memory leak due to a fix that went into 1.5. >> >> The fix was reverted on the 1.5.x branch about two days ago, so one thing >> to try would be to run current 1.5.x branch level rather than released 1.5. >> >> Karen >> > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
