RSS/Atom feed Twitter
Site is read-only, email is disabled
  1. Chat
  2. Useful links
  3. Polls

Featured content

GIMP 2.9.5 commit 0c9d76d corrupting image layers

This discussion is connected to the gimp-user-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

5 of 5 messages available
Toggle history

Please log in to manage your subscriptions.
GIMP 2.9.5 commit 0c9d76d corrupting image layers gstalnaker 25 Apr 02:33
  GIMP 2.9.5 commit 0c9d76d corrupting image layers gstalnaker 25 Apr 02:43
  GIMP 2.9.5 commit 0c9d76d corrupting image layers Michael Schumacher 26 Apr 16:11
   GIMP 2.9.5 commit 0c9d76d corrupting image layers Partha Bagchi 26 Apr 16:15
    GIMP 2.9.5 commit 0c9d76d corrupting image layers gstalnaker 26 Apr 23:14
gstalnaker
2017-04-25 02:33:46 UTC (almost 7 years ago)
postings
9

GIMP 2.9.5 commit 0c9d76d corrupting image layers

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 beyond alarming.

What should one do in such a situation? I can't replicate this, it just happened. Report it? To whom?

gstalnaker
2017-04-25 02:43:22 UTC (almost 7 years ago)
postings
9

GIMP 2.9.5 commit 0c9d76d corrupting image layers

Better full screen screenshot, shows layers

Michael Schumacher
2017-04-26 16:11:07 UTC (almost 7 years ago)

GIMP 2.9.5 commit 0c9d76d corrupting image layers

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.

Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD
Partha Bagchi
2017-04-26 16:15:32 UTC (almost 7 years ago)

GIMP 2.9.5 commit 0c9d76d corrupting image layers

On Wed, Apr 26, 2017 at 12:11 PM, Michael Schumacher wrote:

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.

-- Regards,
Michael
GPG: 96A8 B38A 728A 577D 724D 60E5 F855 53EC B36D 4CDD _______________________________________________ gimp-user-list mailing list
List address: gimp-user-list@gnome.org 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.

OP: if you look through the log as I mentioned before you will see a whole bunch of gegl messages.

gstalnaker
2017-04-26 23:14:48 UTC (almost 7 years ago)
postings
9

GIMP 2.9.5 commit 0c9d76d corrupting image layers

On Wed, Apr 26, 2017 at 12:11 PM, Michael Schumacher wrote:
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.

OP: if you look through the log as I mentioned before you will see a whole
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!).