### ImageMagick version

7.1.0-50 beta Q16-HDRI x86_64 20489

### Operating system

Linux

### Operating system, version and so on

Docker with alpine (node:16.17.1-alpine); also tried with alpine node:18.16.0-alpine

### Description

Hello,

One of our users uploaded a gif that seems to be causing a sigkill when we use 'convert' on it. Specifically:
```convert "${pathToFile}" -channel a -separate -scale 1x1! -format "%[fx:u]" info:```.

<img width="648" alt="imagemagick-sigkill" src="https://github.com/ImageMagick/ImageMagick/assets/3720818/f20cf4a7-068c-4008-8c0c-088b5b6c35b7">

We are using **docker**, with **alpine (node:16.17.1-alpine)**. The docker itself runs on top of Ubuntu 20.04.4 LTS (GNU/Linux 5.13.0-1021-azure x86_64).

I noticed the servers are using 7.1.0-50 beta Q16-HDRI x86_64 20489, but the same happens with the following:
- 7.0.11.14-r1
- 7.1.0.16-r0
- 7.1.0.50-r0
- 7.1.0.62-r0
- 7.1.1.10-r0

Cannot try with the edge ([7.1.1.10-r1](https://pkgs.alpinelinux.org/flag/community/imagemagick/7.1.1.10-r1)) because of some qemu: uncaught target signal 11 (Segmentation fault) - core dumped.

If I run locally, without docker, using my mac with imagemagick ImageMagick 7.1.0-8 Q16-HDRI arm 2021-09-18.

Is it a version or arch issue? or a combination of both? other gifs seem to work fine. Not sure what's causing this one. Perhaps the size of the gif being close to 100mb?


### Steps to Reproduce

Dockerfile:
```
FROM node:16.17.1-alpine as production
# same result with node:18.16.0-alpine
ARG NODE_ENV=production
ENV NODE_ENV=${NODE_ENV}

RUN apk add ffmpeg graphicsmagick imagemagick

WORKDIR /app

COPY package*.json ./

...

RUN npm ci --production

COPY ./dist ./dist

CMD ["npm", "run", "start:prod"]
```

And then enter the docker shell (docker exec -it <container> sh) and run the 'convert' or 'identify' command directly, or through node js:
```
import { exec } from 'child_process';
import { promisify } from 'util';

const execAsync = promisify(exec);

async function callCliCommand(cmd: string) {
  return await execAsync(cmd);
}

const cmd = `convert "${pathToFile}" -channel a -separate -scale 1x1! -format "%[fx:u]" info:`;
const cmdResult = await callCliCommand(cmd);
```

### Images

https://drive.google.com/file/d/1injDmL2b6hUfGo5RE5dOMkrsxLY_hKLa/view

(too big--even zipped--to upload here)
Specific 90+ Mb gif sigkill during 'convert'
This is a GitHub Issue
repo:ImageMagick
owner:ImageMagick
Title : Specific 90+ Mb gif sigkill during 'convert'
Issue date:

--- start body ---
### ImageMagick version

7.1.0-50 beta Q16-HDRI x86_64 20489

### Operating system

Linux

### Operating system, version and so on

Docker with alpine (node:16.17.1-alpine); also tried with alpine node:18.16.0-alpine

### Description

Hello,

One of our users uploaded a gif that seems to be causing a sigkill when we use 'convert' on it. Specifically:
```convert "${pathToFile}" -channel a -separate -scale 1x1! -format "%[fx:u]" info:```.

<img width="648" alt="imagemagick-sigkill" src="https://github.com/ImageMagick/ImageMagick/assets/3720818/f20cf4a7-068c-4008-8c0c-088b5b6c35b7">

We are using **docker**, with **alpine (node:16.17.1-alpine)**. The docker itself runs on top of Ubuntu 20.04.4 LTS (GNU/Linux 5.13.0-1021-azure x86_64).

I noticed the servers are using 7.1.0-50 beta Q16-HDRI x86_64 20489, but the same happens with the following:
- 7.0.11.14-r1
- 7.1.0.16-r0
- 7.1.0.50-r0
- 7.1.0.62-r0
- 7.1.1.10-r0

Cannot try with the edge ([7.1.1.10-r1](https://pkgs.alpinelinux.org/flag/community/imagemagick/7.1.1.10-r1)) because of some qemu: uncaught target signal 11 (Segmentation fault) - core dumped.

If I run locally, without docker, using my mac with imagemagick ImageMagick 7.1.0-8 Q16-HDRI arm 2021-09-18.

Is it a version or arch issue? or a combination of both? other gifs seem to work fine. Not sure what's causing this one. Perhaps the size of the gif being close to 100mb?


### Steps to Reproduce

Dockerfile:
```
FROM node:16.17.1-alpine as production
# same result with node:18.16.0-alpine
ARG NODE_ENV=production
ENV NODE_ENV=${NODE_ENV}

RUN apk add ffmpeg graphicsmagick imagemagick

WORKDIR /app

COPY package*.json ./

...

RUN npm ci --production

COPY ./dist ./dist

CMD ["npm", "run", "start:prod"]
```

And then enter the docker shell (docker exec -it <container> sh) and run the 'convert' or 'identify' command directly, or through node js:
```
import { exec } from 'child_process';
import { promisify } from 'util';

const execAsync = promisify(exec);

async function callCliCommand(cmd: string) {
  return await execAsync(cmd);
}

const cmd = `convert "${pathToFile}" -channel a -separate -scale 1x1! -format "%[fx:u]" info:`;
const cmdResult = await callCliCommand(cmd);
```

### Images

https://drive.google.com/file/d/1injDmL2b6hUfGo5RE5dOMkrsxLY_hKLa/view

(too big--even zipped--to upload here)
--- end body ---

The issue describes a potential Denial of Service (DoS) vulnerability in ImageMagick when processing large GIF files, which can lead to a segmentation fault (SIGKILL) during the 'convert' operation. This behavior may allow an attacker to crash the application by uploading a specially crafted large GIF file, causing resource exhaustion or instability in the service.