Bug #68164 for PDF-Create: Expunge data as part of $pdf->close;

Thu May 12 22:05:10 2011 vollrath111 [...] comcast.net - Ticket created

Subject:	Expunge data as part of $pdf->close;
Date:	Fri, 13 May 2011 02:04:56 +0000 (UTC)
To:	bug-PDF-Create [...] rt.cpan.org
From:	vollrath111 [...] comcast.net

To whom it may concern: It would be greatly helpful if $pdf->close would use perl's delete to expunge all the data structures supporting the "current" PDF (the $pdf referent and all its parts ) , thus free-ing up sufficient memory to handle the "next" pdf. In my application I need to create a series of PDF files (printable invoices, one pdf per invoice) from a large file that contains data for many invoices. On my laptop with 2GB, by the fifth invoice I get an error abort -- !Out of Memory. A quick patch would be ideal (would a return email be too much to ask?). Thanks, Al Vollrath 312-282-8820 P.S.: Great package--easy to use and fairly fast.

Fri May 13 05:00:21 2011 MARKUSB [...] cpan.org - Status changed from 'new' to 'open'

Fri May 13 05:00:21 2011 MARKUSB [...] cpan.org - Severity Normal added

Fri May 13 05:00:22 2011 MARKUSB [...] cpan.org - Broken in 1.06 added

Fri May 13 05:08:48 2011 MARKUSB [...] cpan.org - Correspondence added

On Thu May 12 22:05:10 2011, vollrath111@comcast.net wrote: Show quoted text

> It would be greatly helpful if $pdf->close would use perl's delete to > expunge all the data structures supporting the "current" PDF (the > $pdf referent and all its parts ) , thus free-ing up sufficient > memory to handle the "next" pdf.

Hi Al, I understand the problem, but don't have a fix handy. Could you provide a patch for a solution for the problem ? Markus

Fri May 13 15:56:52 2011 vollrath111 [...] comcast.net - Correspondence added

Subject:	Re: [rt.cpan.org #68164] Expunge data as part of $pdf->close;
Date:	Fri, 13 May 2011 19:56:40 +0000 (UTC)
To:	bug-PDF-Create [...] rt.cpan.org
From:	vollrath111 [...] comcast.net

Markus, Unfortunately, I don't have know how to do that, hence the request. Sorry. Al Show quoted text

----- Original Message ----- From: "Markus Baertschi via RT" <bug-PDF-Create@rt.cpan.org> To: vollrath111@comcast.net Sent: Friday, May 13, 2011 5:08:50 AM Subject: [rt.cpan.org #68164] Expunge data as part of $pdf->close; <URL: https://rt.cpan.org/Ticket/Display.html?id=68164 > On Thu May 12 22:05:10 2011, vollrath111@comcast.net wrote:

> It would be greatly helpful if $pdf->close would use perl's delete to > expunge all the data structures supporting the "current" PDF (the > $pdf referent and all its parts ) , thus free-ing up sufficient > memory to handle the "next" pdf.

Hi Al, I understand the problem, but don't have a fix handy. Could you provide a patch for a solution for the problem ? Markus

Thu Feb 27 11:52:59 2014 chris_jack [...] msn.com - Correspondence added

From:

chris_jack [...] msn.com

So you're aware, I've reproduced this and shown how the problem is happening with the Test::LeakTrace module. I've put a new bug report in so maybe it will get sorted out? Regards Chris On Thu May 12 22:05:10 2011, vollrath111@comcast.net wrote: Show quoted text

> > > To whom it may concern: > > > > It would be greatly helpful if $pdf->close would use perl's delete to > expunge all the data structures supporting the "current" PDF (the $pdf > referent and all its parts ) , thus free-ing up sufficient memory to > handle the "next" pdf. > > > > In my application I need to create a series of PDF files (printable > invoices, one pdf per invoice) from a large file that contains data > for many invoices. On my laptop with 2GB, by the fifth invoice I get > an error abort -- !Out of Memory. > > > > A quick patch would be ideal (would a return email be too much to > ask?). > > Thanks, > > Al Vollrath > > 312-282-8820 > > > > P.S.: Great package--easy to use and fairly fast.

Thu Aug 21 08:25:53 2014 SZABGAB [...] cpan.org - Correspondence added

at least some of the memory leaking has been fixed in the next version of the module.

Thu Aug 21 08:25:54 2014 SZABGAB [...] cpan.org - Status changed from 'open' to 'resolved'