High CPU use after jobber test

[samuelallan72]

Running jobber 1.4.3 on archlinux, built from pkgbuild.

Normal execution is fine, but when I run jobber test <any job>, cpu use of the jobberrunner for my user leaps to around 100%. i run jobber test ... again, and cpu jumps to 200%, and so on up to about 450% (this is as reported by htop; I'm assuming it's because multi cores?). Some kind of resource leak?

[D-K-E]

Same issue, I downloaded debian release. jobber -v outputs Jobber 1.4.3

[dshearer]

Oh man... hashtag lame.

…

On May 29, 2020, at 6:46 AM, Samuel Walladge ***@***.***> wrote:  Running jobber 1.4.3 on archlinux, built from pkgbuild. Normal execution is fine, but when I run jobber test <any job>, cpu use of the jobberrunner for my user leaps to around 100%. i run jobber test ... again, and cpu jumps to 200%, and so on up to about 450% (this is as reported by htop; I'm assuming it's because multi cores?). Some kind of resource leak? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[MCOfficer]

I'm also seeing constantly high CPU load without any jobs running. Just to show off the severity, this is my netdata CPU graph:

• The drop at 20:55:20 is a systemctl stop jobber
• The short peak at 20:57:17 a systemctl start jobber
• At 20:57:40 i jobber test a resource-intensive job (7z compression)
• At 20:48:40 the job finished, but a certain amount of CPU load remains. Unless i restart jobber, the load will stay like this (or higher) indefinitely.

I thought that there were a lot of jobber processes, but the number was the same after a clean service start and after the test run (35).

[dshearer]

Fixed in v1.4.4. Sorry for my incompetence.

[samuelallan72]

@dshearer, thanks for the quick fix!

Sorry for my incompetence.

No not at all! Thank you for building an awesome tool. 👍 👍

[PegasisForever]

The docker version of jobber is not updated and still has this bug.