-
-
Notifications
You must be signed in to change notification settings - Fork 723
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
[BUG] btop
crashes when number of CPU cores enabled < number of CPU cores total
#439
Labels
bug
Something isn't working
Comments
@BSGalvan |
Here you go, output of
|
@BSGalvan |
Awesome! Thanks for the quick fix 😄 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
btop
crashes with an error when only some of the available cores on a CPU are configured to run.The error message is this:
ERROR: Exception in Shared::init() -> collect() : stoi
To Reproduce
The initial error occurred on a work desktop which I do not have access to as of writing this.
On it however, 16 out of 32 CPU cores were enabled.
CPU cores can be manually disabled using
chcpu(8)
, so this is what I did to reproduce the error on my Ryzen 7 4750U laptop:sudo chcpu -d 4-15
(kind of overkill, but on another laptop with an i5-7200U, knocking out 1 or 2 did suffice)btop
, which throws this error:ERROR: Exception in Shared::init() -> collect() : stoi
Expected behavior
btop
should show at least the usual UI, but with lesser CPUs in the 'CPU' box (which indicates that some of them are disabled).This is what it shows now:

Whereas this is what I expect it to show:

Note: I was able to get the above by reverting the change in 96b770c. However, I do not know if that is a sensible bug fix, hence an issue instead of a PR!
Screenshots
Info (please complete the following information):
Additional context
Contents of
~/.config/btop/btop.log
:GDB Backtrace
The text was updated successfully, but these errors were encountered: