Opened 14 years ago
Last modified 8 years ago
#13488 closed
GeoDjango — at Initial Version
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | GIS | Version: | 1.2 |
| Severity: | Normal | Keywords: | gis |
| Cc: | brandon.konkle@…, proppy@…, craig.destigter@…, sheats@… | Triage Stage: | Accepted |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | yes |
| Easy pickings: | no | UI/UX: | no |
Description
I see this traceback in GeoDjango when the application exits. Not exactly
sure but there may be some memory leakage here.
Exception TypeError: "'NoneType' object is not callable" in <bound method_WKTReader.del ofdjango.contrib.gis.geos.prototypes.io._WKTReader object at 0x6b1a790>> ignored
Exception TypeError: "'NoneType' object is not callable" in <bound method _WKBReader.del of <django.contrib.gis.geos.prototypes.io._WKBReader object at 0x6b43690>> ignored
Exception TypeError: "'NoneType' object is not callable" in <bound method WKBWriter.del of <django.contrib.gis.geos.prototypes.io.WKBWriter object at 0x6b1ad50>> ignored
To reproduce, just run a distance function (for example:
airport.objects.distance("POINT (-74.3166750000000036 40.9000249999999994)")
Whent the application exits (or exit from a python prompt), you'll get the
exceptions.