Created attachment 106114 [details]
Writer document that causes the problem
Problem description: When I try and replace the diamond symbol in this document with a diamond symbol with the font colour set to Orange, the replace hangs when recording changes is set on.
Steps to reproduce:
1. Copy the diamond symbol. Open the replace dialog (Ctrl-H) and put the diamond symbol into the Search and Replace boxes. Select other options and Format, change the Font Effects->Font Colour to Orange.
Ensure that Edit->Changes is set to Record.
2. Click 'Replace All'
3. The first dialogue window says do you want to shows changes to avoid delays. Click No.
System now hangs.
Current behavior: System hands and changes are not made. File needs to be recovered.
Expected behavior: Replacements work!
Operating System: Windows 8
Version: 126.96.36.199 release
I reproduce too with LO 188.8.131.52 Build ID: 958349dc3b25111dbca392fbc281a05559ef6848
& Windows 7 Home Premium.
I guess you set font color to red in the search part.
This happens only with Replace all. Result can be achieved by replacing esach occurence one by one without this crash.
I set status to NEW.
Thank you for the report,
Created attachment 106202 [details]
On pc Debian x86-64 with master sources updated today, I could reproduce the problem.
I attached console logs + a bt (I put a location where there's a loop, perhaps infinite loop?)
Also reproduced with LO 184.108.40.206, 220.127.116.11, 18.104.22.168.0+ Time: 2014-09-11_14:25:14 under Ubuntu 12.04 32bit
Created attachment 114518 [details]
The attached document contains a single "♦︎" (BLACK DIAMOND SUIT, U+2666 U+FE0E)
As in comment 0, with tracked changes enabled, replacing the "♦︎" with another "♦︎" formatted with a colour causes a hang.
Character selector led me up the garden path, the character is just U+2666 - but it seems it's not specific to that either. In fact, replacing anything with an added format while tracked changes are enabled seems to hang.
This also occurs all the way back to 3.3.0
-> Version: Inherited from OOo
...and finally, having generalised the problem, I see that there is an earlier duplicate
*** This bug has been marked as a duplicate of bug 65056 ***