php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login

go to bug id or search bugs for

Bug #13230 PDF functions leak
Submitted: 2001-09-10 09:05 UTC Modified: 2001-09-10 13:09 UTC
From: derick@php.net Assigned:
Status: Closed Package: PDF related
PHP Version: 4.0CVS-2001-09-10 OS: Linux 2.4.5/RedHat
Private report: No CVE-ID: None
View Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please !
Your email address:
MUST BE VALID
Solve the problem:
34 - 18 = ?
Subscribe to this entry?

 
 [2001-09-10 09:05 UTC] derick@php.net 
This piece of code:

<?php
    $p = pdf_new ();
    pdf_open_file ($p);
    pdf_close ($p);
?>

Gives these leaks:
pdf.c(306) :  Freeing 0x0820B324 (65536 bytes), script=3pdf.php
Last leak repeated 2 times

This code:
<?php
    $p = pdf_new ();
?>

Gives this leak:
pdf.c(306) :  Freeing 0x08200D54 (2116 bytes), script=3pdf.php
Last leak repeated 1 time

regards,
Derick

Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2001-09-10 11:30 UTC] rjs@php.net 
You should call PDF_delete($); at the end of a script containing PDF functions. This will cleanup the resources allocated by PDFlib.

This might be done in the function given to zend_register_list_destructors_ex (_free_pdf_doc), but as I don't know documentation when this is called it is not yet integrated into the source pdf.c.

For the moment I donot know how to decide whether PDF_delete already was called when _free_pdf_doc() is called.

Regards
Rainer
 [2001-09-10 13:09 UTC] derick@php.net 
Fixed it myself.

Derick
 
PHP Copyright © 2001-2025 The PHP Group
All rights reserved. 		Last updated: Wed Oct 29 18:00:01 2025 UTC