Skip to content
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]bpytop misbehaves after CPU cores are disabled and crashes after they are enabled #424

Open
linuxcf opened this issue Oct 6, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@linuxcf
Copy link

linuxcf commented Oct 6, 2024

Describe the bug

[A clear and concise description of what the bug is.]

To Reproduce

[Steps to reproduce the behavior:]

  1. (While bpytop is running, disable some CPU cores, e.g. sudo chcpu -d 2-11 (here I disable cores 2-11). This will result in weird numbering of the CPU cores on the bpytop display.
  2. In the above example, with cores 2-11 still disabled, shut down bpytop and restart it. Now, the active cores are shown properly.
  3. Now re-enable the deactivated cores (sudo chcpu -e 2-11), while bpytop is running from step (2) above.. bpytop will now crash.

Expected behavior

[A clear and concise description of what you expected to happen.]
The displayed cores should correspond to the active ones. For example, in the classic top if a core is deactivated, it is no longer shown. In htop it is explicitly shown as off-line. bpytop should not crash if more cpu cores are enabled.

Screenshots

[If applicable, add screenshots to help explain your problem.]

Info (please complete the following information):

  • bpytop version: 1.0.68
  • psutil version: 5.9.8
  • (Linux) Linux distribution and version: Ubuntu 24.04
  • (OSX/FreeBSD) Os release version:
  • Terminal used: Bash
  • Font used: Monospace 12
  • Python version, python3 --version (version 3.6 or above is required): 3.12.3

Additional context

contents of ~/.config/bpytop/error.log

(try running bpytop with --debug flag if error.log is empty)

error.log

@linuxcf linuxcf added the bug Something isn't working label Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants