A memory leak problem in GtkTextView

2008-08-29 Thread ustc.chip
Hi, I'm facing a problem in the use of GtkTextView. When I insert a image into the GtkTextView, there is an explicit memory leak problem. Some source code is as follow: // image=gtk_image_new_from_file(path); gtk_widget_show(image); anchor = gtk_text_buffer_create_child_a

Re: is there a memory leak problem with gtk_widget_queue_draw()?

2007-09-09 Thread okty
's memory profiling to check memory usage of my program. I >> noticed that for each refresh in my screen with gtk_widget_queue_draw(), >> I >> am checking my allocated memory and each refresh increases the size of >> allocated memory. Do you know any memory leak problem in

Re: is there a memory leak problem with gtk_widget_queue_draw()?

2007-09-07 Thread Jim George
he size of > allocated memory. Do you know any memory leak problem in > gtk_widget_queue_draw()? The page http://live.gnome.org/Valgrind has some info on providing flags to glib, making it use less efficient (but memcheck-friendly) memory allocation code. Also, try writing a bare-bones pr

Re: is there a memory leak problem with gtk_widget_queue_draw()?

2007-09-07 Thread Fernando ApesteguĂ­a
he size of > allocated memory. Do you know any memory leak problem in > gtk_widget_queue_draw()? I've never used Glib's memory profiling, but sometimes other programs like Valgrind (you could use this as well) report false positives in memory leaks. It has something to do with t

is there a memory leak problem with gtk_widget_queue_draw()?

2007-09-07 Thread okty
Hi, I am using GLib's memory profiling to check memory usage of my program. I noticed that for each refresh in my screen with gtk_widget_queue_draw(), I am checking my allocated memory and each refresh increases the size of allocated memory. Do you know any memory leak probl

Memory leak problem

2005-05-28 Thread John Coppens
Hi all. Please check this code fragment: pxb = gdk_pixbuf_new_from_file(path, &err); // Check if the image was previously allocated. If so, destroy it // Note that this relies on the pxb being destroyed too. It seems // this does _not_ happen (Valgrind indicate this) if (img_item) gtk_o