Skip Menu |
 

This queue is for tickets about the PDF-API2 CPAN distribution.

Report information
The Basics
Id: 95734
Status: resolved
Priority: 0/
Queue: PDF-API2

People
Owner: Nobody in particular
Requestors: melmothx [...] gmail.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 2.022



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>
Download (untitled) / with headers
text/plain 651b
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
Download (untitled) / with headers
text/plain 257b
Thanks for the feature request. For the next release, I've updated the documentation for saveas(), stringify(), and end() to indicate that the first two free memory after writing, and that the third should be called if files are being read but not written.
Subject: Re: [rt.cpan.org #95734] Please document in the main POD how to avoid memory leaks
Date: Fri, 13 Jun 2014 16:31:44 +0200
To: bug-PDF-API2 [...] rt.cpan.org
From: Marco Pessotto <melmothx [...] gmail.com>
Download (untitled) / with headers
text/plain 403b
"Steve Simms via RT" <bug-PDF-API2@rt.cpan.org> writes: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=95734 > > > Thanks for the feature request. For the next release, I've updated the > documentation for saveas(), stringify(), and end() to indicate that > the first two free memory after writing, and that the third should be > called if files are being read but not written.
Thanks! -- Marco


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.