#34356: Memory leak when generating PDFs
-------------------------------------+-------------------------------------
Reporter: Robin (Robert) | Owner: nobody
Thomas |
Type: Bug | Status: closed
Component: Core (Other) | Version: 4.1
Severity: Normal | Resolution: needsinfo
Keywords: memory memory-leak | Triage Stage:
pdf weasyprint | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Often this is Python's garbage collection not kicking in as soon as you
want. First this I'd do it add a `gc.collect()` after processing the PDF,
to see if you can bring it down by hand. (If the memory is collected, it's
not a leak per se… — unless there's something specific, gc behaviour is a
Python issue, rather than anything Django can do.)
--
Ticket URL: <https://code.djangoproject.com/ticket/34356#comment:6>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070186732ad523-9129b1c0-0cfb-4f1c-b531-e8669050ca2c-000000%40eu-central-1.amazonses.com.
