Issue 106551 - Slow responce of Writer when firest click on incorrectly spelled word
Summary: Slow responce of Writer when firest click on incorrectly spelled word
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: OOo 3.0.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-02 12:05 UTC by annulen
Modified: 2013-08-07 14:38 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description annulen 2009-11-02 12:05:23 UTC
When user right clicks on underlined incorrectly spelled word (to correct it or
ignore) first time in session, Writer responds slowly (especially on low-end
hardware). If user immediately clicks another word, Writer responds fast, but if
user edits text, another time Writer also responds slowly
Comment 1 michael.ruess 2009-11-02 14:43:50 UTC
I guess, Linguistic related libraries have to be loaded and dictionaries have to
be read from the HD when the first call of the auto spelling context menu is
performed.

MRU->TL: is there any space for improvement in this area?
Comment 2 thomas.lange 2009-11-03 09:44:21 UTC
Hardly because the problem description is somewhat vague.
Indeed the very fist time a new dialog/menu/... is opened the respective
resources and/or libraries are loaded on demand. But that applies only once and
after that it should be fast.

Thus the only reason for it being slow should be that the actual spell checking
for the current word may be slow. I don't know about the internals of the spell
checker implementation thus it also could be possible that it implements a very
small cache for already checked words. Thus words that are already checked once
and are still found in the cache would yield fast responses whereas other words
would give slower responses.

Also if the memory is very limited it might be possible that required memory is
constantly swapped in and out. 

Thus without having a machine to reproduce the behavior it is hard to guess
about anything. 

TL->MRU: Do we have a machine where this type of problem can be reproduced?

TL->annulen: Can you give more details about your machine? For example CPU type
clock speed and available memory as a reference?
Comment 3 annulen 2009-11-03 10:28:02 UTC
Celeron 566 MHz (Coppermine), 256 MB RAM