-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Input image exceeds pixel limit #1381
Comments
Hello, did you see limitInputPixels? |
Yes I know that exists. Removing/widening the limit means you may suffer from DoS, which is a more serious problem. So that's not a solution. |
And please not edit the title to alter the purpose of this issue. The lack of the error handling is the point. |
Are you referring to Node worker threads? If so, please see #1297 |
No, I'm referring to the libuv tasks you spawn. |
Thanks for confirming, please can you provide a code sample that fails in the manner you describe? |
After some debugging, I found that |
@ishitatsuyuki can you please share a way you fixed it? |
Sorry I don't remember anything from 4 years ago. You might want to fiddle with ts-node as the past me said. |
libvips is designed to handle any malicious input without crashing, and the same should applies to sharp as well.
Unfortunately, you don't seem to propagate the errors detected in the worker thread.
I see things like:
and Node just dies with exit code 1.
The text was updated successfully, but these errors were encountered: