docker-jdownloader-2 icon indicating copy to clipboard operation
docker-jdownloader-2 copied to clipboard

Published 20 hours ago • verified publisher icon jlesage

jdownloader cpu increase with container running time?

Open oystermon opened this issue 2 years ago • 4 comments

Hi for some reason my jdownloader2 container's idle CPU usage seems to increase over time, e.g. rises from 0-2% to 10% over 6 days.

Restarting the container fixes the issue, but it slowly increases over time again.

I couldn't see warnings/errors in the logs, and haven't had any issues with MakeMKV and handbrake (which i assume are quite similar)

Running jdownloader2 as a docker container on openmediavault (debian) on an i3-6100T

Let me know if there's any troubleshooting steps I can do.

glances

oystermon avatar Dec 04 '22 14:12 oystermon

same here. This docker container always has the highest idle cpu usage. (process jdownloader.jar)

fightforlife avatar Dec 29 '22 11:12 fightforlife

If the CPU usage is caused by jdownloader.jar, I think it's worth checking/asking on the JDownloader forum. I'm not sure the behaviour you describe is caused by the fact that JD is running in a container.

jlesage avatar Dec 29 '22 22:12 jlesage

Same behaviour for me, with very visible linear cpu-usage increase, see this netdata graph (drop is because of container restart). The container was mostly idle without any downloads. jdo_cpu

Even if this is actually an upstream issue, I would vote to at least mention this issue in the readme and release-notes as a known limitation if nothing else.

Konsonanz avatar Jan 23 '23 18:01 Konsonanz

As much work as @jlesage putted into the GUI, which is btw amazing... I have to say that jdownloader headless is a more headachefree experience, im sorry but in headless mode i have not a single issue with the container, while i had some troubles in the first days in the GUI mode...

  • like suddenly filling up all memory of the LXC Container and using 100% cpu, which made the whole LXC Container unresponsive/Frozen almost. (I run Docker inside an LXC Container on Proxmox)
  • Crashing, etc...

Switched to headless some days ago and all my issues went away, so in my opinion, as nice as the GUI is, its not worth it. And that has nothing with @jlesage todo, it's simply jdownloader itself, jdownloader is unreliable simply. I mean it can be the case because of a virtual x11 desktop + novnc, but i doubt it. I think jdownloader is simply buggy and written on a slow language anyway that i don't like (java)

EDIT: Btw, headless takes here for me 750mb less memory and around 0.5% less cpu usage. So there is a benefit either. Cheers

Ramalama2 avatar Jun 17 '23 23:06 Ramalama2