#10758: sys.exc_info() should not be stored on a local variable
------------------------------------------------+---------------------------
Reporter: piotr.findei...@azouk.com | Owner: nobody
Status: new | Milestone:
Component: HTTP handling | Version: SVN
Resolution: | Keywords:
Stage: Accepted | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------------------+---------------------------
Comment (by kevinh):
"Off the top of my head - if there's a delay in the gc collecting the
cycle and you get a few tracebacks it could spike the memory usage of the
process and if it's python 2.4 it could result in that memory not being
freed resulting in it looking like a memory leak?"
Yes we are seeing this in production, though with python 2.5. It only
occurs under heavy load (we get around 10 million page views/month), and
only if we push pages out that throw 500 errors. Though it is fairly
consistent.
"As for the memory-leak, I really would like to see some tests, that cause
it. AFAIK, the cycle will be garbage collected by Python sooner or later."
I would love to see some tests too. Though this is beyond me.
--
Ticket URL: <http://code.djangoproject.com/ticket/10758#comment:8>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to django-upda...@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
