Mailing-List: contact ooo-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-issues@incubator.apache.org
From: bugzilla@apache.org
To: ooo-issues@incubator.apache.org
Subject: [Bug 120329] New: OOO Crashes whilst Spell Check is active
Date: Fri, 20 Jul 2012 09:57:53 +0000
Message-ID: <bug-120329-248469@https.issues.apache.org/ooo/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Auto-Submitted: auto-generated
MIME-Version: 1.0

https://issues.apache.org/ooo/show_bug.cgi?id=120329

          Priority: P3
            Bug ID: 120329
          Assignee: ooo-issues@incubator.apache.org
           Summary: OOO Crashes whilst Spell Check is active
          Severity: normal
        Issue Type: DEFECT
    Classification: Application
                OS: Windows XP
          Reporter: shieldlp@earthlink.net
          Hardware: PC
            Status: UNCONFIRMED
           Version: AOO 3.4.0
         Component: editing
           Product: word processor

I use four dictionaries in my configuration OOO wp.

When spell checking a large document -- 200-600 pages -- the OOO system crashes
and begins to recover the document. None of the changes to any of the
dictionaries
are saved and the entire process begins again. Often the system crashes again
at the same word/place in the document.

Making document saves every 5-10 changes, closing the document and reloading
has somewhat ameliorated the situation, but not always.

Recently I began splitting documents into 100 page sections, but this is no
real answer.

My documents are usually created with MS Word 11. When I begin to check
spelling I save the document to an odt format and work from that.

Looking at the structure of OOO, I infer that the software is created under an
operating system other than Windows. I also infer that the actual "operating"
program is contained in the soffice.bin and the soffice.exe handles the
interface to the Windows operating system. I believe the issue is a timeout
problem between the two files. That being said, I increased the priority of
soffice.bin higher than soffice.exe. Perhaps this is backwards. I would
appreciate any input offered.

The problem improved after upgrading to 3.4. Alas, it still exists.

Any ideas would be greatly appreciated.

-- 
You are receiving this mail because:
You are the assignee for the bug.