[BUG]

[WolfFlightTZW]

Describe the bug

Error message produced after running for a period of time

To Reproduce

run btop in terminal

Expected behavior

ERROR: Exception in runner thread -> Cpu:: -> graphs, clock, meter : basic_string::_M_create

Screenshots

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

Info (please complete the following information):

• btop++ version: btop version: 1.1.1
• Binary: static binary from release
• (If compiled) Compiler and version:
• Architecture: [x86_64, aarch64, etc.] uname -m
• Platform: [Linux, FreeBSD, OsX]
• (Linux) Kernel: `4.15.0-128-generic
• (OSX/FreeBSD) Os release version:
• Terminal used: bash
• Font used: FONTFACE="Fixed"

Additional context

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

2021/11/17 (19:40:50) | ===> btop++ v.1.1.1
2021/11/17 (19:40:50) | ERROR: Exception in runner thread -> Cpu:: -> graphs, clock, meter : basic_string::_M_create

2021/11/17 (20:30:53) | ===> btop++ v.1.1.1
2021/11/17 (20:30:53) | ERROR: Exception in runner thread -> Cpu:: -> graphs, clock, meter : basic_string::_M_create

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:

[syrphide]

I have the same issue with v.1.2.13:

2023/01/20 (13:08:57) | ===> btop++ v.1.2.13
2023/01/20 (13:08:57) | ERROR: Exception in runner thread -> Cpu:: -> graphs, clock, meter : basic_string::_M_create

[holdjun]

ERROR: Exception in runner thread -> Cpu:: -> graphs, clock, meter : basic_string::at: __n (which is 0) >= this->size() (which is 0)

same issue with 1.3.0

[imwints]

Please provide a back trace

[holdjun]

@imwints When the terminal's window becomes smaller than a certain size, it will crash.

[imwints]

I can't reproduce the issue. Could you disable GPU support and try to narrow it down with GDB?

[holdjun]

It is indeed caused by the GPU reality; if the GPU is turned off, it won't crash. I understand that it is caused by the GPU displaying too many gpus

I suspect the display item is having issues.

[imwints]

OK please open a new bug report since this is unrelated to the original reported bug.