--===============0288271511==
Content-Type: multipart/alternative; boundary=0016363b83a47e1c51049917db12

--0016363b83a47e1c51049917db12
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Jan 5, 2011 at 10:41 AM, Boudewijn Rempt <boud@valdyas.org> wrote:

> commit eb493aa2b562b0a384899b2327501ac058171aaf
> branch master
> Author: Boudewijn Rempt <boud@valdyas.org>
> Date:   Wed Jan 5 10:36:19 2011 +0100
>
>    check whether the image wsp is valid
>
>    We should check whether a weak shared pointer is valid, instead
>    of checking the pointer -- which isn't set to 0 after the corresponding
>    shared pointer is deleted.
>
>    Should be backported to 2.3.
>
>    CCMAIL:kimageshop@kde.org <CCMAIL%3Akimageshop@kde.org>
>
>    BUG:261940
>

I don't think that this is the complete fix. The problem indicates that
there is an old layer from a now invalid image still around.

--0016363b83a47e1c51049917db12
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote">On Wed, Jan 5, 2011 at 10:41 AM, Boudewijn Rempt=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:boud@valdyas.org" target=3D"_blank=
">boud@valdyas.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt =
0.8ex; padding-left: 1ex;">

commit eb493aa2b562b0a384899b2327501ac058171aaf<br>
branch master<br>
Author: Boudewijn Rempt &lt;<a href=3D"mailto:boud@valdyas.org" target=3D"_=
blank">boud@valdyas.org</a>&gt;<br>
Date: =A0 Wed Jan 5 10:36:19 2011 +0100<br>
<br>
 =A0 =A0check whether the image wsp is valid<br>
<br>
 =A0 =A0We should check whether a weak shared pointer is valid, instead<br>
 =A0 =A0of checking the pointer -- which isn&#39;t set to 0 after the corre=
sponding<br>
 =A0 =A0shared pointer is deleted.<br>
<br>
 =A0 =A0Should be backported to 2.3.<br>
<br>
 =A0 =A0<a href=3D"mailto:CCMAIL%3Akimageshop@kde.org" target=3D"_blank">CC=
MAIL:kimageshop@kde.org</a><br>
<br>
 =A0 =A0BUG:261940<br></blockquote><div><br>I don&#39;t think that this is =
the complete fix. The problem indicates that there is an old layer from a n=
ow invalid image still around.<br></div></div>

--0016363b83a47e1c51049917db12--

--===============0288271511==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
kimageshop mailing list
kimageshop@kde.org
https://mail.kde.org/mailman/listinfo/kimageshop

--===============0288271511==--