-
-
Notifications
You must be signed in to change notification settings - Fork 609
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
imgproxy ate all free space on drive #13
Comments
That's, actually, not totally correct. libvips does use your drive space to store decoded images that are too big to be securely stored in RAM. As you noticed correctly, If you allow processing such big images on the fly, you should know the cost of it. They will either use a lot of your memory or drive space. |
This makes sense, but there are some problems:
|
Btw, could you share the image which you use for testing? |
Sure, here it is: https://en.wikipedia.org/wiki/File:0000140_Wat_Arun_01.jpg |
Results with the current master:
So, everything is definitely much better ) |
Nice, thanks for testing! |
I'm trying to process 7360 × 4912 pixels image and after each request, the free space on the system drive is reduced by 104 MB. This doesn't stop until all space is gone.
By the way,
7360*4912*3
≈ 104 MB.The text was updated successfully, but these errors were encountered: