c f wrote:
>
> I have checked the GTK documentation and it states that gtk_exit free
> all resources allocated for GTK+. gtk_exit is depricated and using
> exit is recommended. I have tested both but non of them improved the
> situation (still more than 5000 leaks).
This is normal. GTK is not go
On Sat, 2007-11-24 at 10:09 +0100, Vincent Torri wrote:
> >> From what I've heard about memory leaking, this is not unique to the
> > GTK library. If the rumours are correct, applications like `ls` are
> > notorious for leaking memory, safe in the knowledge that the OS will
> > clean up after th
Junior Polegato - GTK+ & GTKmm wrote:
> Vincent Torri escreveu:
>> On Sat, 24 Nov 2007, Junior Polegato - GTK+ & GTKmm wrote:
>>> Vincent Torri escreveu:
On Sat, 24 Nov 2007, Michael Lamothe wrote:
>> From what I've heard about memory leaking, this is not unique to the
> GTK library.
Vincent Torri escreveu:
> On Sat, 24 Nov 2007, Junior Polegato - GTK+ & GTKmm wrote:
>> Vincent Torri escreveu:
>>> On Sat, 24 Nov 2007, Michael Lamothe wrote:
> From what I've heard about memory leaking, this is not unique to the
GTK library. If the rumours are correct, applications like
On Sat, 24 Nov 2007, Junior Polegato - GTK+ & GTKmm wrote:
> Vincent Torri escreveu:
>> On Sat, 24 Nov 2007, Michael Lamothe wrote:
>>
From what I've heard about memory leaking, this is not unique to the
>>> GTK library. If the rumours are correct, applications like `ls` are
>>> not
Vincent Torri escreveu:
> On Sat, 24 Nov 2007, Michael Lamothe wrote:
>
>>> From what I've heard about memory leaking, this is not unique to the
>>>
>> GTK library. If the rumours are correct, applications like `ls` are
>> notorious for leaking memory, safe in the knowledge that the OS w
On Sat, 24 Nov 2007, Michael Lamothe wrote:
>> From what I've heard about memory leaking, this is not unique to the
> GTK library. If the rumours are correct, applications like `ls` are
> notorious for leaking memory, safe in the knowledge that the OS will
> clean up after them.
and if someone
>From what I've heard about memory leaking, this is not unique to the
GTK library. If the rumours are correct, applications like `ls` are
notorious for leaking memory, safe in the knowledge that the OS will
clean up after them.
Excellent work on the enable-debug switch, I'll have to keep this
ema
Hi,
In my opinion the definition what you have given describes well when a
memory leak can cause serious problems but I would call memory
leak,any dynamically allocated memory what is not freed when you are
done with it .
However it is true that OS will cleanup everything when the program
termina
> > I have used mtrace to check for memory leaks. In this simple
> > application there are more than 5000 memory allocation which is not
> > freed.
Note that just a dynamic memory allocation that isn't freed before the
application terminates is not a leak, in case there still exists a way
to acces
On Wed, 21 Nov 2007 20:15:25 +0100 c f wrote:
[...]
> I have used mtrace to check for memory leaks. In this simple
> application there are more than 5000 memory allocation which is not
> freed.
See:
http://www.gtk.org/faq/#AEN703
> I have checked the GTK documentation and it states that gtk_ex
Hi Michael,
Thanks for your suggestion.
Actually I have not mentioned but I also tried to decrease the ref
count of the mainWindow (just to be sure). In theory it is already
destroyed at this point as the main quit is called in the destoyed
handler of the main window. In that case (unref), GTK sh
I'm no master profiler but I think that you'll want to put a
gtk_widget_destroy(mainWindow); after the gtk_main();. You really
don't need to do this because it will be destroyed when the
application terminates 0.01 seconds after that line. But if you feel
you must then go for it. I also like to
Hi,
I have made a simple application with a top level window:
"
#include
#include
gboolean OnDeleteHandler(GtkWidget *sender,
GdkEvent *event,
gpointer data)
{
return FALSE;
}
void OnDestroyHandler(GtkWidget *sender, gpointer data)
14 matches
Mail list logo
