#13488: GeoDjango
---------------------------------------+------------------------------------
Reporter: mro...@arinc.com | Owner: jbronn
Status: assigned | Milestone: 1.2
Component: GIS | Version: 1.2-beta
Resolution: | Keywords: gis
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------+------------------------------------
Comment (by jbronn):
I can't reproduce. I need details on the platform you're using. What
version of Python/Django/GEOS/PostGIS? What OS are you running on
(instinct tells me RHEL)?
I don't think memory leakage is occurring. !GeoDjango instantiates up to
5 GEOS I/O objects per-thread. These references are cleaned up by the
`__del__` method on the I/O objects, however in your particular install of
Python the GC order has the I/O object destructor wrapper destroyed before
the Python object -- hence why it doesn't exist at the time of interpreter
exit. The GEOS I/O references aren't being cleaned upon exit of the
process, so even though the references aren't released the process memory
space should be reclaimed by the OS regardless because the process is
terminating.
In other words, it may look bad but it's relatively benign. But again, I
need more details so I can confirm what's going on and possibly tweak
variable names so it won't occur on platforms of your type.
--
Ticket URL: <http://code.djangoproject.com/ticket/13488#comment:4>
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.
