Potential memory leak in WeaverImpl
mirko at kde.org
Sun May 11 16:37:07 BST 2008
On Saturday 10 May 2008 21:52:35 Michael Jansen wrote:
> I'm currently playing with valgrind. It says in
> 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.
thanks for finding out. I will double check it and fix the leaks.
KDE e.V.: http://ev.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel