Created attachment 112978 [details]
Steps to reproduce:
1. Copy contents of 'crash_string.txt'.
2. Open Draw.
3. Create text box.
4. Paste previously copied text.
Microsoft Visual C++ Runtime Library
Expression: mnSubStringMin <= rVisualItem.mnEndCharPos
Created attachment 112979 [details]
On pc Debian x86-64 with master sources updated 2 days ago, I don't reproduce this.
Windows only bug?
Yes, you are right.
Actually, this can be understood looking at the file name:
Could not reproduce.
Win 7 Pro 64-bit Version: 188.8.131.52.alpha0+
Build ID: 309574394bd4ae3e9e10e5ff0d64bdd7bbbc8b83
TinderBox: Win-x86@62-TDF, Branch:MASTER, Time: 2015-01-29_23:44:46
I can not confirm with Version: 184.108.40.206.alpha0+
Build ID: 20deac4903fc0697477e855feeff482b3da234f9
TinderBox: Win-x86@42, Branch:master, Time: 2015-01-29_23:02:41
I tried copy string from notepad and internet explorer.
Created attachment 113014 [details]
Here is the simplified version of the problematic string.
It consists of three characters: U+05DD, U+006F, U+05EA.
Now on my test systems (Win7 x64 SP1, Win10 x64 9926) it crashes even LO.Writer.
Please recheck with this link:
Looks like different tinderboxes produces different results.
Yep, reproduced with
Build ID: 4b9a9ce8a0e5e0716dad9a9ec87d16237e534dc2
TinderBox: Win-x86@39, Branch:master, Time: 2015-01-31_09:49:44
But this is a dupe.
*** This bug has been marked as a duplicate of bug 67601 ***