-
Notifications
You must be signed in to change notification settings - Fork 79
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 CPU use after jobber test #301
Comments
Same issue, I downloaded debian release. |
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.
|
dshearer
added a commit
that referenced
this issue
Jun 2, 2020
dshearer
added a commit
that referenced
this issue
Jun 2, 2020
dshearer
added a commit
that referenced
this issue
Jun 2, 2020
dshearer
added a commit
that referenced
this issue
Jun 2, 2020
Fixed in v1.4.4. Sorry for my incompetence. |
@dshearer, thanks for the quick fix!
No not at all! Thank you for building an awesome tool. 👍 👍 |
The docker version of jobber is not updated and still has this bug. |
You can open an issue over at https://github.com/dshearer/jobber-docker |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 runjobber 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?The text was updated successfully, but these errors were encountered: