[gs-bugs] [Bug 691643] New: memory leaks in ghostxps

bugzilla-daemon at ghostscript.com bugzilla-daemon at ghostscript.com
Fri Sep 24 10:50:01 UTC 2010


           Summary: memory leaks in ghostxps
           Product: GhostXPS
           Version: trunk
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P4
         Component: General
        AssignedTo: tor.andersson at artifex.com
        ReportedBy: tor.andersson at artifex.com
         QAContact: gs-bugs at ghostscript.com
   Estimated Hours: 0.0

Created an attachment (id=6754)
 --> (http://bugs.ghostscript.com/attachment.cgi?id=6754)

leak [a+]chunk_obj_alloc (xps_new_part)(303296) = 0xf53860
leak [a+]chunk_obj_alloc (xps_new_part)(367112) = 0xfc6140
leak [a+]chunk_obj_alloc (xps_new_part)(409280) = 0x102fc40
leak [a+]chunk_obj_alloc (xps_parse_metadata_imp)(29) = 0xf26b80

as well as

leak [a+]chunk_obj_alloc (gsicc_load_profile)(3144) = 0xf1cf20
leak [a+]chunk_obj_alloc (gsicc_load_profile)(416) = 0x1374f40
leak [a+]chunk_obj_alloc (gsicc_load_profile)(5340) = 0x13713a0
leak [a+]chunk_obj_alloc (gsicc_load_profile)(564) = 0x1370fa0
leak [a+]chunk_obj_alloc (gsicc_new_iccsmask)(32) = 0x1e7d900
leak [a+]chunk_obj_alloc (gsicc_profile_new)(10) = 0x1370c40
leak [a+]chunk_obj_alloc (gsicc_profile_new)(11) = 0x1370c80
leak [a+]chunk_obj_alloc (gsicc_profile_new)(11) = 0x1374f00
leak [a+]chunk_obj_alloc (gsicc_profile_new)(15) = 0xf1cb80
leak [a+]chunk_obj_alloc (gsicc_profile_new)(296) = 0x1370e40
leak [a+]chunk_obj_alloc (gsicc_profile_new)(296) = 0x1371240
leak [a+]chunk_obj_alloc (gsicc_profile_new)(296) = 0x1374da0
leak [a+]chunk_obj_alloc (gsicc_profile_new)(296) = 0xf1cdc0

detected by running with the attached leaks.awk script:

./xps/debugobj/gxps -sDEVICE=ppmraw -sOutputFile=foo.pnm -ZA -l -dNOPAUSE
-dQUIT -dBATCH /mnt/d/tests_xps/xpsfts-a4/fts_01xx.xps 2>&1 | awk -f leaks.awk

Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

More information about the gs-bugs mailing list