Bug 140026

Summary: Spel Check in Open Office Takes 1 minute to respond on first spell check of any session
Product: [Fedora] Fedora Reporter: Charles Milhaus <cmilhaus>
Component: openoffice.orgAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3CC: john
Target Milestone: ---   
Target Release: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-12-15 16:07:13 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:

Description Charles Milhaus 2004-11-19 13:28:08 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041111 Firefox/1.0

Description of problem:
In Open Ofice writer, any time I am in a new session, and need to use
spell check; the initial invokation takes between 45 seconds and one
minute to respond. After this, it's fine, and it works well, but it's
always that first invokation of spell check that hangs, and hangs, and
hangs (or simply does not want to get started)(And it's ONLY in Fedora
Core 2 and 3

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

How reproducible:
Always

Steps to Reproduce:
1.type a word, and mispell this work

2.right click, to invoke spell check
3.wait, and wait
    

Additional info:

Comment 1 John Brown 2004-11-19 16:54:04 UTC
I too have experienced the same problem, I have also noted that while
openoffice is hung waiting for the first spell dialog to open,
openoffice is allocation a large ammount of memory in the background.
 Basically the memory allocated to openoffice jumps from about 84 Meg
to round 500 Meg.  Once OOffice has responded and produced the
spelling dialog the run away memory allocation stops however the
ammount of memory in use by OOffice never drops backdown again.

Comment 2 Sitsofe Wheeler 2004-11-22 17:32:59 UTC
(Especially comment #1) This sounds an awful lot like bug 137124 .
I've been ssh'd into the a machine which is reproducing this problem
with only 256M of memory and things get so far out of hand that the
OOM killer is brought in... It takes minutes for things to return to
normal after X dies...

Comment 3 Sitsofe Wheeler 2004-11-22 17:34:01 UTC
Oops that should be bug 136133 (137124 is a dup of that)

Comment 4 John Brown 2004-11-23 10:12:13 UTC
Yep looking a bug 136133 this does indeed seam to be the same bug.

Comment 5 Dan Williams 2004-11-30 02:43:26 UTC

*** This bug has been marked as a duplicate of 124374 ***