ERROR: Exception in runner thread -> Cpu:: -> deque::_M_range_check: __n (which is 3)>= this->size() (which is 2)

[jialiangZ]

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

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

Describe the bug

I used a snap install at first, then I remove it. I followed the readme process to install btop, using the make default configuration, and after that running btop reported errors.

To Reproduce

Running btop keeps giving me errors

Screenshots

Info (please complete the following information):

• btop++ version: 1.4.0+5535f50
  • If using snap: snap info btop do have some info
• Binary: [self compiled]
• Architecture: [x86_64]
• Platform: [Linux]
• (Linux) Kernel: 6.8.0-48-generic
• (OSX/FreeBSD) Os release version:
• Terminal used:
• Font used:

Additional context

Contents of ~/.config/btop/btop.log
2025/01/17 (09:40:39) | ===> btop++ v.1.4.0
2025/01/17 (09:40:39) | ERROR: Exception in runner thread -> Cpu:: -> deque::_M_range_check: __n (which is 3)>= this->size() (which is 2)

Note: The snap uses: ~/snap/btop/current/.config/btop

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

GDB Backtrace

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:

[Gingko4ever]

Strangely enough, the error disappeared when I switched to a bigger monitor🥲

[pistej]

Installed btop via apt: (1.3.0-1)
Exception in runner thread -> Cpu:: -> graphs, clock, meter : vector::_M_range_check: __n (which is 0) >= this->size() (which is 0)

[dusty-nv]

Strangely enough, the error disappeared when I switched to a bigger monitor🥲

If you start it on a larger terminal, it runs. Then change screens off the CPUs with the number keys. Then you can make the window smaller again, and if you attempt to change back to a screen that would have overflowed and crashed, it warns you with an error dialog.

[serhiiKalchenko]

Linux Mint:
sudo apt install btop
btop
ERROR: Exception in runner thread -> Proc:: -> wstring_convert::from_bytes
WTF?

btop version: 1.2.3

[WhoisDonlee]

I ran into the same problem. I did some testing and it only happens if the CPU lower or upper graph is set to something that devides it in multiple compartments, for me this is only some GPU settings, like gpu-totals.

Then resize the window to where you should get the "Terminal size too small" message and it crashes.

With any other settings where it's just a single graph it works fine.

I'm on btop 1.4.0 compiled with GPU support.