|
From: Daniel J S. <dan...@ie...> - 2004-10-03 19:47:08
|
Ethan Merritt wrote: >On Saturday 02 October 2004 05:43 pm, Daniel J Sebald wrote: > > >>It is the QF causing problems which is executed as: >> case 'F': >> /* Strip out just the font name */ >> c = &(buffer[strlen(buffer)-1]); >> while (*c <= ' ') *c-- = '\0'; >> pr_font(&buffer[2]); >> XSetFont(dpy,gc,font->fid); >> break; >> >>When I comment out the "XSetFont" function, the memory leak goes away. >> >> > >So are you saying this is a memory leak in your X-server? >That's not really surprising, but it's not something we can fix. > >How are you testing for memory leaks? > I watch the processes, specifically the memory size parameter, as windows are open and closed. (My window manager has a convenient system monitor for watching memory... but "ps" will do too.) When a window is open, the memory size increases, naturally. But when the window is closed, the memory size doesn't necessarily have to drop back down to its previous value because sometimes the heap isn't cleared immediately. (Perhaps the kernel thinks the process will want the memory again.) However, if you plot the same exact plot, the memory should not grow any higher than the previous. In other words, keep plotting and closing the same plot; we shouldn't see memory keep on growing, just stay within some limit. Now, for the unsolved leak, just resizing the very first plot should keep making the memory for the process "gnuplot_x11" keep growing. Dan |