[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-kimageshop
Subject:    Re: koffice/krita/image
From:       Dmitry Kazakov <dimula73 () gmail ! com>
Date:       2009-09-25 11:48:34
Message-ID: ae32c1ef0909250448u1e9ecc3bv74b4cf281e113657 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


>
> > Already fixed in my patch.
>
> We need to discuss this patch -- given that there's another beta and that
> it
> seems that the proper fix for the projection issues needs this work (or
> else
> would conflict with this work), we might want to apply this in time for the
> beta release.




> And if that makes it possible to enable the pyramid (did I
> understand correctly that the pyramid is dependent on this work?),


It is dependent on the third part of the work - synchronization and
scheduling =)
More than that, after adding synchronization, i'll have to port the
scheduler to kis_view to parallelize pyramid at the higher level, as it's
quite slow now.


> I think we
> should aim for that, too. Using the pyramid will likely fix
> https://bugs.kde.org/show_bug.cgi?id=208141, since that seems an
> out-of-memory
> error caused by the QImage cache.
>

I'm not sure the bug is related to OOM and to projection cache at all. There
are the following reasons:
1) It happens on the side of KisImage, not on the side of KisView2.
2) I can't imagine OOM case on any modern system. 2000px as was said in the
bug report is about 2000x3000*4 (rgba - CS of QImage), that is about 24
megabytes. That is too small to cause any sane OOM.
3) [and most probable] The backtrace is almost identical to
https://bugs.kde.org/show_bug.cgi?id=205210, that is surely NOT OOM bug.



> So -- could you give us a high-level overview of what you've done, and a
> todo-
> list?
>

I've not finished it yet. Hope, i'll finish it today.



-- 
Dmitry Kazakov

[Attachment #5 (text/html)]

<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div \
class="im"> &gt; Already fixed in my patch.<br>
<br>
</div>We need to discuss this patch -- given that there&#39;s another beta and that \
it<br> seems that the proper fix for the projection issues needs this work (or \
else<br> would conflict with this work), we might want to apply this in time for \
the<br> beta release.</blockquote><div><br>  </div><blockquote class="gmail_quote" \
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; \
padding-left: 1ex;"> And if that makes it possible to enable the pyramid (did I<br>

understand correctly that the pyramid is dependent on this \
work?),</blockquote><div><br>It is dependent on the third part of the work - \
synchronization and scheduling =)<br>More than that, after adding synchronization, \
i&#39;ll have to port the scheduler to kis_view to parallelize pyramid at the higher \
level, as it&#39;s quite slow now.<br>  <br></div><blockquote class="gmail_quote" \
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; \
padding-left: 1ex;"> I think we<br> should aim for that, too. Using the pyramid will \
likely fix<br> <a href="https://bugs.kde.org/show_bug.cgi?id=208141" \
target="_blank">https://bugs.kde.org/show_bug.cgi?id=208141</a>, since that seems an \
out-of-memory<br> error caused by the QImage cache.<br></blockquote><div><br>I&#39;m \
not sure the bug is related to OOM and to projection cache at all. There are the \
following reasons:<br>1) It happens on the side of KisImage, not on the side of \
KisView2.<br> 2) I can&#39;t imagine OOM case on any modern system. 2000px as was \
said in the bug report is about 2000x3000*4 (rgba - CS of QImage), that is about 24 \
megabytes. That is too small to cause any sane OOM.<br>3) [and most probable] The \
backtrace is almost identical to <a \
href="https://bugs.kde.org/show_bug.cgi?id=205210">https://bugs.kde.org/show_bug.cgi?id=205210</a>, \
that is surely NOT OOM bug.<br> <br>  </div><blockquote class="gmail_quote" \
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; \
padding-left: 1ex;">

So -- could you give us a high-level overview of what you&#39;ve done, and a \
todo-<br> list?<br></blockquote><div><br>I&#39;ve not finished it yet. Hope, i&#39;ll \
finish it today.<br></div></div><br><br clear="all"><br>-- <br>Dmitry Kazakov<br>



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


[prev in list] [next in list] [prev in thread] [next in thread]