#25072: GDALRaster Garbage Collection not working
-------------------------------------+-------------------------------------
Reporter: yellowcap | Owner: nobody
Type: Bug | Status: closed
Component: GIS | Version: master
Severity: Normal | Resolution: fixed
Keywords: memory gis raster | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Claude Paroz <claude@…>):
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"d72f8862cb1a39934952e708c3c869be1399846e" d72f8862]:
{{{
#!CommitTicketReference repository=""
revision="d72f8862cb1a39934952e708c3c869be1399846e"
Fixed #25072 -- Prevented GDALRaster memory to be uncollectable
Setting GDALRaster.bands as a cached property was creating a circular
reference with objects having __del__ methods, which means the memory
could never be freed.
Thanks Daniel Wiesmann for the report and test, and Tim Graham for the
review.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/25072#comment:14>
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/067.baf3775d4eec4a7727526b86a311bbaf%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.