koffice/krita/image

[Dmitry Kazakov]

>
> > 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kimageshop/attachments/20090925/32357c05/attachment.htm