Bug 69696

Summary:	Gdict cpu usage way up at a particular word
Product:	[Retired] Red Hat Linux	Reporter:	C. Ray Ng <crn1>
Component:	gnome-utils	Assignee:	Havoc Pennington <hp>
Status:	CLOSED RAWHIDE	QA Contact:	Aaron Brown <abrown>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2003-01-10 22:43:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	67218, 79579

Description C. Ray Ng 2002-07-24 15:43:47 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020513

Description of problem:
Checking the spelling of this word, "brought", gdict's cpu usage suddenly went
way up, back to normal when selecting some other words.
Reproduced on RH7.2 and RH7.3 on different machines.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.Start gdict from gnome menu;
2.Lookup the word "brought";
3.Check cpu usage.
	

Additional info:

Comment 1 Havoc Pennington 2003-01-10 22:43:51 UTC

Does not happen with latest code, at least not for me.