Skip to content

[BUG] Crash on startup #248

@boxxxie

Description

@boxxxie

Describe the bug

launch bashtop. it goes through it's checklist. gets to the screen dimensions. then exits without any messages/error.

To Reproduce

bashtop

Expected behavior

expect it to run and show me its sexy TUI

Screenshots

N/A

Info (please complete the following information):

  • Bashtop version: git via AUR
  • (Linux) Linux distribution and version: manjaro
  • (Linux) Data collection type (/proc or psutil): /proc
  • Psutil version: python3 -c "import psutil; print(psutil.version_info)" (version 5.7.0 or above is required): (7, 2, 2)
  • (OSX/FreeBSD) Os release version: n/a
  • Terminal used: ghostty & warp
  • Font used: ubuntu
  • Bash version, bash --version (version 4.4 or above is required): GNU bash, version 5.3.9(1)-release (x86_64-pc-linux-gnu)
  • Locales: output of locale -v: LANG=en_CA.UTF-8 LC_CTYPE="en_CA.UTF-8" LC_NUMERIC=en_CA.UTF-8 LC_TIME=en_CA.UTF-8 LC_COLLATE="en_CA.UTF-8" LC_MONETARY=en_CA.UTF-8 LC_MESSAGES="en_CA.UTF-8" LC_PAPER=en_CA.UTF-8 LC_NAME=en_CA.UTF-8 LC_ADDRESS=en_CA.UTF-8 LC_TELEPHONE=en_CA.UTF-8 LC_MEASUREMENT=en_CA.UTF-8 LC_IDENTIFICATION=en_CA.UTF-8 LC_ALL=

Additional context

contents of $HOME/.config/bashtop/error.log

New instance of bashtop version: 0.9.25 Pid: 1043260
03:12:17 PM ERROR: On line 363 
/usr/bin/bashtop: line 2424: ( ( 49-22 ) * 1000 * 1000 ) / ( cpu[hz]*time_elapsed*16 ) : division by 0 (error token is "( cpu[hz]*time_elapsed*16 ) ")
/usr/bin/bashtop: line 2424: ( ( 69-22 ) * 1000 * 1000 ) / ( cpu[hz]*time_elapsed*16 ) : division by 0 (error token is "( cpu[hz]*time_elapsed*16 ) ")

(enable error-logging in "$HOME/.config/bashtop/bashtop.cfg" if missing)

[work around]

i deleted my config and bashtop started working again.
i think we should have better support for troubleshooting when errors happen. i didn't know where to look for logs until i came here to github. that type of info could be spit out when the program crashes. also this seems to be an error related to config, so maybe a more robust config validator could help here.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions