Trouble with creating a benchmark

[Dmitry Kazakov]

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 :)

-- 
Dmitry Kazakov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kimageshop/attachments/20100521/99fd14d4/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Fixed-a-crash-on-exit-from-KisProjectionBenchmark.patch
Type: text/x-patch
Size: 4856 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kimageshop/attachments/20100521/99fd14d4/attachment.patch