Gimp 2.8 "has stoppped working" on WIndows

Hello.

I'm using Gimp 2.8 and when I do: "File/Open as layers" Gimp stops and I
see the error "GNU Image Manipulation Program has stopped working".
This heappens after about 60 layers. I increased the max size for a
image from "Edit/Preferences" Environment - "Maximum new image size" to
12G but this was of no help.I have enough RAM on my computer.

Gimp 2.8 "has stoppped working" on WIndows

How big are the images you are trying to load?

On 03/12/18 13:25, Sterpu Victor wrote:

Hello.

I'm using Gimp 2.8 and when I do: "File/Open as layers" Gimp stops and
I see the error "GNU Image Manipulation Program has stopped working".
This heappens after about 60 layers. I increased the max size for a
image from "Edit/Preferences" Environment - "Maximum new image size"
to 12G but this was of no help.I have enough RAM on my computer.

Gimp 2.8 "has stoppped working" on WIndows

Images are 5456x362 and I was tryng to batch crop all of them with a
Gimp script.I have 800 of these images and Gimp stops at 60.
I know this is not very efficient as Gimp loads all layers in memory but
I have enough RAM.

I'm using Gimp 2.8 and when I do: "File/Open as layers" Gimp stops and
I see the error "GNU Image Manipulation Program has stopped working".
This heappens after about 60 layers. I increased the max size for a
image from "Edit/Preferences" Environment - "Maximum new image size"
to 12G but this was of no help.I have enough RAM on my computer.

Gimp 2.8 "has stoppped working" on WIndows

On 03/12/18 15:31, Sterpu Victor wrote:

Images are 5456x362 and I was tryng to batch crop all of them with a
Gimp script.I have 800 of these images and Gimp stops at 60.
I know this is not very efficient as Gimp loads all layers in memory
but I have enough RAM.

Strange size, or is it missing a digit and is 5456x3632 from a Sony camera?

If this is the case, Gimp uses about 65MB/layer, so at 60 layers you are
hitting a 4GB limit. Are you using a 32-bit version of Gimp?

Images are 5456x362 and I was tryng to batch crop all of them with a
Gimp script.I have 800 of these images and Gimp stops at 60.
I know this is not very efficient as Gimp loads all layers in memory
but I have enough RAM.

Strange size, or is it missing a digit and is 5456x3632 from a Sony
camera?

If this is the case, Gimp uses about 65MB/layer, so at 60 layers you
are hitting a 4GB limit. Are you using a 32-bit version of Gimp?

Sorry, I missed the image size, the size is 5456x3632(from a Sony
camera)Gimp is on 64 bits("C:\Program Files\GIMP 2\bin\gimp-2.8.exe").
CPU is a 64 bits, I7 series, Windows is 10 Pro on 64 bits.
I copied here first 67 images: http://cc123.caido.ro/test.zip

Gimp 2.8 "has stoppped working" on WIndows

Sorry, I missed the image size, the size is 5456x3632(from a Sony camera)
Gimp is on 64 bits("C:\Program Files\GIMP 2\bin\gimp-2.8.exe").
CPU is a 64 bits, I7 series, Windows is 10 Pro on 64 bits.
I copied here first 67 images: http://cc123.caido.ro/test.zip

I can load 71 images (5472x3648) just fine and Gimp's memore indicator
is at 4.6GB.

What is you tile cache size set to (see Edit>Preferences>Environment)?
This is the max RAM Gimp will use, and beyond this it performs its own
swapping to disk, which reduces performance dramatically. If your I/O
rate increases around the 60th image, you may have an explanation. In
your case with a HDD it could be especially bad since the image loader
would be reading some part of the disk while the tiles would be written
to the swap file somewhere else on the disk.

Sorry, I missed the image size, the size is 5456x3632(from a Sony
camera)Gimp is on 64 bits("C:\Program Files\GIMP 2\bin\gimp-2.8.exe").
CPU is a 64 bits, I7 series, Windows is 10 Pro on 64 bits.
I copied here first 67 images: http://cc123.caido.ro/test.zip

I can load 71 images (5472x3648) just fine and Gimp's memore indicator
is at 4.6GB.

What is you tile cache size set to (see Edit>Preferences>Environment)?
This is the max RAM Gimp will use, and beyond this it performs its own
swapping to disk, which reduces performance dramatically. If your I/O
rate increases around the 60th image, you may have an explanation. In
your case with a HDD it could be especially bad since the image loader
would be reading some part of the disk while the tiles would be
written to the swap file somewhere else on the disk.