[libGD] #224 [Task opened] memory leak in gdImageTrueColorToPalette

[email protected] Mon, 10 May 2010 19:04:54 +0200 (CEST)
Newsgroups php.gd.bugs
Message-ID <[email protected]>
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

A new Flyspray task has been opened.  Details are below. 

User who did this - maggie Lin (mlin) 

Attached to Project - libGD
Summary - memory leak in gdImageTrueColorToPalette
Task Type - Bug Report
Category - General
Status - Unconfirmed
Assigned To - 
Operating System - All
Severity - High
Priority - Normal
Reported Version - 2.0.35
Due in Version - Undecided
Due Date - Undecided
Details - 6 byte memory leak in function call of gdImageTrueColorToPalette from C++.
let me know if you need more info. Thanks

Maggie
gd version:
Installed Packages:
gd-devel.x86_64                      2.0.33-9.4.el5_4.2     installed
Available Packages:
gd-devel.i386                        2.0.33-9.4.el5_4.2     updates

valgrind memory check result:
[root@tilesgen-dev gd_maps_mlin]# valgrind -q -v --tool=memcheck --leak-check=full --show-below-main=yes  --num-callers=40 ./fimage fuseimage1.def city_ir.txt -ir  noaaport_satir/201005101210
==12871== Memcheck, a memory error detector.
==12871== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al.
==12871== Using LibVEX rev 1658, a library for dynamic binary translation.
==12871== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP.
==12871== Using valgrind-3.2.1, a dynamic binary instrumentation framework.
==12871== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al.
==12871== For more details, rerun with: -v
==12871==
^[[B==12871==
==12871== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 4 from 1)
==12871== malloc/free: in use at exit: 1,584 bytes in 264 blocks.
==12871== malloc/free: 2,393,832 allocs, 2,393,568 frees, 5,381,428,108 bytes allocated.
==12871== For counts of detected errors, rerun with: -v
==12871== searching for pointers to 264 not-freed blocks.
==12871== checked 530,184 bytes.
==12871==
==12871== 1,584 bytes in 264 blocks are definitely lost in loss record 1 of 1
==12871==    at 0x4A05809: malloc (vg_replace_malloc.c:149)
==12871==    by 0x4C306A3: (within /usr/lib64/libgd.so.2.0.0)
==12871==    by 0x407444: langCropImage(gdImageStruct*, char const*, std::string const*, int, int, int const*, int const*, std::string const*, std::basic_ofstream<char, std::char_traits<char> >*, bool) (in /var/www/html/gd_maps_mlin/fimage)
==12871==    by 0x4085CA: drawFuseImage(std::basic_ofstream<char, std::char_traits<char> >*, double const*, double const*, int const*, int const*, int const*, std::string, std::string, bool) (in /var/www/html/gd_maps_mlin/fimage)
==12871==    by 0x40959D: main (in /var/www/html/gd_maps_mlin/fimage)
==12871==    by 0x373F81D8A3: (below main) (in /lib64/libc-2.5.so)
==12871==    by 0x402258: (within /var/www/html/gd_maps_mlin/fimage)
==12871==
==12871== LEAK SUMMARY:
==12871==    definitely lost: 1,584 bytes in 264 blocks.
==12871==      possibly lost: 0 bytes in 0 blocks.
==12871==    still reachable: 0 bytes in 0 blocks.
==12871==         suppressed: 0 bytes in 0 blocks.
==12871== Reachable blocks (those to which a pointer was found) are not shown.
==12871== To see them, rerun with: --show-reachable=yes






More information can be found at the following URL:
http://bugs.libgd.org/?do=details&task_id=224

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.