问题描述
所以...我正在尝试从我的 GTK+ 3 程序中消除一些内存泄漏.我虽然回顾一些简单的例子来看看是否有一些我忘记的清理东西是个好主意，但是文档中提供的 hello_world 程序也有泄漏.(Valgrind 输出如下).
So... I'm trying to eliminate some memory leaks from my GTK+ 3 program. I though it would be a good idea to look back at some simple examples to see if there is some cleanup stuff I'm forgetting, but the hello_world program provided in the documentation has leaks too. (Valgrind output below).
这些泄漏是否可以接受?如果是这样，我是否应该使用其他一些应用程序来调试 GTK 程序?
Are these leaks acceptable? If so, is there some other application I should be using to debug GTK programs?
==13717== Memcheck, a memory error detector
==13717== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==13717== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==13717== Command: ./a
==13717==
Hello World
==13717==
==13717== HEAP SUMMARY:
==13717== in use at exit: 1,578,162 bytes in 11,614 blocks
==13717== total heap usage: 45,699 allocs, 34,085 frees, 6,461,970 bytes allocated
==13717==
==13717== LEAK SUMMARY:
==13717== definitely lost: 2,560 bytes in 5 blocks
==13717== indirectly lost: 6,656 bytes in 207 blocks
==13717== possibly lost: 363,228 bytes in 1,937 blocks
==13717== still reachable: 1,205,718 bytes in 9,465 blocks
==13717== suppressed: 0 bytes in 0 blocks
==13717== Rerun with --leak-check=full to see details of leaked memory
==13717==
==13717== For counts of detected and suppressed errors, rerun with: -v
==13717== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
代码:
#include <gtk/gtk.h>
/* This is a callback function. The data arguments are ignored
* in this example. More on callbacks below.
*/
static void
print_hello (GtkWidget *widget,
gpointer data)
{
g_print ("Hello World
");
}
static gboolean
on_delete_event (GtkWidget *widget,
GdkEvent *event,
gpointer data)
{
/* If you return FALSE in the "delete_event" signal handler,
* GTK will emit the "destroy" signal. Returning TRUE means
* you don't want the window to be destroyed.
*
* This is useful for popping up 'are you sure you want to quit?'
* type dialogs.
*/
g_print ("delete event occurred
");
return TRUE;
}
int
main (int argc,
char *argv[])
{
/* GtkWidget is the storage type for widgets */
GtkWidget *window;
GtkWidget *button;
/* This is called in all GTK applications. Arguments are parsed
* from the command line and are returned to the application.
*/
gtk_init (&argc, &argv);
/* create a new window, and set its title */
window = gtk_window_new (GTK_WINDOW_TOPLEVEL);
gtk_window_set_title (GTK_WINDOW (window), "Hello");
/* When the window emits the "delete-event" signal (which is emitted
* by GTK+ in response to an event coming from the window manager,
* usually as a result of clicking the "close" window control), we
* ask it to call the on_delete_event() function as defined above.
*
* The data passed to the callback function is NULL and is ignored
* in the callback function.
*/
g_signal_connect (window, "delete-event", G_CALLBACK (on_delete_event), NULL);
/* Here we connect the "destroy" event to the gtk_main_quit() function.
*
* This signal is emitted when we call gtk_widget_destroy() on the window,
* or if we return FALSE in the "delete_event" callback.
*/
g_signal_connect (window, "destroy", G_CALLBACK (gtk_main_quit), NULL);
/* Sets the border width of the window. */
gtk_container_set_border_width (GTK_CONTAINER (window), 10);
/* Creates a new button with the label "Hello World". */
button = gtk_button_new_with_label ("Hello World");
/* When the button receives the "clicked" signal, it will call the
* function print_hello() passing it NULL as its argument.
*
* The print_hello() function is defined above.
*/
g_signal_connect (button, "clicked", G_CALLBACK (print_hello), NULL);
/* The g_signal_connect_swapped() function will connect the "clicked" signal
* of the button to the gtk_widget_destroy() function; instead of calling it
* using the button as its argument, it will swap it with the user data
* argument. This will cause the window to be destroyed by calling
* gtk_widget_destroy() on the window.
*/
g_signal_connect_swapped (button, "clicked", G_CALLBACK (gtk_widget_destroy), window);
/* This packs the button into the window. A GtkWindow inherits from GtkBin,
* which is a special container that can only have one child
*/
gtk_container_add (GTK_CONTAINER (window), button);
/* The final step is to display this newly created widget... */
gtk_widget_show (button);
/* ... and the window */
gtk_widget_show (window);
/* All GTK applications must have a gtk_main(). Control ends here
* and waits for an event to occur (like a key press or a mouse event),
* until gtk_main_quit() is called.
*/
gtk_main ();
return 0;
}
推荐答案
这个答案是根据对同一问题的答案(在现已不存在的 www.gtkforums.com 上)汇编而成的.
This answer is compiled from answers to the same question (on the now defunct www.gtkforums.com).
GTK+ 在分配和释放应用程序生命周期所需的内部缓冲区时非常懒惰.例如，它可能会在应用程序生命周期所需的初始化期间为查找表分配一块内存区域.GTK+ 将永远不会释放它.对 Valgrind 来说，这看起来像是内存泄漏(技术上确实如此)，但作为优化，GTK+ 不会释放它，因为它将在应用程序退出期间释放，因此不是错误.这就是为什么您需要抑制文件以便 Valgrind 可以忽略这些文件.问题是您需要在大多数 GTK+ 版本更改时更改这些内容.
抑制文件的存储库:https://github.com/dtrebbien/GNOME.supp
克隆存储库后，您可以使用make"生成抑制文件(也带有 glib、gdk 和其他文件)，然后像这样将 valgrind 引用给它们:
After cloning the repository, you can generate the suppression files (also comes with glib, gdk, and others) with "make" and then refer valgrind to them like so:
valgrind ./a --suppression=/path/to/gtk3.supp
这篇关于GTK hello_world 程序中的内存泄漏的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！