Trouble with creating a benchmark

Boudewijn Rempt boud at valdyas.org
Sat May 22 13:13:00 CEST 2010


On Friday 21 May 2010, Dmitry Kazakov wrote:
> Well, i've managed to fixed this.
> It was caused by direct signal connection and sequence of object's
> deletion.
> 
> It happened because KisWaitUpdateDone object was deleted before KisImage
> leaved it's slot slotImageUpdated(). It turned out that the projection
> thread was executing in the context of the object that was removed in a
> parallel thread. To fix this, i had to do explicit removal of the KisDoc2
> object and add synchronous deletion of KisProjection in the destructor of
> KisImage object.
> 
> If someone is interested, there is a small patch attached :)

I think it would be okay for you to commit this and the previous patch; that 
will make it much easier to test for all of us :-)

-- 
Boudewijn Rempt | http://www.valdyas.org


More information about the kimageshop mailing list