Potential memory leak in WeaverImpl

[Mirko Boehm]

On Saturday 10 May 2008 21:52:35 Michael Jansen wrote:
> Hi
>
> I'm currently playing with valgrind. It says in
>
> /kdelibs/threadweaver/Weaver/WeaverImpl.cpp:60
>
> those states get leaked.
>
>     // initialize state objects:
>     m_states[InConstruction] = new InConstructionState( this );
>     setState ( InConstruction );
>     m_states[WorkingHard] = new WorkingHardState( this );
>     m_states[Suspending] = new SuspendingState( this );
>     m_states[Suspended] = new SuspendedState( this );
>     m_states[ShuttingDown] = new ShuttingDownState( this );
>     m_states[Destructed] = new DestructedState( this );
>
> They don't get deleted in the destructor, but i leave it to someone with
> insight into the code to fix it.
>
> Mike
Hi, 

thanks for finding out. I will double check it and fix the leaks. 

Cheers,

Mirko.
-- 
KDE e.V.: http://ev.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080511/e8a4b583/attachment.sig>