Open florent4014 opened 6 days ago
Yeah, this will happen during the image resize process with large source images. Memory exhaustion limits are a pain to handle, since the app/framework jumps to a shutdown state in out of memory scenarios rather than it being a normal catchable error like logical errors.
We could add specific handling (like we have done elsewhere in a few key areas) but I'm not sure if it's worthwhile to add complexity to logins for this rare edge-case of a scenario.
Another option is to skip certain potentially problematic images, but we don't really know the memory use beforehand.
I guess the less time consuming would be to put a warning in the documentation so that other users can be aware of this issue. Or maybe (i'm no dev) imagine a system, like you said, to ignore profile pics on resolution or size criteria. At least, once you spot the problem, it is easy to fix.
Yeah, that's a good idea. I'll update & tag this issue to focus on adding an comment for the setting in our docs to note/consider this scenario.
I've now updated the ldap docs to add a comment for that option to warn about possible liklihood of additional issues. I'll therefore close this off.
Describe the Bug
Using the linuxserver.io Bookstack docker image, and the docker compose from the documentation (with some LDAP env variables in order to log with LDAP accounts). A user with like a 2MB profile pic will cause HTTP ERROR 500 when logging in to Bookstack app, thus causing the unavailability of the service and requiring a reboot.
I was able to eliminate the problem by adding
memory_limit = 512M
to php-local.ini. Here is the log of the error :Steps to Reproduce
Expected Behaviour
Being able to log without causing critical behaviour
Screenshots or Additional Context
No response
Browser Details
BRAVE Version 1.70.119 Chromium: 129.0.6668.70 (64 bits)
Exact BookStack Version
BookStack v24.05.4