jimp-dev/jimp

Can't Resize GIF

Open

#948 opened on Oct 3, 2020

View on GitHub
 (1 comment) (0 reactions) (0 assignees)JavaScript (13,218 stars) (785 forks)batch import
GIF Supportbughelp wanted

Description

If I try to resize an image to a big value like 5000 (both for width and height) my program will load for some time and then it will just exit with no errors seen in console.

Expected Behavior

It should resize the image correctly and I should get a image that is 5000x5000

Current Behavior

Doesn't work and the program just exists.

Failure Information (for bugs)

Steps to Reproduce

  • Create an image
  • Try to resize it to 5000x5000
  • Watch it exit silently

Screenshots

Context

Well I'm creating a image server and I want to be able to resize the images.

  • Jimp Version: ^0.16.1
  • Operating System: Linux
  • Node version: v12.18.3

Failure Logs

None

Contributor guide

Tech stack
javascriptnodejs
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic JavaScriptNode.js environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Investigate why resizing a GIF to large dimensions (e.g., 5000x5000) causes the Jimp program to exit silently without an error. This may be due to memory exhaustion or a bug in the GIF plugin's resize handling. Look into Jimp's source code for the resize method and the GIF plugin (jimp gif). Check for similar issues or commits related to large GIF resizing. Reproduce with a sample GIF and test with smaller sizes to narrow down the threshold. Consider adding error handling or logging to identify the failure point.