Hi;
On 3 August 2016 at 17:54, Jonas wrote:
> Thanks for the info about the slice allocator, I think that'll be good
> for my purposes. As for valgrind and the suppression files, I tried a
> few, it's too bad that it's hard to differentiate between actual memory
> leaks and the ones that valgrin
Hi Emanuelle,
Thanks for the info about the slice allocator, I think that'll be good
for my purposes. As for valgrind and the suppression files, I tried a
few, it's too bad that it's hard to differentiate between actual memory
leaks and the ones that valgrind shows as leaks... Do you have any
othe
Hi;
On 3 August 2016 at 15:37, Jonas wrote:
> Hello Emmanuele,
>
> I reran my code, looked a bit at the archives (especially your answer
> to a question about a potential memory leak of gtk_widget_destroy()
> https://mail.gnome.org/archives/gtk-list/2008-September/msg00108.html)
> and here's wher
Hello Emmanuele,
I reran my code, looked a bit at the archives (especially your answer
to a question about a potential memory leak of gtk_widget_destroy()
https://mail.gnome.org/archives/gtk-list/2008-September/msg00108.html)
and here's where I am now:
- not only the test program for the dialog i
Hi;
you should probably search the archives of this very mailing list, as
this question has been asked countless times.
The tl;dr is:
* GObject uses a slab allocator, not the system one
* top is not a memory profiling tool
* if you keep things running in a tight loop you don't give GTK any
ch
Hello everyone,
I have a question about a memory leak I seem to have with GtkDialog. I
already posted this on DreaminCode (username Progammer) and decided to
ask the same question on the mailing lists here. Here it is:
"[...]I looked at the Gtk and GObject Documentation and figured out the
follow
