timlag1305
commented
9 months ago Here is a snippet of the backtrace with some of the symbols. The Input::process is repeated like 10,000 times.
#0 0x00005c6960ea009a in std::unordered_map<std::basic_string_view<char, std::char_traits<char> >, bool, std::hash<std::basic_string_view<char, std::char_traits<char> > >, std::equal_to<std::basic_string_view<char, std::char_traits<char> > >, std::allocator<std::pair<std::basic_string_view<char, std::char_traits<char> > const, bool> > >::at (__k=..., this=<optimized out>, this=<optimized out>, __k=...)
at /usr/include/c++/13.2.1/bits/unordered_map.h:1004
No locals.
#1 Config::getB (name=..., name=...) at src/btop_config.hpp:80
No locals.
#2 Input::process (key="down") at src/btop_input.cpp:209
filtering = <optimized out>
vim_keys = <optimized out>
help_key = <optimized out>
kill_key = <optimized out>
boxes = {_M_elems = {"gpu5", "cpu", "mem", "net", "proc", "gpu0", "gpu1", "gpu2", "gpu3", "gpu4"}}
last_press = 0
#3 0x00005c6960ea04b0 in Input::process (key="down") at src/btop_input.cpp:282
keep_going = false
no_update = true
redraw = true
filtering = <optimized out>
vim_keys = <optimized out>
help_key = <optimized out>
kill_key = 0x5c6960f381cb "k"
boxes = {_M_elems = {"gpu5", "cpu", "mem", "net", "proc", "gpu0", "gpu1", "gpu2", "gpu3", "gpu4"}}
last_press = 0
hauleth
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
BTOP is crashing with the latest version 1.3.2. I suspect this is because rocm doesn't fully support my GPU (RX Vega 56)
To Reproduce
Open btop and wait for it to crash.
Expected behavior
Not crash
Screenshots
[If applicable, add screenshots to help explain your problem.]
Info (please complete the following information):
btop -vbtop version: 1.3.2snap info btopuname -mx86_64uname -r6.7.4-zen1-1-zenAdditional context
Contents of
~/.config/btop/btop.logNote: The snap uses:
~/snap/btop/current/.config/btop(try running btop with
--debugflag 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")run (linux):
gdb btop(macos):lldb btoprto run, wait for crash and press enter if prompted, CTRL+L to clear screen if needed.(gdb):
thread apply all bt(lldb):bt allto get backtrace for all threadsCopy and paste the backtrace here: