High CPU usage caused by freezing due to pressing dd to kill a process

[ShahramMohammed]

Checklist

• I've looked through the troubleshooting docs, the known problems list, and existing open issues for similar issues.

What operating system and version are you using?

6.11.9-arch1-1

What architecture are you using?

x86_64/AMD64

What terminal(s) are you running bottom on that are experiencing the problem?

st 0.8.5

(Optional) What filesystem(s) are you using?

Btrfs

What version of bottom are you running?

0.10.2

How did you install bottom?

Arch official repos

Describe the issue

I have a somewhat similar issue to #1602. It is not easy to reproduce as it happens inconsistently and I don't know what triggers it. But it could be related to another issue I have of bottom suddenly freezing shortly after opening it. Again, that issue is also hard to reproduce but from what I can recall I think it was freezing right after I tried to kill a process by pressing dd.

What is the expected behaviour?

Normal CPU usage of 2% and below. When this issue happens I can hear my fans speeding up and the usage can go all the way up to 50% if I remember right.

What is the actual behaviour?

Explained

How can we reproduce this?

Unfortunately I don't know what triggers it so I am unable to reproduce but I will update this issue if I ever figure out what a way to reproduce it

Additional information

No response

[ShahramMohammed]

Okay it just happened again and I can confirm the high CPU usage is due to the freezing issue that I can also now confirm happens due to pressing dd on a process to kill it. But this freezing behavior is inconsistent, dd works fine most of the time.
It went from normal to 12 percent after the freeze, then to 25 percent a short while later. It unfroze after a few minutes but the high CPU usage remains.

same CPU usage report from btop:

[ShahramMohammed]

I forgot to add: when the program freezes, the process killing confirmation page fails to show up, so it freezes on the main process window.

[ClementTsang]

Interesting, I'll take a look at this.

[m1126stryker]

been able to reproduce it here too though it appears to happen semi randomly..
and trying to use another instance of bottom to kill the blocked one blocks it the same way too -high cpu usage and freezing without initiating the signal dialog etc.-

arch linux 6.12.1 x86_64 btrfs
bottom 0.10.2 from the official repo
running on alacritty 0.14