Bug 106173 - EDITING: Opening the context menu on red squiggly underlined word in LibreOffice takes several seconds
Summary: EDITING: Opening the context menu on red squiggly underlined word in LibreOff...
Status: RESOLVED DUPLICATE of bug 105426
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2017-02-24 11:06 UTC by jhertel
Modified: 2017-02-24 11:46 UTC (History)
0 users

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description jhertel 2017-02-24 11:06:40 UTC
When a word has a red squiggly line under it (meaning the spelling cannot be recognized by the spell checker) and I right click it (or place the cursor inside the word and press the context menu key), it takes 3-7 seconds every time before the context menu is displayed, if the word is "formatted" as Danish. If the word is "formatted" as English (USA), it takes 1-2 seconds (still consistently). 

Here are some specifics: I tested with the word "Lisp-agtigt" (which is a valid Danish word), marked as Danish, and that gives response times at around 5 to 7 seconds; if I test with a gibberish word "slfiouw", again marked as Danish, the context menu comes up after 3 seconds.

It should go without saying that this is annoying as it stops you in the process of writing; you just want to add the valid word to the dictionary but have to wait up to 7 seconds to do that. The display of the context menu ought to be instantaneous, of course, or at least under 500 ms or so.

I would like to give a list of installed extensions, in case one of them could be the culprit, but I don't know how. Anyhow, I only have extensions that came bundled with LibreOffice. And there is no obvious way to disable them via the user interface, so I can't try disabling them to see if that solves the problem.

I am not able to compile LibreOffice myself to do any debugging, as there are no functional instructions on how to do that successfully and consistently on Windows. I have spent days earlier trying to compile but had to give up in the end.

I am not using as it has a major bug (Bug 105844) that prevents me from using it.
Comment 1 Caolán McNamara 2017-02-24 11:46:40 UTC

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