Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#48191 - htop 2.0 crashes and totally screws running terminal

Attached to Project: Arch Linux
Opened by Bruno Pagani (ArchangeGabriel) - Monday, 15 February 2016, 10:32 GMT
Last edited by Doug Newgard (Scimmia) - Monday, 15 February 2016, 14:00 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

When running htop in a terminal, would it be a tty or konsole (ruling out this bug to be terminal specific), it crashes and destroy the running terminal: nothing works within the terminal except writings commands, so I can’t scroll to view full output or select the output to copy it…

The output starts like this:
*** Error in `htop': free(): invalid next size (fast): 0x0000000000cc8cb0 ***

I’ve joined two screen captures:

–htop.png is the one with the maximum font size that lets the output fit in height

–htop_tiny.png is the one with the lowest available font size, so that the maximum possible of the output content is on the screen (else parts of it disappear at the right).

Sorry I can’t get more of it or in an more usable way, but there is literally nothing I can do in that terminal to get more or even a text copy…
   htop.png (239.1 KiB)
   htop_tiny.png (178.9 KiB)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Monday, 15 February 2016, 14:00 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#48149 
Comment by Bruno Pagani (ArchangeGabriel) - Monday, 15 February 2016, 10:34 GMT
Oh, and I’ve just figured out that removing my htoprc fix this. So attached it.
   htoprc (0.7 KiB)
Comment by Bruno Pagani (ArchangeGabriel) - Monday, 15 February 2016, 10:38 GMT
Narrowed it down to:
update_process_names=1

Can anyone confirm this? So that I could report it upstream.
Comment by Nikolay Bryskin (nbryskin) - Monday, 15 February 2016, 11:07 GMT
I can confirm, I have exactly the same bug, setting update_process_names=0 helps to fix it.
Comment by Bruno Pagani (ArchangeGabriel) - Monday, 15 February 2016, 11:12 GMT
Already upstreamed several times: https://github.com/hishamhm/htop/issues/377.
Comment by Bruno Pagani (ArchangeGabriel) - Monday, 15 February 2016, 12:49 GMT
So, the fix would be to include https://github.com/hishamhm/htop/commit/0b70439316b4e4608c0916317ded7e6e56982de6 while waiting for 2.0.1.

Loading...