Description: First day on a new install. I was editing a document while viewing Track Changes, with comments on and with deletions in margins. I had deleted some sentences, then changed my mind, and used several Undo (Command-Z) keystrokes. I then wanted to Redo one with Command-Y. The document scrolled down half a page and left me stuck there. I tried Command-Y again, then Command-Z. In the text the word !!br0ken!! appeared, after which the app crashed and restarted, recovering the file. When it recovered the file I was back where I should have been, but the clipboard text was lost, and the word !!br0ken!! had been saved in the document a page below. Also, the Review toolbar setting had gone back to showing all changes in line, not deletions in margins. When I deleted !!br0ken!! it was treated as text, and I see its deletion in the margins. I consciously tried to reproduce the bug. The result was similar - crash, recovered file, reset Track Changes to viewing all inline - but worse; LibreOffice hung and had to be Force Quitted, and the recovered file had large numbers of deletions I never made, both in my text and in another person's corrections. I had to get an old version from Dropbox. Steps to Reproduce: 1.Open a document with Track Changes and comments. 2.Set view to show deletions in margins. 3.Delete some text in several actions, either highlight-delete or keystroke. 4.Undo most of those deletions with Control-Z 5.Redo one with Control-Y Actual Results: LibreOffice Writer crashes, once neat enough to restart and recover, once forcing me to Force Quit Expected Results: Redo a text change Reproducible: Always User Profile Reset: No Additional Info: Version: 7.4.3.2 / LibreOffice Community Build ID: 1048a8393ae2eeec98dff31b5c133c5f1d08b890 CPU threads: 10; OS: Mac OS X 12.6; UI render: default; VCL: osx Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
BigTonyD, thank you for your bug report. Could you please retest with a clean user profile? Thank you. => NEEDINFO
Clean user profile fixed the bug.
(In reply to BigTonyD from comment #2) > Clean user profile fixed the bug. => RESOLVED NOTABUG