Just checking to see if anyone has experienced image corruption on an image open
in 2.9.5. This is a Partha build, latest STD (not Color Corrected version).
See attached screen shot.
Just now I finished my work restoring a family image scan. I copied a layer to a
new image, did some more changes (scale, etc.) then saved it. On returning to
the original multiple layers are corrupted beyond recovery ... beyond recovery.
I attempted to us the history to "go back" but that had no positive affect. In
fact, image layers that had be removed, when restored, were also corrupted. Two
of the eight layers are not corrupted, the remaining six are corrupted, two of
them entirely so.
I know ... I know ... 2.9.5 is not a general release build, still
"experimental," but that any version of Gimp should corrupt an image layer is
What should one do in such a situation? I can't replicate this, it just
happened. Report it? To whom?
On Wed, Apr 26, 2017 at 12:11 PM, Michael Schumacher <[hidden email]>
> On 04/25/2017 04:33 AM, gstalnaker wrote:
> > I know ... I know ... 2.9.5 is not a general release build, still
> > "experimental," but that any version of Gimp should corrupt an image
> layer is
> > beyond alarming.
> There is no testing whatsoever done for random builds of the development
> branch at random times - and this is what every 2.9.5 is.
> GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
> gimp-user-list mailing list
> List address: [hidden email] > List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list > List archives: https://mail.gnome.org/archives/gimp-user-list >
This has to do with gegl tiles/cache and how gegl manages memory on
Windows. You set the cache size too high and you have stack issues. It have
nothing to do with "random builds at random times". It's a design issue.
>On Wed, Apr 26, 2017 at 12:11 PM, Michael Schumacher <[hidden email]>
>This has to do with gegl tiles/cache and how gegl manages memory on
>Windows. You set the cache size too high and you have stack issues. It
>nothing to do with "random builds at random times". It's a design
>OP: if you look through the log as I mentioned before you will see a
>bunch of gegl messages.
Thanks Partha. I had in fact changed the tile/cache value in an attempt to
"speed up" your 2.9.5 build. I'm working with 16-bit high DPI scans and adding
multiple layers does affect how quickly Gimp performs operations (I routinely
see 4GiB memory usage on open images). I have renamed the
APPDATA\Roaming\Gimp\2.9 folder to get Gimp to revert to defaults (since I
cannot remember the defaults for cache, etc.).
Warmest regards (and thanks for your Windows Gimp builds!).