Comments on: Avoiding memory leaks with GtkTreeView http://blogs.gnome.org/johannes/2007/09/02/avoiding-memory-leaks-with-gtktreeview/ Blog of Johannes Schmid Sun, 05 Feb 2012 00:22:37 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Thomas http://blogs.gnome.org/johannes/2007/09/02/avoiding-memory-leaks-with-gtktreeview/comment-page-1/#comment-342 Thomas Tue, 04 Sep 2007 09:46:02 +0000 http://blogs.gnome.org/johannes/2007/09/02/avoiding-memory-leaks-with-gtktreeview/#comment-342 Shouldn't a valgrind plugin of some sort be able to detect that ? Shouldn’t a valgrind plugin of some sort be able to detect that ?

]]> By: Daniel Elstner http://blogs.gnome.org/johannes/2007/09/02/avoiding-memory-leaks-with-gtktreeview/comment-page-1/#comment-341 Daniel Elstner Mon, 03 Sep 2007 18:15:55 +0000 http://blogs.gnome.org/johannes/2007/09/02/avoiding-memory-leaks-with-gtktreeview/#comment-341 Or just use gtkmm. :-P Or just use gtkmm. :-P

]]> By: Ross http://blogs.gnome.org/johannes/2007/09/02/avoiding-memory-leaks-with-gtktreeview/comment-page-1/#comment-345 Ross Sun, 02 Sep 2007 20:21:04 +0000 http://blogs.gnome.org/johannes/2007/09/02/avoiding-memory-leaks-with-gtktreeview/#comment-345 Strictly speaking, you free all memory you get from gtk_tree_model_get(). So you free strings, unref objects, unref boxed types, and so on. Obviously literal pointers and integer types don't need any special work. Strictly speaking, you free all memory you get from gtk_tree_model_get(). So you free strings, unref objects, unref boxed types, and so on. Obviously literal pointers and integer types don’t need any special work.

]]> By: johannes.schmid http://blogs.gnome.org/johannes/2007/09/02/avoiding-memory-leaks-with-gtktreeview/comment-page-1/#comment-344 johannes.schmid Sun, 02 Sep 2007 17:14:21 +0000 http://blogs.gnome.org/johannes/2007/09/02/avoiding-memory-leaks-with-gtktreeview/#comment-344 hmm, might be difficult to do this in an automated way as there might be a lot of code depending on the string before I can be free'd. But maybe some grep wizards might even be able to do this. Anyway, I think it's better to check your code with valgrind to fix those (and other bugs). This also gives you hints on invalid reads/writes. hmm, might be difficult to do this in an automated way as there might be a lot of code depending on the string before I can be free’d. But maybe some grep wizards might even be able to do this. Anyway, I think it’s better to check your code with valgrind to fix those (and other bugs). This also gives you hints on invalid reads/writes.

]]> By: bjoern http://blogs.gnome.org/johannes/2007/09/02/avoiding-memory-leaks-with-gtktreeview/comment-page-1/#comment-343 bjoern Sun, 02 Sep 2007 16:05:18 +0000 http://blogs.gnome.org/johannes/2007/09/02/avoiding-memory-leaks-with-gtktreeview/#comment-343 Hi Johannes, it is possible to scan gnome-svn for such code fragment? Maybe, we can start a gnome-goal to fix that. Hi Johannes,

it is possible to scan gnome-svn for such code fragment?
Maybe, we can start a gnome-goal to fix that.

]]>