-
-
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
Issues during size scaling of images (mostly occurs with jpeg) #403
Comments
Hello, this is an error I've not seen before. The Could |
There are quite a few other modules with similar reports for this problem https://github.com/search?o=desc&q=Assertion+failed%3A+%28loop-%3Ewatchers%5Bw-%3Efd%5D+%3D%3D+w%29%2C+function+uv__io_stop&s=created&type=Issues&utf8=%E2%9C%93 |
If this is caused by libvips writing to sharp doesn't directly use any of libuv's file handling logic so my best guess remains that another module is doing so - if not MariaDB then perhaps a logging or monitoring library that's trying to watch |
Thank you for the response! I've looked at our logs, and it turns out the assertion error doesn't always happen in conjunction with a read error, in fact, most of the time the read error happens with an assertion error. The process continues nontheless, without reporting an error, and that's our primary concern. |
Are you able to set the |
Were you able to solve this? If so, are you able to share details in case others have the same problem? Thanks! |
Thank you for trying to help me. I was not able to solve it, and I had to replace the library as it caused a sigabort (I think libvips -> imagemagick), which crashed my application (forever detected the sigabort and killed the process). If I get the time to look into the cause, I will, but for now I must leave you without an answer. |
I have a hard time describing the issue, so I've attached an example instead:
As you can see, it seems an issue occurs while scaling jpeg images, however it's not a consistent issue, and libvips throws warnings when it happens. For example
If I can listen for these warnings, that would be sufficient.
Here is the original image:
It seems to occur in about 0.6% of scaling jobs, for reference here is the code I use to scale the image (edited for brevity):
The text was updated successfully, but these errors were encountered: