I will try to work on it and get back to you. But tell me where will I get
valgrind. If you can point it I will be able to get it.Important Regarding the Modaless windows, I created a modaless window, with two buttons on it also I mapped the button events to properly. When I show the window, it is able to show the window properly. But I am not able to get the button click events. Can you please tell me why this is happening. Also When I make it modal, I am able to get the button clicks, Is there anything I should do to make it work. Regards RD -----Original Message----- From: Sven Neumann [mailto:[EMAIL PROTECTED]]On Behalf Of Sven Neumann Sent: Saturday, August 10, 2002 09:32 P To: R O N A L D D U C K Cc: [EMAIL PROTECTED] Subject: [directfb-users] Re: Suspected Memory Leak in gtk Hi, "R O N A L D D U C K" <[EMAIL PROTECTED]> writes: > In course of developing my application I found something strange in the > gtk+-directfb. > > Environment > ~~~~~~~~~~~ > 1) gtk+-directfb-2.0.5 > 2) DirectFB-0.9.12 > 3) Pentium III > 4) glib-2.0 > 5) 128 MB RAM etc > 6) RedHat Linux 7.1 > 7) VISA Frame buffer > 8) Intel i810 Chipset > > I wrote a small application which was having 10 Buttons, If you press any > one it will pop up hai to you. I connected another PC through the serial > shell, so that I can see the memory usage and other activities of this > application. I ran my application in the machine and ran 'top' (Program to > view the process and memory status) on the serial shell (Other machine), I > was surprised to the see the memory usage when I just pressed 'TAB' key > continuously. I have not even pressed the button, I was simply pressing TAB > key 1 time per second. (I just pressed the TAB keys to find out wheather > the key traversing was ok) > > The memory was getting increased by 16 bytes or more for every four TAB key > press. I also found that, even you use arrow keys to traverse the same > behaviors was happening. I wouldn't be surprised if there are some memleaks left in GTK+-DirectFB since I haven't used any memory leak detectors on it for a long time. I'd suggest you try valgrind to find the cause of the leak or just audit the code carefully. > Please address this issue. And help me I will if I find the time but I'd also be happy if you located the problem and sent a patch to fix it. Salut, Sven -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-users" as subject. -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-users" as subject.
