-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
High memory usage/leak #174
Comments
I think this is the purpose of the -Xmx100m argument in the readme which you aren't using - to limit the program's memory usage. |
The -Xmx100 argument would indeed help, but your top is still worrying. I'll keep this thread open so that I can try this out myself when I'm back at a computer (I'll been afk for a while, perhaps until October) |
Thank you for both your replies. I am using Docker in Unraid. Where should I be able to enter this argument? CMD=("/app/bin/watchlistarr") JAVA_OPTS=(-Xmx100m) exec "${CMD[@]}" "${JAVA_OPTS[@]}" |
Same, Unraid reporting container using 3.2gb dedotated wam |
seems like the update may have fixed it? |
It hasn't fixed mine unfortunately. Still using lots of RAM. |
Thanks all for your comments, the latest build wouldn't have fixed this issue, as this looks like a real memory leak. Out of curiosity, is everybody here who's getting the issue running on a java version that's less than version 21? (If you're running via docker, then the answer is yes I'm using version 11). |
Docker, but no idea what Java version |
Also getting this issue, Docker on Unraid. 4GB's of RAM taken up but I've turned it off for now. |
Windows. Exception in thread "io-compute-0" java.lang.OutOfMemoryError: Java heap space |
Same issue here. Good to know the memory limit command and I’ll check it out later. I’m using Docker for windows |
Hi. Same for me when running Watchlistarr in a docker container on Unraid. The RAM usage is at 3GB but ramps up over time. Now sitting at 6GB. |
This is Still an issue with docker on Unraid. |
For all of you experiencing this on Unraid, adding this flag in the extra parameters field of the container will solve the issue: It is now using about 400MB for over 2 weeks without noticing any impact on performance. |
This process is taking over 20% of the RAM:
/usr/local/openjdk-11/bin/java -Dsonarr.apikey=apikey -Dsonarr.baseUrl=http://192.168.2.150:8989/ -Dsonarr.qualityProfile=WEB-DL1080p -Dradarr.api can't read the rest of the process
Killing Watchlistarr (on Unraid) fixed it.
The text was updated successfully, but these errors were encountered: