How to confirm a memory leak
- From: Norman Goldstein <normvcr telus net>
- To: gtk-app-devel-list gnome org
- Subject: How to confirm a memory leak
- Date: Thu, 28 Jul 2016 09:18:06 -0700
I'd like to understand how to confirm a potential memory leak in gtk3.
Valgrind shows a definite leak, and "top" shows a steadily increasing
resident set size (RES). However, as I have come to understand, due to
how gtk/glib uses slices for memory management, and how the main loop of
gtk plays a part, things are not as straightforward as I have just
outlined. Is there a definitive guide, "How to confirm a memory leak in
GTK"? I have only seen various relevant pages on the net.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]