On Wed, May 2, 2018 at 3:49 PM, Ell <ell...@yahoo.com> wrote:

> On Wed, 2 May 2018 15:04:01 -0400
> Partha Bagchi <parth...@gmail.com> wrote:
>
> > On Wed, May 2, 2018 at 2:18 PM, Øyvind Kolås <pip...@gimp.org> wrote:
> >
> > >
> > > GEGL has stopped enabling opencl by defult now, since GEGL-0.3.24 of
> > > 2017-11-24 it no longer being enabled by default since it relies on
> > > good results from the varying quality different opencl
> > > implementations,.. may also have generic race conditions resulting
> > > from new code not manifest during regular testing either, so trying
> > > without OpenCL enabled.
> > >
> > > /pippin
> > >
> > I removed the above environment variable but no change with my 36MP
> > image. The moment I put the brush on the screen, I get the error
> > messages above.
> >
> > Then I experimented with some more pictures and it seems to be
> > related to the size of the image.
> >
> > I open a 1 megabyte (MB), and 4MB image and no error. Then I open a
> > 74MB image without error. But when I opened an 300 MB Tiff, I started
> > getting the error.
> >
> > I repeated the experiment with GEGL_CACHE_SIZE = 2048 with the same
> > result.
> >
> > For all all images, I first fit to window > duplicate layer > paint on
> > duplicate layer.
>
> My guess is that this is related to the zoom level (being <= 50%),
> rather than to the size of the image per se.  There were some changes
> to the mipmapped tiles code recently, and there was indeed a subtle bug
> there.  GEGL commit 3557811a5527bccbfef2006046a05047b6edd480 should fix
> it.
>
You may be right! I changed the zoom level to 51% and didn't see that
error. I'll have to experiment some more of course.

For GEGL, I'll git pull and rebuild to see what the effect is.

>
> Note that the actual bug was the swap being used in the first place.
> I'm still not sure why you're getting read errors, though.  Since the
> swap shouldn't be used anymore (in this particular case) after the
> above commit, the errors will probably go away, but the issue causing
> them might still be there.  I'd try to set a very low cache size, in
> order to force the swap to become very active, and see if you're
> getting any more errors.
>
I should do this after update gegl and gimp, correct?

>
> --
> Ell
>
Thanks!
Partha
_______________________________________________
gimp-developer-list mailing list
List address:    gimp-developer-list@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-list

Reply via email to