HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
hishamhm
htop
C2015–2026
hishamhm / htop · Archived

htop

htop is an interactive text-mode process viewer for Unix systems. It aims to be a better 'top'.

Command LineSystems & InfrastructureMobile & Desktop
Explore on GitHubRead Hacker News discussions
17Distinct people
18Mentions
0Explicit recommenders
5.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

htop is an interactive text-mode process viewer for Unix systems. It aims to be a better 'top'.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year18 dated mentions

Observed mentions: 2015-10-03 10:19:37 UTC to 2026-01-14 19:02:55 UTC.

024682015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 3 mentions; 2 submissions, 1 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC101
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC321
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC826
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC101
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC000
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC101
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

What Hacker News says

18 sources
jonasn·Jan 14, 2026
You are spot on that the original author had a valid reason: at the time, it was literally the only way to do it. The method in question (Java 1.5) was released in September 2004. While the POSIX standard existed, it only provided a way to get total CPU time, not the specific user time that Java needed. You can read about it more in the history section here: https://norlinder.nu/posts/User-CPU-Time-JVM/#a-walk-through.... But it's worth noting that while this specific case can be "fixed" with a function call, parsing /proc is still the standard way to get data in Linux. Even today, a vast amount of kernel telemetry is only exposed via the filesystem. If you look at the source code for tools like htop, they are still busy parsing text files from /proc to get memory stats (/proc/meminfo), network I/O, or per-process limits. See here https:/
Read the rest
/github.com/hishamhm/htop/blob/master/linux/LinuxProc....
In A 40-line fix eliminated a 400x performance gap
shakna·Jan 31, 2018Submission

Ask HN: Crashing High Sierra with Serial?

I don't really know where to report this, as Apple's bugtrackers seem to be private. And I'm hoping somebody else has a fix, because this is highly irritating. I can crash my macOS High Sierra machine consistently, just by reading from a serial line. To explain more, I've just been working on a silly side-project, using an Arduino Pro Mini. A tiny 8Mhz machine. The code is fairly simple, see here [0]. Now, if I try and read from the serial line for that, then the program trying to read will freeze up. It works across any program: Arduino IDE's serial monitor, gnu screen, picocom, even cat and head. e.g. cat /dev/tty.usbserial-A703CXL3 Terminal still takes input, but seems to do nothing with it, and I can't open a new terminal. So, if I go with the nuclear option, and take the USB-serial connection out of the computer, High Sierra cra
Read the rest
shes to reboot instantly. I think this might be related to the htop[1] or task_for_pid[2] bugs, but I don't know. Here's the kicker though: Since this program started those crashes, I can't read from any serial device without the same problem, whether or not I'm using the same serial line reader. (Different boards connected using different cables still cause the problem). And not being able to use a serial line is a problem for my everyday. (I should also note that same device and same cable that caused this, works perfectly fine on my crappy Linux laptop.) [0] https://gist.github.com/shakna-israel/6e6f7d6dcec871505f2d9b0f033ea584 [1] https://github.com/hishamhm/htop/issues/682 [2] https://jvns.ca/blog/2018/01/28/mac-freeze/
1 points · Open discussion
bangonkeyboard·Jan 6, 2018
Speaking of making unsubstantiated claims: this post is totally untrue. The formula was not updated with an OS requirement due to some misconstrued build issue; installation on High Sierra was blocked 6 hours ago, as noted in the very issue thread that this HN topic is about [0], explicitly because the freezes and crashes are very real and reproducible. [0]: https://github.com/hishamhm/htop/issues/682#issuecomment-355...
In Leaving htop running freezes macOS High Sierra

Showing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.