Bug 128123 - entire Writer App hangs up when spell checking runs and autosaving coincides with entering letters
Summary: entire Writer App hangs up when spell checking runs and autosaving coincides ...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) rc
Hardware: All macOS (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Spell-Checking-Dialog
  Show dependency treegraph
Reported: 2019-10-13 19:34 UTC by HTK300
Modified: 2022-01-20 19:40 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

screenshot of apple bug report initial section (166.68 KB, image/png)
2019-12-29 12:13 UTC, HTK300

Note You need to log in before you can comment on or make changes to this bug.
Description HTK300 2019-10-13 19:34:14 UTC
When I go through large files of 50 A4 pages and up, using the Spelling feature, it may take sometimes over 20 Minutes for me to have all phrases being reviewed. Incidently, when I enter and correct spellings at my own will - and the autosaving feature jumps in, the Writer app hangs-up. Very frustrating, because the spelling corrections that I have done so far has to be done again, the file that was open is the corrupt and has to be repaired.
Comment 1 Julien Nabet 2019-10-15 18:00:38 UTC
It might be a dup of tdf#128138 put in See Also and which is fixed from next release version 6.3.4.
Comment 2 Michael Stahl (allotropia) 2019-10-16 08:29:13 UTC
bug 128138 must be unrelated because attribute search is a really obscure feature, but maybe this fixed it:

commit 7a12cd31d5057fb268e6faa47a4c65209a267617
Author:     Michael Stahl <Michael.Stahl@cib.de>
AuthorDate: Tue Sep 17 19:34:01 2019 +0200
Commit:     Caolán McNamara <caolanm@redhat.com>
CommitDate: Wed Sep 18 21:59:11 2019 +0200

    cui: infinite loop in SentenceEditWindow_Impl::MarkNextError()
    Looks like previously the aCursor never moved backwards so try to ensure
    the same for nCursor.
    (regression from 5261417cbb3051b812164838d19c0f748573df45)

... although it has nothing to do with auto-save so maybe it's a different problem.
Comment 3 Alex Thurgood 2019-10-24 07:33:48 UTC

without a sample document, it is going to be difficult to reproduce this. Any chance of you providing one that we could test with ?
Comment 4 Alex Thurgood 2019-10-24 07:37:46 UTC
@HTK300 : it might also be fixed as Michael Stahl has mentioned in comment 2, so you should give LO633 pre-release a try and see if that solves the issue for you, then report back here.
Comment 5 HTK300 2019-12-04 13:41:12 UTC

just coming back to let you guys know, I have given up using this version Writer LO 6.3.3 unil the new version is available. So far I am doing fine with 6.2.8 no problems at all. 


Comment 6 QA Administrators 2019-12-05 04:27:37 UTC Comment hidden (obsolete)
Comment 7 HTK300 2019-12-07 16:37:28 UTC
haven't been testing the reportet version 6.3.3 lately, because too annoying when it crashes. Working with 6.2.8 has no problem in this respect, at all.

I´ve changed the component to WRITER, that's where it occurred - sorry, my bad.

Comment 8 Dieter 2019-12-10 07:30:29 UTC
Sounds like a problem, that was reported in bug 128074. But it works in 6.3.3. HTK, so please test with a version 6.3.3 or newer if it will be available.

Comment 9 HTK300 2019-12-10 14:19:26 UTC
Hallo Dieter P.

I have been testing this bug with LO 6.3.4 ! and haven't encountered a situation during spell checking of huge Writer files 500 pages. I could not test it with previous version 6.3.3 because that version was not able to accept german keyboard entries (other than US, even German was indicated) of my own. See [Bug 128104] macOS.

So, looks good & worksforme

Comment 10 Julien Nabet 2019-12-10 14:24:47 UTC
Thank you for your feedback.
Let's put this one to WFM then.
Comment 11 HTK300 2019-12-29 12:09:19 UTC

I had again incidents of this crash, twice. I my perception is, that the cause may be related - as described in the headline - to the autosaving in the background and simultaneously entering corrections to the red highligted spelling typo found by the spell checker dialog window.

I had 3 Writer documents open *each of them at least over 100 A4 pages long, and one Calc file.

The fist occurrence of this crash incident I thought was related to the APP Dr. Cleaner which organizes the occupation of low internal memory. The second occurrence of this crash though happened without Dr. Cleaner running in the background.
Comment 12 HTK300 2019-12-29 12:13:04 UTC
Created attachment 156833 [details]
screenshot of apple bug report initial section
Comment 13 HTK300 2019-12-29 13:00:54 UTC
may I advice to increase the severity/importance to a higher level?

It is annoying trying to figure out, what had been autosaved so far in the process of spell checking. My Spell checking interactions may take up to 20/30 minutes or more, which means several autosaving must have been taken place in the background. But When I recover the documents It seams that the spelling I modified so far and prior to the crash are not autosaved/recovered. the default autosave interval is set to 12 minutes, meaning there a three chances to coincide with saving and entering modifications to spellings within this time frame in my case
Comment 14 Xisco Faulí 2020-01-20 11:59:27 UTC
You can't confirm your own bugs. Moving it back to UNCONFIRMED until someone
else confirms it.
Comment 15 Ahmad Haris 2020-02-19 02:10:07 UTC
Hi, can you attach the sample document?
Comment 16 Dieter 2020-02-19 10:07:20 UTC
(In reply to Ahmad Haris from comment #15)
> Hi, can you attach the sample document?

Comment 17 HTK300 2020-02-19 10:15:42 UTC
Hi all,
I am not using LO anymore. The latest release seems to have fixe that so for no more occurrences about this bug.
I am currently using WRITER and it works fine.
The file I have been working on is very private, has over 500 pages, 
I am using a MacBook High Sierra, only 6 GB RAM. (hope this helps)

Comment 18 Dieter 2020-02-19 10:25:56 UTC
(In reply to HTK300 from comment #17)
> Hi all,
> I am not using LO anymore. The latest release seems to have fixe
> that so for no more occurrences about this bug.
> I am currently using WRITER and it works fine.