#27066: Possible Memory leak while evaluating a QuerySet
-------------------------------------+-------------------------------------
Reporter: RamezIssac | Owner: nobody
Type: Uncategorized | Status: new
Component: Database layer | Version: 1.8
(models, ORM) |
Severity: Normal | Resolution:
Keywords: queryset evaluation | Triage Stage:
memory leak | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
I'm not intimately familiar with memory management in Python but unless
you can provide details as to why, I'm doubtful that Django is at fault
for this behavior. Maybe this post about [http://chase-
seibert.github.io/blog/2013/08/03/diagnosing-memory-leaks-python.html
Diagnosing Memory "Leaks" in Python] helps.
--
Ticket URL: <https://code.djangoproject.com/ticket/27066#comment:3>
Django <https://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 unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.94feb5130537d0b34e65b0ee631313eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
