High RAM usage with System Health Monitoring
Hello,
I just added the System Health Monitoring widget to Homarr and I am experiencing a constantly-increasing RAM usage of my qBittorrent docker container (which is running in the same docker stack as Homarr) to the point where I am running into a OOM issue after about an hour. This only happens when the Homarr webpage is selected. If I go on any other tab, the RAM just stops increasing (without going down) and starts increasing again as soon as I go back to the Homarr tab. How can I solve this problem?
Thank you for you help.
6 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
The hypervisor I am using is Proxmox and Homarr is running in a docker container alongside qBittorrent. Homarr version is latest.
homarr | API response for /api/trpc/download.get?batch=1&input=%7B%220%22%3A%7B%22json%22%3A%7B%22configName%22%3A%22default%22%7D%7D%7D exceeds 4MB. API Routes are meant to respond quickly. https://nextjs.org/docs/messages/api-routes-response-size-limit
This message is being spammed in the logs when the System Health Monitoring widget is running, so I am guessing this is related to my issue. I am however not sure how to fix this.
As a side note, I am using Firefox on my PC to access Homarr.You could try changing the
responseLimit in your configIt seems there was a strange coincidence because the widget causing the RAM issue was actually the Torrent widget, which never caused trouble before. I will have to look into that because my troubleshooting was all wrong. Apologies for the confusion.
So this is 0.15.10, right?
Correct
It appears the issue is caused by my qBittorrent instance having multiple thousand torrents in it, which is hardly manageable by Homarr.