bug-gnustep
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug #13705] possible memory leak in setStringValue


From: UBoss UBoss
Subject: Re: [bug #13705] possible memory leak in setStringValue
Date: Mon, 29 May 2006 12:22:34 +0000

Hi Fred,
today i tried to use some of memdebug using libumem and mdb
mdb found some points with memory leaks see attached file when some audits are made.

when looking into sources there maybe the bug is in XGGState.m or GSXftFontInfo.m in gnustep-back-0.10.2 xlib

in XGGState.m xft_draw is never freed maybe it is the bug.
i'll try to recompile back with freeing it in dealloc

I hope this helps.

bye

On 5/27/06, Fred Kiefer <INVALID.NOREPLY@gnu.org> wrote:

Follow-up Comment #5, bug #13705 (project gnustep):

Could not reproduce this problem with the xlib backend on Suse 10.1 linux.
(But had other problems with that backend here)
I would think that this problem is specific to solaris. Could you please use
valgrind (or a similar tool) to find out, where the memory gets leaked?

    _______________________________________________________

Reply to this item at:

  < http://savannah.gnu.org/bugs/?func=detailitem&item_id=13705>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/


Attachment: audit
Description: Binary data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]