Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

maxMemoryUsageInMB - dependency of jimp/plugin-resize #144

Open
twofingerrightclick opened this issue Aug 13, 2023 · 0 comments
Open

maxMemoryUsageInMB - dependency of jimp/plugin-resize #144

twofingerrightclick opened this issue Aug 13, 2023 · 0 comments

Comments

@twofingerrightclick
Copy link

twofingerrightclick commented Aug 13, 2023

When trying to get palettes from larger images (like jpegs greater than 5mb) (using node) it appears that jimp/plugin-resize throws a maxMemoryUsageInMB error. The default for jimp decode options is 512mb.

Where can it be configured from node-vibrant to allow working with larger images?

Be neat if the Jimp object could be exposed by Vibrant allowing for configuration like so:
Jimp.decoders['image/jpeg'] = (data: Buffer) => JPEG.decode(data, { maxMemoryUsageInMB: 1024 });

@twofingerrightclick twofingerrightclick changed the title maxMemoryUsageInMB maxMemoryUsageInMB - dependency of jimp/plugin-resize Aug 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants