Htop does not show on Catalina

[knightjp]

I'm having a weird problem with htop. It installed just fine on Catalina. No issues there. But when you try to run it. It shows a blank terminal window. Then it appears suddenly after a while like it was taking time to render.

[knightjp]

blank screen

[cjones051073 (Chris Jones)]

I see no such issue here, on macOS 10.15, Xcode 11.1.

Using either Apple's Terminal application, or MacPorts iTerm2 build, htop starts and renders immediately. I am also, incase it is relevant, using the new zsh default shell.

what terminal / shell are you using ?

[neverpanic (Clemens Lang)]

I'm not on Catalina yet, so I can't debug this.

[knightjp]

Replying to cjones051073:

I see no such issue here, on macOS 10.15, Xcode 11.1.

Using either Apple's Terminal application, or MacPorts iTerm2 build, htop starts and renders immediately. I am also, incase it is relevant, using the new zsh default shell.

what terminal / shell are you using ?

I am using the standard MacOS Terminal.app and the zsh shell.

It is rather weird. I am not sure. Honestly wish I was a developer so that I could find a way to assist with this.

[cjones051073 (Chris Jones)]

I am afraid, but until someone else chimes in to say they also see this, then only you can make progress on resolving it.

Do you have a custom htop configuration ? Its normally kept under ~/.config/htop . If so, try moving it out the way.

Do you have anything in your shell profile, ~/.zshrc or ~/.zprofile that could be affecting this ?

[kurthindenburg (Kurt Hindenburg)]

It works here - are you running in it a terminal with system zsh?

[knightjp]

Replying to kurthindenburg:

It works here - are you running in it a terminal with system zsh?

yes I am.. I am not sure what to do here. Everything is stock MacOS. I haven't done anything to the stock zshrc or zprofile.

[cjones051073 (Chris Jones)]

I understand it is annoying, but the fact is until someone else can reproduce the issue, the evidence has to point to it being something specific to your setup.

Maybe you could send a mail to one of the mailing list, just asking people running 10.15 to give it a try, to see if you can find someone else with the issue ?

[kurthindenburg (Kurt Hindenburg)]

maybe try 'sudo dtruss htop ' and see what it is doing when it is "stuck" - I get a lot of errors due to system restrictions but it might show something for you.

[knightjp]

copy of the errors

[knightjp]

I attached a copy of the results of the command

'sudo dtruss htop'

[kurthindenburg (Kurt Hindenburg)]

This is beyond me- can you make a new user and try it on that w/ everything the default? Try using bash?

Here's the reporters:

SYSCALL(args) 		 = return

Here's the first few lines for me

dtrace: system integrity protection is on, some features will not be available

SYSCALL(args) 		 = return
select(0x1, 0x7FFEEC4BB750, 0x0, 0x0, 0x7FFEEC4BB7D8)		 = 1 0
dtrace: error on enabled probe ID 2186 (ID 165: syscall::read:return): invalid kernel access in action #12 at DIF offset 68
sigaction(0x12, 0x7FFEEC4BB918, 0x1037A5C48)		 = 0 0
select(0x1, 0x7FFEEC4BB890, 0x0, 0x0, 0x7FFEEC4BB918)		 = 0 0
dtrace: error on enabled probe ID 2184 (ID 167: syscall::write:return): invalid kernel access in action #12 at DIF offset 68

[tracuser]

Hi, I'm having the same problem, on Catalina 10.15.1 using Bash 3.2, here is the dtruss htop dump:

bash-3.2$ sudo dtruss htop
Password:
dtrace: system integrity protection is on, some features will not be available

SYSCALL(args) = return
select(0x1, 0x7FFEEC7688D0, 0x0, 0x0, 0x7FFEEC768958) = 1 0
dtrace: error on enabled probe ID 2186 (ID 165: syscall::read:return): invalid kernel access in action #12 at DIF offset 68
sigaction(0x12, 0x7FFEEC768AA8, 0x1034FEBF8) = 0 0\ select(0x1, 0x7FFEEC768A20, 0x0, 0x0, 0x7FFEEC768AA8) = 0 0
dtrace: error on enabled probe ID 2184 (ID 167: syscall::write:return): invalid kernel access in action #12 at DIF offset 68
select(0x1, 0x7FFEEC768A20, 0x0, 0x0, 0x7FFEEC768AA8) = 0 proc_info0
dtrace: error on enabled probe ID 2184 (ID 167: syscall::write:return): invalid kernel access in action #12 at DIF offset 68 sigaction(0x12, 0x7FFEEC768A88, 0x0) = 0 0 dtrace: error on enabled probe ID 2184 (ID 167: syscall::write:return): invalid kernel access in action #12 at DIF offset 68 dtrace: error on enabled probe ID 2184 (ID 167: syscall::write:return): invalid kernel access in action #12 at DIF offset 68 dtrace: error on enabled probe ID 2184 (ID 167: syscall::write:return): invalid kernel access in action #12 at DIF offset 68 ioctl(0x1, 0x80487415, 0x7FAB56C03ED0) = 0 0

[barracuda156]

Is this still an issue?

[neverpanic (Clemens Lang)]

Likely no longer an issue, please re-open if the problem persists.