Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Image picker broken after uploading image with large resolution #2562

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.

Sign up for GitHub

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

Jump to bottom
Open
antontkv opened this issue Feb 15, 2021 · 5 comments
Open

Image picker broken after uploading image with large resolution #2562

antontkv opened this issue Feb 15, 2021 · 5 comments

Comments

@antontkv
Copy link

antontkv commented Feb 15, 2021 •
edited
Loading

Describe the bug
After uploading image with high resolution, 10425x8499 in my case. There is 500 error after upload and image picker breaks. It always shows loading animation. I can fix that by deleting uploaded image from uploads/images/gallery. My guess that bookstack can't create thumbnail of the image, because there is no new image in thumbs-150-150 directory.

Steps To Reproduce
Steps to reproduce the behavior:

  1. Go to Editing the page
  2. Click on Insert an Image
  3. Upload big image
  4. See error

Screenshots
image
image

Your Configuration (please complete the following information):

  • Exact BookStack Version (Found in settings): v0.31.4
  • PHP Version: 7.4
  • Hosting Method (Nginx/Apache/Docker): Bookstack and Apache inside Docker container, reverse proxy with Nginx on the host.

Additional context
I attach image that can help reproduce this issue.
bigimage
@hwcltjn
Copy link

hwcltjn commented Feb 18, 2021

I tested this on the demo, gave me a 502

@critchtionary
Copy link

I get the same issue on Bookstack 0.29.3 with a 7047x4888 image.

@ssddanbrown
Copy link
Member

Just been testing this. This will be due to thumbnail system needing a lot of resources to process the image. If you max the system resources your php process will be killed and you'll get an error.

It'll generally be due to memory availability. This is where a bit of swap space can help if possible in your environment.

@Adrian-at-CrimsonAzure
Copy link

I'm also having this issue with a 32MB map I'm trying to upload which is admittedly absolutely massive.

@S1lander
Copy link

S1lander commented May 8, 2025 •
edited
Loading

Are there any good solutions to this?
Edit: In my case I was able to fix this by setting the "memory_limit" of the PHP Settings in the plesk admin panel to 256M.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@Adrian-at-CrimsonAzure @ssddanbrown @critchtionary @antontkv @S1lander @hwcltjn