btop: [BUG] Crashes on startup (on kitty and alacritty)
Describe the bug Tried to run on pop OS 21.04. Crashes on startup with the following log:
/usr/include/c++/11/ranges:540: constexpr std::ranges::iota_view<_Winc, _Bound>::iota_view(std::type_identity_t<_Winc>, st
3 d::type_identity_t<_Bound>) [with _Winc = int; _Bound = int; std::type_identity_t<_Winc> = int; std::type_identity_t<_Boun
2 d> = int]: Assertion 'bool(__value <= __bound)' failed.
1 fish: “btop” terminated by signal SIGABRT (Abort)
It seems that it doesn’t like the kitty terminal, but sometimes it seemed random. Unfortunately I wasn’t taking note of everything before but I think it happens on kitty but not eg. on gnome terminal.
To Reproduce Run the executable on the kitty terminal.
Info (please complete the following information):
- btop++ version: 1.0.2
- Architecture: x86_64
- Platform: Linux
- (Linux) Kernel: 5.11.0-7620-generic
- Terminal used: kitty
- Font used: Victor Mono
Additional context
contents of ~/.config/btop/btop.log
(try running btop with --debug flag if error.log is empty)
2021/09/20 (19:15:41) | ===> btop++ v.1.0.2
2021/09/20 (19:15:41) | DEBUG: Starting in DEBUG mode!
2021/09/20 (19:15:41) | INFO: Logger set to DEBUG
2021/09/20 (19:15:41) | DEBUG: Setting LC_ALL=en_US.UTF-8
2021/09/20 (19:15:41) | INFO: Running on /dev/pts/1
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 44 (16 by maintainers)
You’re a legend, can no longer reproduce this.
@StreakyCobra @Shinyzenith I’m pretty sure I know somewhat where this is happening (when the graphs in the CPU box is generated and calling the
back()function on the list holding either the cpu percent or cpu temperature values.But I’m gonna have to set up a proper test environment so I can reproduce the exception myself. Just uploading commit on commit with you guys testing it out is gonna be a bit tedious.
But should have some time to take a proper look at this later this week.
It could be helpful if you both wanted to post a short list of the terminals and window manager combinations you have gotten the exception with so far (to make it easier for me to set up the testing).