github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 19:47:47 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #97] Vikunja eating memory with large swap enabled on Raspberry Pi #5963

New Issue
Closed
opened 2026-04-20 16:25:24 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-04-20 16:25:24 -05:00
Owner
Copy Link

Originally created by @DaCHack on GitHub (Nov 27, 2023).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/97

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

Originally created by @DaCHack on GitHub (Nov 27, 2023). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/97 ### 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_
GiteaMirror commented 2026-04-20 16:25:26 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 28, 2023):

Is this about the frontend or API? How are you running Vikunja? Did it use the memory as cache or as actual memory?

<!-- gh-comment-id:1830828797 --> @kolaente commented on GitHub (Nov 28, 2023): Is this about the frontend or API? How are you running Vikunja? Did it use the memory as cache or as actual memory?
GiteaMirror commented 2026-04-20 16:25:27 -05:00
Author
Owner
Copy Link

@DaCHack commented on GitHub (Nov 28, 2023):

I am not sure about frontend or API: Both is running as a docker container on my RPi.
I think in htop it was /app/vikunja/vikunja with multiple threads eating the memory - cannot reproduce right now without breaking the system again.
I run both at latest docker images for arm64 as well as linuxserver/mariadb:10.6.13 in the stack.
It was using actual memory.

<!-- gh-comment-id:1830828801 --> @DaCHack commented on GitHub (Nov 28, 2023): I am not sure about frontend or API: Both is running as a docker container on my RPi. I think in htop it was /app/vikunja/vikunja with multiple threads eating the memory - cannot reproduce right now without breaking the system again. I run both at latest docker images for arm64 as well as linuxserver/mariadb:10.6.13 in the stack. It was using actual memory.
GiteaMirror commented 2026-04-20 16:25:27 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 28, 2023):

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?

<!-- gh-comment-id:1830830156 --> @kolaente commented on GitHub (Nov 28, 2023): 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?
GiteaMirror commented 2026-04-20 16:25:28 -05:00
Author
Owner
Copy Link

@DaCHack commented on GitHub (Nov 28, 2023):

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...).
Also this occurred as first output after boot which might have the same root cause since eventually vikunja was able to connect:

2023-11-27T21:57:04.02580685Z: CRITICAL	▶ migration/Migrate 002 Migration failed: dial tcp: lookup db on 127.0.0.11:53: no such host
2023-11-27T21:57:05.653843555Z: CRITICAL	▶ migration/Migrate 002 Migration failed: dial tcp 172.22.0.4:3306: connect: connection refused
2023-11-27T21:57:07.051648955Z: CRITICAL	▶ migration/Migrate 002 Migration failed: dial tcp 172.22.0.4:3306: connect: connection refused
2023-11-27T21:57:08.666376493Z: INFO	▶ migration/Migrate 052 Ran all migrations successfully.
2023-11-27T21:57:08.670324654Z: INFO	▶ cmd/func25 054 Vikunja version v0.21.0
<!-- gh-comment-id:1830842603 --> @DaCHack commented on GitHub (Nov 28, 2023): 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...). Also this occurred as first output after boot which might have the same root cause since eventually vikunja was able to connect: ``` 2023-11-27T21:57:04.02580685Z: CRITICAL ▶ migration/Migrate 002 Migration failed: dial tcp: lookup db on 127.0.0.11:53: no such host 2023-11-27T21:57:05.653843555Z: CRITICAL ▶ migration/Migrate 002 Migration failed: dial tcp 172.22.0.4:3306: connect: connection refused 2023-11-27T21:57:07.051648955Z: CRITICAL ▶ migration/Migrate 002 Migration failed: dial tcp 172.22.0.4:3306: connect: connection refused 2023-11-27T21:57:08.666376493Z: INFO ▶ migration/Migrate 052 Ran all migrations successfully. 2023-11-27T21:57:08.670324654Z: INFO ▶ cmd/func25 054 Vikunja version v0.21.0 ```
GiteaMirror commented 2026-04-20 16:25:29 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Nov 29, 2023):

Does it always happen or only sometimes?

<!-- gh-comment-id:1831638541 --> @kolaente commented on GitHub (Nov 29, 2023): Does it always happen or only sometimes?
GiteaMirror commented 2026-04-20 16:25:29 -05:00
Author
Owner
Copy Link

@DaCHack commented on GitHub (Nov 29, 2023):

It happened on two consecutive boots

<!-- gh-comment-id:1831644743 --> @DaCHack commented on GitHub (Nov 29, 2023): It happened on two consecutive boots
GiteaMirror commented 2026-04-20 16:25:29 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 1, 2023):

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.

<!-- gh-comment-id:1836202575 --> @kolaente commented on GitHub (Dec 1, 2023): 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.
GiteaMirror commented 2026-04-20 16:25:30 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Sep 13, 2024):

Is this still reproducible?

<!-- gh-comment-id:2348378554 --> @kolaente commented on GitHub (Sep 13, 2024): Is this still reproducible?
GiteaMirror commented 2026-04-20 16:25:30 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jan 21, 2025):

Closing as inactive, please ping or open a new issue with relevant information if you still have this problem.

<!-- gh-comment-id:2605225477 --> @kolaente commented on GitHub (Jan 21, 2025): Closing as inactive, please ping or open a new issue with relevant information if you still have this problem.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#5963
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?