On Wed, 2 May 2018 09:16:46 -0400 Partha Bagchi <partha1b@xxxxxxxxx> wrote: > > It started again after the final release. It was not there in RC1. So it only started at some point after RC1, but before 2.10? (days? weeks?) I'm trying of think of things that changed during that time that might have caused this. Did you change something on your end? > > This may be a affect of the transition from gegl 0.3 to 0.4? Not likely, especially if it already happened before 2.10. The 0.4 switch happened right before the release. > > In the past, it was related to complicated images with high > > resolution and usually setting GEGL_CACHE_SIZE to 2048 or > > thereabouts fixed it. Now, it does not. This sounds like you might have ran out of cache and swap space, in which case you'd start getting write errors. These are read errors, which are much more surprising. > I did the following. I set the following environment variables: > GEGL_SWAP=C:\Users\partha\AppData\Local\Temp\gegl > GIMP_NO_PAINT_THREAD="Y" > > It didn't make any difference. Ok, so it's not the separate paint thread. That's a good thing :) What's the rest of your GEGL setup like? Are you using any other environment variables? What's the thread count? > Matter of fact, GEGL_SWAP was unused. > So, I removed it and reran GIMP. No change. Do you mean that GEGL wasn't using the swap? Can you use the dashboard to see if anything "interesting" is going on while this happens? Is the cache full? Is the swap nearly full? Do the reported cache/swap size limits make sense? -- Ell _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list@xxxxxxxxx List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
