> The base class is simply never cleaned up. Typical types registered with
> GType are static, meaning they aren't ever cleaned up for the entire duration
> of the process.
>
> Why do you need to clean up the type?
I'm making a framework which other developers will use to create applications.
Ye
> From: Tristan Van Berkom [mailto:tris...@upstairslabs.com]
> Sent: 10. februar 2015 08:25
> To: Norman, Anders
> Cc: gtk-list@gnome.org
> Subject: RE: Memory leak in gdbus-codegen generated code
>
> On Tue, 2015-02-10 at 06:59 +, Norman, Anders wrote:
> > Well, I consider it a leak and need i
On 10/02/2015 08:37, Norman, Anders wrote:
The base class is simply never cleaned up. Typical types registered with GType
are static, meaning they aren't ever cleaned up for the entire duration of the
process.
Why do you need to clean up the type?
I'm making a framework which other developers
On Tue, 2015-02-10 at 08:45 +, Norman, Anders wrote:
> > From: Tristan Van Berkom [mailto:tris...@upstairslabs.com]
> > Sent: 10. februar 2015 08:25
> > To: Norman, Anders
> > Cc: gtk-list@gnome.org
> > Subject: RE: Memory leak in gdbus-codegen generated code
> >
> > On Tue, 2015-02-10 at 06:59
On Tue, Feb 10, 2015 at 3:37 AM, Norman, Anders
wrote:
> > The base class is simply never cleaned up. Typical types registered with
> GType are static, meaning they aren't ever cleaned up for the entire
> duration of the process.
> >
> > Why do you need to clean up the type?
> I'm making a framew
I don't see *how* we can clean it up. We could register an atexit handler
which tears down everybody's classes, but then we're just doing work for no
reason: the OS will clean up our memory in any case.
The issue seems to be "I'm using valgrind and it mentions a lot of
'possibly lost' data." In wh
