#29989: Geodjango running through memory
-------------------------------------+-------------------------------------
Reporter: Taylor | Owner: nobody
Type: Bug | Status: new
Component: GIS | Version: 2.1
Severity: Normal | Resolution:
Keywords: raster, geodjango, | Triage Stage:
postgis | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
Please provide a full traceback so we can determine in which phase the
process runs out of memory. I assume it's happening at on the `save()`
call?
Also while I'm not that familiar with GDAL rasters I know that TIFF images
can be heavily compressed so it's possible that even if the ''compressed''
file is only 1GB it could be way larger uncompressed.
--
Ticket URL: <https://code.djangoproject.com/ticket/29989#comment:1>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.2b27cce8054b0b3b58021f2f8a82b1e2%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
