-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
[Bug]: cron fails because of gd-webp #45531
Comments
sigh (not directed at you; just frustrated at these preview processing matters). #38364 should address this too since I think you're only hitting that code path due to the fallback in place: server/lib/private/Blurhash/Listener/GenerateBlurhashMetadata.php Lines 88 to 97 in 36ae775
Thanks for reporting. I'll try to get that PR in. It's been on the back burner for awhile. |
No problem, i understand. Is there maybe a setting where we can disable all previews and prevent these errors for now? |
The cron issue seems to have fixed itself, but should we keep this issue open in case anything else happens? |
Bug description
Animated webp are not supported and will generate
gd-webp cannot allocate temporary buffer at /var/www/html/lib/private/legacy/OC_Image.php#751
as described in #37263 but this will also prevent cron from running successfully.I have also tried to disable image previews but that didn't seem to help, you can see the line
"enable_previews": false,
in the config.Steps to reproduce
gd-webp cannot allocate temporary buffer
error logExpected behavior
Let cron carry on like normal
Installation method
Community Docker image
Nextcloud Server version
29
Operating system
None
PHP engine version
None
Web server
None
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Fresh Nextcloud Server install
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
No response
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: