-
-
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
Got error "extract_area: bad extract area" when using rotate()
when using 0.31.0
#3352
Closed
3 tasks done
Labels
Milestone
Comments
3 tasks
@lovell Thanks, I confirm the bug is fixed with your commit 👍 |
3 tasks
Re-opening until the fix is published. |
v0.31.1 now available |
@lovell In the latest version(v0.31.1) it is fixed Thanks👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Possible bug
Is this a possible bug in a feature of sharp, unrelated to installation?
npm install sharp
completes without error.node -e "require('sharp')"
completes without error.If you cannot confirm both of these, please open an installation issue instead.
Are you using the latest version of sharp?
sharp
as reported bynpm view sharp dist-tags.latest
.If you cannot confirm this, please upgrade to the latest version and try again before opening an issue.
If you are using another package which depends on a version of
sharp
that is not the latest, please open an issue against that package instead.What is the output of running
npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp
?What are the steps to reproduce?
I've created a short script to reproduce the bug.
Only sharp is used as deps.
I'm using that image for my test (called
20171031_PAR.jpg
in the script).What is the expected behaviour?
It should log the Buffer after rotate + extract + resize.
Instead I got:
If I remove the
rotate()
action (the second one used), everything went fine.The image is 296x382.
The extract info are:
So the box isn't outside the image.
There are no Orientation information in the given image, so the
rotate()
should do nothing (but we are using it because sometimes some images have the Orientation info).Everything run fine on 0.30.7. The bug appears on 0.31.0
The text was updated successfully, but these errors were encountered: