Subject: | Please document in the main POD how to avoid memory leaks |
Date: | Sat, 17 May 2014 15:03:32 +0200 |
To: | bug-PDF-API2 [...] rt.cpan.org |
From: | Marco Pessotto <melmothx [...] gmail.com> |
Hello there and thanks for all your work.
While hunting down a leak in my module PDF::Imposition, it turned out
that the pdf objects weren't properly destroyed, thus producing
impressive leakages on long running processs, because I failed to call
->end or ->release on them.
The fix, once I found it, was pretty simple: just call one of the above
methods on the objects. I think it would be a good idea to have it
documented (possibly in the synopsis after ->saveas), or at least in the
doc for the "end" method, stating that failing to do so would leak
memory.
Of course, this has wishlist priority :-)
Thanks in advance
Best wishes
--
Marco