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
It's been crashing for me lately. Locks up (display won't update), no response to keys, 100% CPU on one core, Ctrl-C won't stop it, kill -SIGHUP will. Usually it runs for days before this happens, but just now it was less than an hour from startup so I suppose it's random. It's been doing this for a few months. Is there any info I can collect to help you?
I'm running this in a tmux window. Linux kernel 5.1.5.
The text was updated successfully, but these errors were encountered:
Hello @jtgd, my apologies for not replying earlier. I had intended to do so but honestly just forgot.
I tried letting it run for days as you did back when you reported this but I wasn't able to reproduce this so I'm afraid you would have to give me some info on this first. Fortunately it's simple:
Build and run the debug build (cargo run). It will be noticeably slower but it will most probably be still fast enough to be usable. It might idle on 10-20% of CPU though.
Wait for it to hang
When it hangs, attach with gdb (ie rust-gdb --pid=$(pgrep bb)). If successful bb will be stopped (process state T).
Usually you would share a core dump, but this would mean I would see all of the procfs data in the memory. Instead print a backtrace (bt), and copy paste it here. That should hopefully be enough.
Run kill to stop the process. (by the way, Ctrl-C not working is a bug. I hope I fix a push for this asap, thank you)
It's been crashing for me lately. Locks up (display won't update), no response to keys, 100% CPU on one core, Ctrl-C won't stop it, kill -SIGHUP will. Usually it runs for days before this happens, but just now it was less than an hour from startup so I suppose it's random. It's been doing this for a few months. Is there any info I can collect to help you?
I'm running this in a tmux window. Linux kernel 5.1.5.
The text was updated successfully, but these errors were encountered: