cpu load goes to 100% when beacon dies
I realized that the cpu load of bliss grows to 100% when beacon is killed (stopped with ctrl-c). This happens when using tmux so I think it is a problem with the listener process that displays scans.
Here are the processes that are running on my pc:
(base) linus@rix$ ps -ax | grep bliss
22936 pts/3 Sl+ 0:02 /home/linus/miniconda3/envs/bliss_dec19/bin/python /home/linus/miniconda3/envs/bliss_dec19/bin/beacon-server --db_path=tests/test_configuration --tango-port=20000 --log_server_port 0
22940 pts/3 Sl+ 0:01 /home/linus/miniconda3/envs/bliss_dec19/bin/python -m bliss.tango.servers.databaseds -l 0 --db_access beacon --port 20000 2
23301 pts/4 Sl+ 0:02 /home/linus/miniconda3/envs/bliss_dec19/bin/python /home/linus/miniconda3/envs/bliss_dec19/bin/bliss -s test_session
23312 ? Ss 0:00 tmux -S /tmp/bliss_tmux_1000.sock -f /home/linus/Documents/work/bcu/bliss_dec19/bliss/config/tmux.conf new-session -d -s test_session -n bliss /home/linus/miniconda3/envs/bliss_dec19/bin/python -m bliss.shell.cli.start_bliss_repl test_session WARN
23313 pts/7 Ssl+ 0:08 /home/linus/miniconda3/envs/bliss_dec19/bin/python -m bliss.shell.cli.start_bliss_repl test_session WARN
23315 pts/8 Ssl+ 0:01 /home/linus/miniconda3/envs/bliss_dec19/bin/python -m bliss.data.start_listener test_session
23317 pts/4 S+ 0:00 tmux -S /tmp/bliss_tmux_1000.sock attach-session -t test_session
23452 pts/5 S+ 0:00 grep --color=auto bliss
if beacon stops the process with the really high load is
23315 [...]/miniconda3/envs/bliss_dec19/bin/python -m bliss.data.start_listener test_session
this one also shows increased load
23312 tmux -S /tmp/bliss_tmux_1000.sock -f [...]/bliss/config/tmux.conf new-session -d -s test_session -n bliss [...]/miniconda3/envs/bliss_dec19/bin/python -m bliss.shell.cli.start_bliss_repl test_session WARN