[BUG] OxiCloud container crashes with 137

[dscso]

Description

When uploading folders with a lot of sub-folders I regularly get a the following error:

Unfortunately, there are no previous error messages.

oxicloud-1 exited with code 137 (restarting)
postgres-1  | 2026-05-18 09:16:38.546 UTC [30] LOG:  checkpoint starting: time
oxicloud-1 exited with code 137 (restarting)
oxicloud-1 exited with code 137 (restarting)

I don't think that it is a OOM, since I have 32GB of RAM running on bare-metal.

To Reproduce

Steps to reproduce the behavior:

I am using the standard docker compose file linked in the repository.

To reproduce the error, try uploading a big folder with many sub-folders. e.g. a Rust project containing the target folder.

Expected Behavior

No crash :D

Screenshots

If applicable, add screenshots to help explain your problem.

Environment

• OS: Debian Trixy (latest version) + Docker
• Browser: Firefox 150.0.3
• OxiCloud Version: diocrafts/oxicloud:latest (should be v0.5.6)

[EdouardVanbelle]

137 is usually 128 + 9 meaning you got an OOM kill, you can see this from docker (some limits may be in place)

I just uploaded OxiCloud project via drag & drop including .git assets and target/build without any issue

to check:

% docker inspect <your container id> --format='{{.State.OOMKilled}}'
false

% docker inspect <your container id> --format='Memory: {{.HostConfig.Memory}}, Swap: {{.HostConfig.MemorySwap}}'
Memory: 0, Swap: 0

0 = no limits

[dscso]

Thank you for your help.

Ok, so it crashed but i dont get the OOM error in docker

$ docker inspect oxicloud-oxicloud-1 --format='Memory: {{.HostConfig.Memory}}, Swap: {{.HostConfig.MemorySwap}}'
Memory: 0, Swap: 0
$ docker inspect oxicloud-oxicloud-1 --format='{{.State.OOMKilled}}'
false

I really don't think that it is OOM, since no other container has problems with this and i have 32GB memory and 12GB swap. (5 are used rn).