Read the README.md and search for similar issues before posting a bug report!

Yes

Any bug that can be solved by just reading the prerequisites section of the README will likely be ignored.

Describe the bug

Way too much cores

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

To Reproduce

Run

[Steps to reproduce the behavior:]

Expected behavior

Not way too much cores

[A clear and concise description of what you expected to happen.]

Screenshots

See up

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

Info (please complete the following information):

• btop++ version: btop -v
• Binary: [self compiled or static binary from release]
• (If compiled) Compiler and version:
• Architecture: [x86_64, aarch64, etc.] uname -m
• Platform: [Linux, FreeBSD, OsX]
• (Linux) Kernel: uname -r
• (OSX/FreeBSD) Os release version:
• Terminal used:
• Font used:

Latest arch; latest community; all default; all terminals; x64

Additional context

No

contents of ~/.config/btop/btop.log

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

GDB Backtrace

No crash

If btop++ is crashing at start the following steps could be helpful:

(Extra helpful if compiled with make OPTFLAGS="-O0 -g")

1. run (linux): gdb btop (macos): lldb btop

2. r to run, wait for crash and press enter if prompted, CTRL+L to clear screen if needed.

3. (gdb): thread apply all bt (lldb): bt all to get backtrace for all threads

4. Copy and paste the backtrace here: