The “Processing” stage of uploading images with a large resolution (larger than 1500 pixels in one dimension) takes extremely long
Steps to reproduce
Using version 5.11.0, but this problem also existed on 5.9.0. It wasn’t always like this, however, the processing stage got slower and slower as time went on.
How to reproduce, try to upload an image with a large resolution. Might only be on my server, though.
Expected behavior
Processing should probably not take that long.
Observed behavior
The actual uploading of the image happens fairly quickly, but then gets seemingly stuck at the processing stage. Sometimes it finishes in around 3-6 minutes, sometimes even longer than 15 minutes where I stopped waiting.
I have tried observing the data directory and the logs when I try to upload images to the server, but the logs only tell about finished jobs from various workers, no error messages, even at debug output level.
The data directory contains the image as expected, but then gets stuck when creating the thumbnail and preview images.
All users on my server are affected, and it seems to only fail at large resolutions, not necessarily at large files. A 3000x2000 JPEG compressed to 80 kB failed to upload, but a binary file with 500 kB was done instantly.
Any ideas on what the issue could be? I’m kinda at a loss.
This (Raspberry Pi 3B+) is an unsupported architecture (arm64). Furthermore, it’s not that great in regards to compute power and memory. Would you be open to trying if you can reproduce the issue on a supported architecture? List is here: https://docs.mattermost.com/install/requirements.html#software-requirements.
I’ve the same issue on my ARM server. We use Mattermost for company internal usage only, is there any way to disable this very slow “processing image”?
Mattermost version: dev-linux-arm-v5.30.1
Storage: local
Everything else has good performances, search, sending message, PDF and others files uploads, etc. Only “Image processing” after uploading an image is crazy slow.
Or if anyone know what I could change in the Mattermost source code to improve the situation?
I’m OK to disable the thumbnail generation or anything which cause this issue .