<br><br><div class="gmail_quote">On Sat, May 22, 2010 at 2:13 PM, Boudewijn Rempt <span dir="ltr"><<a href="mailto:boud@valdyas.org">boud@valdyas.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On Friday 21 May 2010, Dmitry Kazakov wrote:<br>
> Well, i've managed to fixed this.<br>
> It was caused by direct signal connection and sequence of object's<br>
> deletion.<br>
><br>
> It happened because KisWaitUpdateDone object was deleted before KisImage<br>
> leaved it's slot slotImageUpdated(). It turned out that the projection<br>
> thread was executing in the context of the object that was removed in a<br>
> parallel thread. To fix this, i had to do explicit removal of the KisDoc2<br>
> object and add synchronous deletion of KisProjection in the destructor of<br>
> KisImage object.<br>
><br>
> If someone is interested, there is a small patch attached :)<br>
<br>
</div></div>I think it would be okay for you to commit this and the previous patch; that<br>
will make it much easier to test for all of us :-)<br>
</blockquote></div><br>Ok, i'll do it tomorrow morning =)<br><br clear="all"><br>-- <br>Dmitry Kazakov<br>