Bug 155340

Summary:	HTDIG takes up 90% of CPU
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Joe Crollard <lunar_raven>
Component:	Other	Assignee:	Hendrik Vogelsang <hvogel>
Status:	RESOLVED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	suse-beta
Version:	Beta 6
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Joe Crollard 2006-03-06 02:33:44 UTC

PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
8361 root     27  10 35484  23m 1852 R 91.3  9.6   3:27.74 htdig

I filed this as a bug (mixed in with the y2base problem)...but it really didn't get much attention...because it went towards the yast issue.

Anyway, this was very random, but I noticed things were running slow again, checked top...and as you can see above, htdig is taking up 90% of my cpu.  I'm not sure which log you need...but I figured I should file this as a bug so it is ironed out before the final release.

Comment 1 Michael Gross 2006-03-06 09:47:00 UTC

Joe, we can handle only one problem per report, so always file seperate reports for seperate problems.

Is there any way to reproduce this reliably? What makes you sure this is a bug? Please be more verbose.

Comment 2 Michael Gross 2006-03-06 10:03:13 UTC

*** Bug 155330 has been marked as a duplicate of this bug. ***

Comment 3 Christian Boltz 2006-03-06 22:53:31 UTC

Duplicate of bug #152273?

Comment 4 Michael Gross 2006-03-07 10:08:28 UTC

This was fixed for Beta4, however it could be connected. Joe: When exactly does this happen and how often?

Comment 5 Joe Crollard 2006-03-08 00:15:25 UTC

Well it's only happened once so far, which is different than beta 4.  I haven't had the problem again after killing the process.   If it happens again, is there a certain log I should attach?

Thanks

Comment 6 Michael Gross 2006-03-08 11:43:58 UTC

If it happened right after the installation or in connection with susehelp, it could really be the problem in 152273. Is it possible for you to reproduce this (maby with a fresh installation or by deleting the index of susehelp and calling it again)?

Comment 7 Michael Gross 2006-03-15 14:01:49 UTC

I noticed that htdig seems to use extensive algorithms that consumes a lot of CPU-time, it even makes the machine unresponsive for some seconds for a remote connection. So I suppose this is not a bug. Reassigning to Hendrik for a comment.

Comment 8 Hendrik Vogelsang 2006-03-15 14:06:19 UTC

everything can run with a CPU usage of 100% if its needed. Thats no bug. Will what did you fix in beta4?

Comment 9 Joe Crollard 2006-03-15 17:21:36 UTC

If some newbie tries out linux and immediatly notices that one single process is taking up 100% of their CPU, chances are they will conclude that linux sucks and windows is better.  This may not be a bug, but it is a problematic feature that will annoy users.

However, since I killed it, it has not come back and I've been unable to recreate the issue.

Comment 10 Hendrik Vogelsang 2006-03-21 13:18:17 UTC

will?

Comment 11 Will Stephenson 2006-03-21 14:30:43 UTC

Yes, it's me.  Since beta4 I have reduced the number of manuals that susehelp indexes on SuSEconfig run by default.  Once an index is generated, susehelp does not reindex on subsequent runs of SuSEconfig.

Comment 12 Hendrik Vogelsang 2006-03-21 15:33:09 UTC

so i consider this fixed