[bug #13705] possible memory leak in setStringValue

2006-05-30 Thread Fred Kiefer
Update of bug #13705 (project gnustep): Open/Closed: In Test => Closed ___ Reply to this item at:

[bug #13705] possible memory leak in setStringValue

2006-05-30 Thread UBoss
Follow-up Comment #7, bug #13705 (project gnustep): Tested on Solaris 10 x86 No more memory leaks Tested on Solaris 9 sparc No more momory leaks ___ Reply to this item at:

[bug #13705] possible memory leak in setStringValue

2006-05-29 Thread Fred Kiefer
Update of bug #13705 (project gnustep): Status:None => Fixed Assigned to:None => FredKiefer Open/Closed:Open => In Test _

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

2006-05-29 Thread UBoss UBoss
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 xlibin XGGState.m xft_draw is never free

[bug #13705] possible memory leak in setStringValue

2006-05-27 Thread Fred Kiefer
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, whe

[bug #13705] possible memory leak in setStringValue

2006-05-16 Thread UBoss
Follow-up Comment #4, bug #13705 (project gnustep): oh i forgot runnign on sun blade 1500 sparc solaris 8(9) ___ Reply to this item at:

[bug #13705] possible memory leak in setStringValue

2006-05-16 Thread UBoss
Follow-up Comment #3, bug #13705 (project gnustep): It realy looks like memory leak in text rendering fro me the memory increase stops when PSshow(timeStr); lines are commented but happens only on gnustep-back-0.10.2 on back-0.9.0 works fine no increase of used memory. using x11-xlib backend as

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

2005-07-10 Thread Markus Hitter
Am 10.07.2005 um 02:59 schrieb Riccardo mottola: Follow-up Comment #1, bug #13705 (project gnustep): just as a note using [NSString stringWithFormat: xxx] instead of alloc+init does the same thing and no changes. Just as another note, they are different. alloc + init avoids using the aut

[bug #13705] possible memory leak in setStringValue

2005-07-10 Thread Fred Kiefer
Follow-up Comment #2, bug #13705 (project gnustep): As this looks like an important problem I tried hard to reproduce it with a simple program, but failed to. A small loop made up of the lines you posted does not produce a memory leak: int main (int argc, const char *argv[]) { int i; NSStrin

[bug #13705] possible memory leak in setStringValue

2005-07-09 Thread Riccardo mottola
Follow-up Comment #1, bug #13705 (project gnustep): just as a note using [NSString stringWithFormat: xxx] instead of alloc+init does the same thing and no changes. ___ Reply to this item at:

[bug #13705] possible memory leak in setStringValue

2005-07-09 Thread Riccardo mottola
URL: Summary: possible memory leak in setStringValue Project: GNUstep Submitted by: rmottola Submitted on: Sun 07/10/2005 at 00:41 Category: Gui/AppKit