Bug 107692 – htop-0.5.2 segfaults after some time running

• Status: RESOLVED UPSTREAM
• Product: Gentoo Linux

[Description Wolf Giesen (RETIRED) 2005-09-30 05:02:04 UTC]

htop-0.5.2 dies an me when I let it run for some time. I have this behaviour on
at least 5 x86 servers. The time to segfault varies. Sometimes 15 minutes are
enough, but overnight (please don't argue about that being nonsense :-) I
usually find it dead the next morning.

All machines use +nptl. Investigating on alpha now.


Reproducible: Sometimes
Steps to Reproduce:
1. ssh into machine
2. start htop
3. wait

Actual Results:  
htop segfaults

Expected Results:  
htop keeps running

x86, stable package versions only, except samba (3.0.20).
2.6.11 and 2.6.12 kernels with NPTL. Various RAM sizes from .5 to 2 Gig, uni-
and dual-CPU machines.

[Comment 1 Wolf Giesen (RETIRED) 2005-09-30 06:47:54 UTC]

Hm, I take a guess and hint to SMP. All affected machines have at least
HyperThreading, and thus SMP support. I'll try with my old P3 and Athlons, and I
don't remember htop dying on me there. More results to come.

[Comment 2 Wolf Giesen (RETIRED) 2005-09-30 06:48:12 UTC]

Hm, I take a guess and hint to SMP. All affected machines have at least
HyperThreading, and thus SMP support. I'll try with my old P3 and Athlons, and I
don't remember htop dying on me there. More results to come.

[Comment 3 Tres 'RiverRat' Melton 2005-10-01 07:10:21 UTC]

What would be really useful here is a core dump and a backtrace.  I suggest
enabling debugging and seeing what function in htop is mis-handling the memory.

[Comment 4 Wolf Giesen (RETIRED) 2005-10-05 03:24:35 UTC]

Well, the fun part is: when I build htop-0.5.2 with "debug", it bombs directly
after calling with

htop: ProcessList.c:579: ProcessList_scan: Assertion `cpuid == i - 1' failed.

:)

[Comment 5 Wolf Giesen (RETIRED) 2005-10-05 22:29:29 UTC]

Seriously. USE="debug" emerge htop gives me an htop-0.5.2 that does not work.

[Comment 6 Wolfram Schlich (RETIRED) 2005-10-06 03:13:21 UTC]

contacted the htop developer -- stay tuned...

[Comment 7 Wolf Giesen (RETIRED) 2005-10-06 05:20:17 UTC]

Alright...

[Comment 8 Wolfram Schlich (RETIRED) 2005-10-06 07:22:26 UTC]

Hisham told me 0.5.4 will be released shortly which should
fix those problems. So please stand by until it's released
and added to the portage tree.

[Comment 9 Wolf Giesen (RETIRED) 2005-12-15 21:30:13 UTC]

I find it mildly bewildering that this bug was closed weeks ago, and yet, we are
still on 0.5.2 stable, which is definitely broken on *all* my SMP systems.

This bug was closed but not resolved ...

[Comment 10 Wolfram Schlich (RETIRED) 2005-12-16 00:32:27 UTC]

have you tried the archmasked 0.5.4?

[Comment 11 Wolf Giesen (RETIRED) 2005-12-16 01:00:21 UTC]

Since I use SMP systems for production and non-SMP for testing, no.
I tend to draw a clear line between production and testing, so I didn't really
want to. Guess I have to, hm?

[Comment 12 Wolfram Schlich (RETIRED) 2005-12-16 05:28:11 UTC]

$ echo '=sys-process/htop-0.5.4 ~arch' >>/etc/portage/package.keywords
$ emerge -avt =sys-process/htop-0.5.4

What's the deal?

[Comment 13 Wolf Giesen (RETIRED) 2005-12-18 03:59:45 UTC]

The deal was me not seeing that it's become ~x86 from hardmasked :) I usually don't bother with hardmasked things unless it's something where I'm personally committed the dig through the source. I'll report back.