TL/DR: indications of a transient Writer memory corruption issue. --- The word count for my document has become unreliable. I noticed that when I edited a comment, the word count changed (to 27,336 words and 154,625 characters, for what that information is worth). Clicking back into the main document, the word count and character count on the bottom status bar didn't change. Jumping to a point about 80% into the document, the numbers changed to 30,830 words and 175,405 chars. Saving the document refreshes the counts to the correct figures: 147,345 words and 847,090 characters. Clicking in and out of a comment at this point, and back into the current page, did not change the counts. Going to the end of the doc and clicking into a comment did not change the numbers. But adding a character and then backspacing to erase the character *did* change the numbers: to 27,336 words, 154,625 chars. Saving the doc refreshed the numbers to the correct values. Going back to my 80% mark, clicking into the comment, and adding a space did not change the numbers. Backspacing to delete the space in the comment did change the numbers: 26,720 words and 148,093 characters. Saving the doc refreshes the numbers to the correct values. This is weird and disturbing behaviour, especially the similar but different wrong numbers produced by adding and backspacing in a comment. In fact, I just added 5 spaces in a comment, and backspaced over them one by one. The wc/cc totals were: 58,105/332,749 (61,632/352,679) 64,133/367,116 (66,070/378,101) 68,893/394,301 (70,520/404,132) 79,828/457,565 (85,535/478,758) 89,954/516,853 (92,370/530,770) The pairs in the parentheses are what these numbers jumped to when I clicked into the comment after changing focus to this browser window to type in the numbers. I.e. the numbers jumped (once only) after changing focus back to the Writer doc, after adding to this bug report. More worrying still: exiting from the document and reopening it, this bizarre behaviour stopped. I suspect this means some Writer data structures had become corrupted. That's a very frightening thought. But I doubt this bug report will be useful as now *I* can't reproduce the problem myself.
Without a sample document where the issues clearly shows up it becomes extremely difficult to follow.
I agree. It also just started happening again, so I'm now installing LibreOffice_25.2.1.2. I'll see what happens.
Dear Luke Kendall, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
[Automated Action] NeedInfo-To-Unconfirmed