-
-
Notifications
You must be signed in to change notification settings - Fork 51
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.
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
Vikunja eating memory with large swap enabled on Raspberry Pi #97
Comments
Is this about the frontend or API? How are you running Vikunja? Did it use the memory as cache or as actual memory? |
I am not sure about frontend or API: Both is running as a docker container on my RPi. |
Sounds like a problem of the api. Were you doing anything during that time? Did it happen at a specific time? Anything in the logs when it happened? |
No, I was not doing anything yet. I occured right after the reboot to enable swap and did not stop until I stopped the containers for vikunja. The logs show a couple of timeouts from database connections that I assume stem from the large latency when the system was memory flooded (while I do not get why it was slow despite no swap was used...).
|
Does it always happen or only sometimes? |
It happened on two consecutive boots |
Not sure how to reproduce this - I've never noticed this on any of the instances I run myself. Please report back if you can pin it down to something more clearly. I'll keep an eye on it as well. |
Description
Running Raspberry Pi OS on a RPi4 2GB
Vikunja runs fine under default settings with less than 5% memory usage.
When enabling 2GB of swap for another app I noticed that suddenly Vikunja took 40% of physical memory filling up the entire physical memory. Swap file was not used by the system yet due to swappiness at 0. Still, system got extremely slow so I need to revert back to default settings and disable swap to have all service available to the users again.
Vikunja Frontend Version
0.21.0
Vikunja API Version
0.21.0
Browser and version
Edge
Can you reproduce the bug on the Vikunja demo site?
No
Screenshots
No response
The text was updated successfully, but these errors were encountered: