You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Lately I've been getting crashes in btop every couple of days. This might be Fedora-specific (I'm going to report there as well), but I thought it might be relevant for upstream as well.
I'm not doing anything special, just running btop in a window for an extended time (a couple days pass until a crash occurs). After the crash, the terminal is in a weird state with no cursor and some terminal escape sequences dumped as clear text. reset brings it back to normal.
To Reproduce
I'm not sure how to reproduce this crash, I'm not even interacting with btop.
Expected behavior
btop should run for an extended period of time without crashing.
It looks like Stall in Runner thread, restarting! coincides with the crash (bar a few seconds). For completeness, coredumpctl lists the following crashes on my system:
TIME PID UID GID SIG COREFILE EXE SIZE
Sun 2024-02-18 10:39:45 CET 66383 1000 1000 SIGABRT missing /usr/bin/btop -
Mon 2024-02-19 23:17:08 CET 1800059 1000 1000 SIGABRT missing /usr/bin/btop -
Tue 2024-02-27 11:02:08 CET 2158319 1000 1000 SIGABRT missing /usr/bin/btop -
Mon 2024-03-04 13:01:03 CET 799199 1000 1000 SIGABRT missing /usr/bin/btop -
Tue 2024-03-05 10:00:55 CET 2728784 1000 1000 SIGABRT missing /usr/bin/btop -
Wed 2024-03-06 11:30:27 CET 2918685 1000 1000 SIGABRT missing /usr/bin/btop -
Thu 2024-03-07 10:51:54 CET 3098213 1000 1000 SIGABRT missing /usr/bin/btop -
Wed 2024-03-13 10:04:26 CET 6033 1000 1000 SIGABRT missing /usr/bin/btop -
Sun 2024-03-17 11:10:33 CET 2176201 1000 1000 SIGABRT missing /usr/bin/btop -
Wed 2024-03-20 09:43:04 CET 2405689 1000 1000 SIGABRT missing /usr/bin/btop -
Thu 2024-03-28 10:45:11 CET 570858 1000 1000 SIGABRT missing /usr/bin/btop -
Wed 2024-04-03 09:12:26 CEST 1828000 1000 1000 SIGABRT missing /usr/bin/btop -
Fri 2024-04-05 10:11:04 CEST 2199085 1000 1000 SIGABRT missing /usr/bin/btop -
Sun 2024-04-07 16:23:09 CEST 3118394 1000 1000 SIGABRT missing /usr/bin/btop -
Fri 2024-04-12 22:25:32 CEST 3187773 1000 1000 SIGABRT missing /usr/bin/btop -
Tue 2024-04-16 11:05:38 CEST 4048104 1000 1000 SIGABRT missing /usr/bin/btop -
Sat 2024-04-20 11:49:23 CEST 88530 1000 1000 SIGABRT missing /usr/bin/btop -
Wed 2024-04-24 14:30:45 CEST 289726 1000 1000 SIGABRT present /usr/bin/btop 676.4K
Fri 2024-05-03 11:02:04 CEST 725139 1000 1000 SIGABRT present /usr/bin/btop 1.7M
Mon 2024-05-06 12:40:16 CEST 12462 1000 1000 SIGABRT present /usr/bin/btop 527.7K
So there is some correlation, but not all time. Particularly, note that the logs from 2024/05/07 were from my own compiled btop from master and it did not crash. The 1.7M dump is a different crash which I will report separately. The last one (PID 12462) is identical to the one I'm reporting here (PID 289726).
Describe the bug
Lately I've been getting crashes in btop every couple of days. This might be Fedora-specific (I'm going to report there as well), but I thought it might be relevant for upstream as well.
I'm not doing anything special, just running btop in a window for an extended time (a couple days pass until a crash occurs). After the crash, the terminal is in a weird state with no cursor and some terminal escape sequences dumped as clear text.
reset
brings it back to normal.To Reproduce
I'm not sure how to reproduce this crash, I'm not even interacting with btop.
Expected behavior
btop should run for an extended period of time without crashing.
Screenshots
n/a
Info (please complete the following information):
btop --version
: 1.3.2snap info btop
uname -m
: x86_64uname -r
: 6.1.89-200.fc40.x86_64Additional context
Contents of
~/.config/btop/btop.log
It looks like
Stall in Runner thread, restarting!
coincides with the crash (bar a few seconds). For completeness,coredumpctl
lists the following crashes on my system:So there is some correlation, but not all time. Particularly, note that the logs from
2024/05/07
were from my own compiled btop from master and it did not crash. The 1.7M dump is a different crash which I will report separately. The last one (PID 12462) is identical to the one I'm reporting here (PID 289726).Backtrace
Core dump: crash3.zip
The text was updated successfully, but these errors were encountered: