jimp-dev/jimp

Maximum and minimum file size supported

Open

#1,081 opened on Apr 6, 2022

View on GitHub
 (1 comment) (1 reaction) (0 assignees)JavaScript (785 forks)batch import
documentationfile size issuehelp wanted

Repository metrics

Stars
 (13,218 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

With Jimp, I resize images on my local computer and on a live application. When I try to resize images with high dimensions (40k*40k or 100mb), I encounter a few errors. When calculating the total size, 2 different values are taken as a basis. These are the maxMemoryUsageInMB and maxResolutionInMP values. Exceeding any of these values returns an error code:::

maxMemoryUsageInMB::

maxMemory

maxResolutionInMP::

maxResolution

And sometimes when getting some of these errors I can see it coming due to the amount of RAM being exceeded. I guess this is happening because of NodeJS runtime.

nodeJSENV

I have a few questions.

  1. Up to what dimensions can I resize an image?
  2. What dimensions should the pixel pitches (10px10px -- 35000px35000px) of an image I want to resize be?

To test this situation, try to reconstruct a 1800x1800 pixel image with 36000*36000 dimensions. In such a scenario it will return error codes.


Jimp.read('./images/xxxxx.png', (err, image) => {
    if (err) throw err;
    image
      .resize(35000, 35000)
      .write('./images/dune-resize.png'); // save
});```

- Jimp Version: 0.16.1
- Node version: v17.4.0

Contributor guide

Research direction
Investigate the Jimp source code to find the current values of `maxMemoryUsageInMB` and `maxResolutionInMP` constants. They are likely defined in the core library. Check the documentation or the code to determine the exact limits. Then update the documentation to clearly state these limits and consider whether the limits can be made configurable.
Tech stack
javascriptnodejs
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
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.
Clear
Prerequisites
JavaScript basicsNode.js environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80