[GH-ISSUE #772] Server crash if an entry redirecting to a large file exists #531

New issue

Closed

opened 2026-03-03 01:30:14 +03:00 by kerem · 1 comment

kerem commented

2026-03-03 01:30:14 +03:00

Owner

Originally created by @aschereT on GitHub (Dec 18, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/772

Subject of the issue

Bitwarden server crashing when opening the Web Vault. The server's MEM usage would quickly skyrocket to several gigabytes, causing the server to run out of memory and crash.
I suspected one of my login items was causing this. I managed to narrow it down to a login with the url http://code.runnable.com, which redirects to a 1GB file. top in the container shows all the threads trying to download at the same time?

Let me know if there's anything else needed, or if something I forgot to add/was wrong!

Your environment

Bitwarden_rs version: 2.12.1
Install method: Docker image / Docker-compose
Clients used: Wb Vault
Reverse proxy and version: nginx (https://hub.docker.com/r/linuxserver/letsencrypt:latest as of today)
Version of mysql/postgresql: Default SQLite
Other relevant information:
Server has CPU: Pentium G3258 and 7GB of RAM. Ubuntu Server 19.10.

Steps to reproduce

Spin up bitwarden container
Open an ssh session into the server and run docker stats
Open an ssh session into the server and run docker exec -it bitwarden sh, then run top
Open an ssh session into the server and be ready to run docker kill bitwarden
Login to the web vault
Add a login entry with http://code.runnable.com as the URL
Watch bitwarden MEM usage rocket to the moon
Kill it

Expected behaviour

Bitwarden uses MEM responsibly, and not try to download a 1GB file to memory with all of its threads.

Actual behaviour

Bitwarden takes over all the MEM and kills the server

Relevant logs

Image taken seconds before server goes MIA

Originally created by @aschereT on GitHub (Dec 18, 2019). Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/772  ### Subject of the issue Bitwarden server crashing when opening the Web Vault. The server's `MEM` usage would quickly skyrocket to several gigabytes, causing the server to run out of memory and crash. I suspected one of my login items was causing this. I managed to narrow it down to a login with the url `http://code.runnable.com`, which redirects to a 1GB file. top in the container shows all the threads trying to download at the same time? Let me know if there's anything else needed, or if something I forgot to add/was wrong! ### Your environment * Bitwarden_rs version: 2.12.1 * Install method: Docker image / Docker-compose * Clients used: Wb Vault * Reverse proxy and version: nginx (https://hub.docker.com/r/linuxserver/letsencrypt:latest as of today) * Version of mysql/postgresql: Default SQLite * Other relevant information: Server has CPU: Pentium G3258 and 7GB of RAM. Ubuntu Server 19.10. ### Steps to reproduce  1. Spin up bitwarden container 2. Open an ssh session into the server and run `docker stats` 3. Open an ssh session into the server and run `docker exec -it bitwarden sh`, then run top 4. Open an ssh session into the server and be ready to run `docker kill bitwarden` 5. Login to the web vault 6. Add a login entry with `http://code.runnable.com` as the URL 7. Watch bitwarden `MEM` usage rocket to the moon 8. Kill it ### Expected behaviour Bitwarden uses `MEM` responsibly, and not try to download a 1GB file to memory with all of its threads. ### Actual behaviour Bitwarden takes over all the `MEM` and kills the server ### Relevant logs  ![Screenshot from 2019-12-18 13-26-56](https://user-images.githubusercontent.com/12742227/71124622-1ccb7f00-219a-11ea-9dea-16a48c410740.png) <img width="1440" alt="Image taken seconds before server goes MIA" src="https://user-images.githubusercontent.com/12742227/71124993-ee9a6f00-219a-11ea-8580-c92d8dc9eee1.png">

kerem closed this issue

2026-03-03 01:30:15 +03:00

kerem commented

2026-03-03 01:30:16 +03:00

Author

Owner

@dani-garcia commented on GitHub (Dec 18, 2019):

Very interesting case! I never expected a URL to point to a huge file like that. I limited it now to 512 KB which should be more than enough to download any HTML page. (github.com/dani-garcia/bitwarden_rs@2545469713)

The images are being built now, and should be all finished by tomorrow. Thanks!

@dani-garcia commented on GitHub (Dec 18, 2019): Very interesting case! I never expected a URL to point to a huge file like that. I limited it now to 512 KB which should be more than enough to download any HTML page. (https://github.com/dani-garcia/bitwarden_rs/commit/25454697130a2bcbb76f7f29cdf8d1d382de96c7) The images are being built now, and should be all finished by tomorrow. Thanks!