Skip to content
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

Uploaded images are rendered with gray areas #276

Open
1 of 3 tasks
emmavanderhaeghen opened this issue Nov 19, 2024 · 1 comment
Open
1 of 3 tasks

Uploaded images are rendered with gray areas #276

emmavanderhaeghen opened this issue Nov 19, 2024 · 1 comment

Comments

@emmavanderhaeghen
Copy link

emmavanderhaeghen commented Nov 19, 2024

I'm submitting a...

  • bug report
  • feature request
  • general question

Description

Expected Behavior:
Uploaded images should be processed and rendered fully without any gray areas.

Actual Behavior:
Some images occasionally render with a gray block (see attached screenshots), appearing as if the rendering process was incomplete. I adviced my client to upload images who are less then 1MB for better performance, but some of the images they want to use are above 1MB.

Screenshot 2024-11-19 at 16 57 12
Screenshot 2024-11-19 at 16 57 18
Screenshot 2024-11-19 at 16 57 28
Screenshot 2024-11-19 at 16 58 08

How can it be avoided that these gray areas appear when uploading new images? Could the problem be the file size of the images? Or could the problem be somewhere else?

Additional info

  • Imager version & edition: 4.2.3 PRO
  • Imager transformer: craft
  • Craft version: 4.5.6.1 PRO
  • PHP version: 8.2.25
  • Image driver & version: GD 8.2.25
@aelvan
Copy link
Contributor

aelvan commented Nov 22, 2024

This is almost certainly due to PHP/connections timing out one way or another. Imager adds as much safeguards as it can, but some scenarios can't be mitigated. Are you using external storages, ie AWS S3, DigitalOcean Spaces, or similar?

The only advice I can give is to increase timeout limits, most notably max_execution_time in PHP, request_terminate_timeout if you're using PHP-FPM with nginx, and also fastcgi_read_timeout when using nginx. This issue is probably not due to memory constraints, but there's a slim chance that increasing memory limits also could be beneficial. Also, generate as many transforms as possible up front, as long as you have a working queue running, it's less likely to cause these kinds of timeouts.

Hope this helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants