Bug 1663 - Possible memory leak in |ProcXpStartPage()|
Summary: Possible memory leak in |ProcXpStartPage()|
Status: RESOLVED WONTFIX
Alias: None
Product: xprint
Classification: Unclassified
Component: Server: Extensions: XpExtension (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high normal
Assignee: Roland Mainz
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-18 06:48 UTC by Roland Mainz
Modified: 2011-09-13 14:07 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:

Attachments

Description Roland Mainz 2004-10-18 06:48:51 UTC 
"valgrind" on Linux reports the following memory leak in |ProcXpStartPage()|
-- snip --
==24079== 128 bytes in 8 blocks are possibly lost in loss record 8 of 20
==24079==    at 0x40027B98: malloc (vg_replace_malloc.c:153)
==24079==    by 0x8091555: Xalloc (utils.c:1362)
==24079==    by 0x8196735: ProcXpStartPage (xprint.c:1858)
==24079==    by 0x8194001: ProcXpDispatch (xprint.c:469)
==24079==    by 0x8077710: Dispatch (dispatch.c:455)
==24079==    by 0x805E334: main (main.c:442)
==24079==    by 0x403068AD: __libc_start_main (in /lib/libc.so.6)
==24079==    by 0x804C290: (within
/home/gismobile/projects/xorg/work004/xc/programs/Xserver/Xprt)
==24079== 
==24079== 
==24079== 160444 bytes in 10012 blocks are definitely lost in loss record 20 of
20
==24079==    at 0x40027B98: malloc (vg_replace_malloc.c:153)
==24079==    by 0x8091555: Xalloc (utils.c:1362)
==24079==    by 0x8196735: ProcXpStartPage (xprint.c:1858)
==24079==    by 0x8194001: ProcXpDispatch (xprint.c:469)
==24079==    by 0x8077710: Dispatch (dispatch.c:455)
==24079==    by 0x805E334: main (main.c:442)
==24079==    by 0x403068AD: __libc_start_main (in /lib/libc.so.6)
==24079==    by 0x804C290: (within
/home/gismobile/projects/xorg/work004/xc/programs/Xserver/Xprt)
-- snip --

It seems each XpStartPage() causes memory tp be leaked in the server... ;-(
Comment 1 Corbin Simpson 2011-09-13 14:07:00 UTC 
Closing WONTFIX because nobody cares about Xprint. Reopen if you plan to address this bug.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.