Re: [Evolution] About performance

[Adam Tauno Williams <awilliam whitemice org>]

On Fri, 2013-04-05 at 11:57 +0200, Thomas Prost wrote: 
> Am Mittwoch, den 27.03.2013, 00:54 +0100 schrieb Thomas Prost: 
> > Am Montag, den 11.03.2013, 16:55 -0400 schrieb Matthew Barnes:
> > (...) 
> > > Widgets from closed composer windows were sticking around in memory and
> > Is there an easy way to check that ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ? 
> obviously not :-(

No.  Hunting memory leaks [in 'unmanaged' code] is tough work; it
usually involves a tool like valgrind and a full development stack.  Or
just code review at a maddeningly tedious level [this works best at 2am
in a dark world of complete silence, or accompanied by harsh death metal
rock at a volume of stun].

But I believe Mr. Barnes indicated the problem mentioned is fixed in
current releases.

Even in 'managed' code [Java, .NET, etc...] it involves sifting through
a lot of data; first you have to see the leak, and *then* you have to
figure out what code is to blame.  And asking yourself 'why didn't I
just become a bar tender?'