Hi,
This is related to the SO question
http://stackoverflow.com/questions/29823097/glib-memory-leak-when-creating-gdbusproxy
I'm using Glibmm (2.44.0) and also faced a memory leak problem when
instantiating/freeing Gio::DBus::Proxy. It doesn't look to be Glibmm specific,
so question
On Wed, 6 Jan 2016 15:14:32 +0200
Andrejs Hanins wrote:
> Hi,
>
> This is related to the SO question
> http://stackoverflow.com/questions/29823097/glib-memory-leak-when-creating-gdbusproxy
>
> I'm using Glibmm (2.44.0) and also faced a memory leak problem
> when
GTK2 on Linux is not relocatable. I did a patch that makes it so, it lives
somewhere in bugzilla. We have been using it in our distro-neutral
builds/packages of Ardour for several years (the package includes all
required libraries except libc and X Window, and GTK is the only one that
is not
Hi
I'm sure most people have encountered this problem at some point, you
are scrolling a window which contains spinboxes or comboboxes and you
accidentally change a value or setting. I find Glade especially bad in
this respect.
In my own application I tried blocking the scroll-events from the
I'm using glib without the whole GObject system and reference counting
mechanism, and I'd like to integrate bdwgc
(https://github.com/ivmai/bdwgc/) because of the complexity of my
program.
I've read about using GMemVTable to redirect memory allocation of glib
to GC_malloc, however as in