Bug 43074 - Libreoffice Writer 3.4 stops working when asked to display a particular string in Angsana New
Summary: Libreoffice Writer 3.4 stops working when asked to display a particular strin...
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected)
3.4.4 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Caolán McNamara
Depends on:
Reported: 2011-11-18 11:51 UTC by John Thomson
Modified: 2012-02-17 08:37 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Sample file which reproduces the problem when opened. (2.19 KB, application/vnd.oasis.opendocument.text)
2011-11-18 11:51 UTC, John Thomson

Note You need to log in before you can comment on or make changes to this bug.
Description John Thomson 2011-11-18 11:51:29 UTC
Created attachment 53675 [details]
Sample file which reproduces the problem when opened.

LibreOffice 3.4 fails to open the attached file; attempting to open it displays the OO main window but before displaying the document content it gives a message "Libre Office 3.4 has stopped working".

This file was not created by LO. It was originally exported from another program (SIL FieldWorks) and has been hand-edited to isolate the problem. The problem can also be reproduced by pasting the following string into LO Writer, selecting it, and setting the font to Angsana New: "chʉ̂ʉ" (don't include the quotes). I can't create a sample file in LO because as soon as I select this font for the given string the program stops working.

I have confirmed that this file opens normally in LO 3.3.3 and in MS Word. I have confirmed that it fails in 3.4.4 on both a desktop and laptop running Windows 7 Professional 64-bit. I know it fails on at least one other computer but don't know its specifications.

When re-opening the document, LO offers to recover it. If I attempt to do so, it tells me that a report of the crash was created and to click Next to get to the error report. However, when I click Next I don't see the report. Instead it attempts to open the document, tells me is is locked, and asks whether to open it read only or open a copy. Both options lead to crashing again, so I have not been able to get the crash report. Starting LO without opening a document gives a similar message, but in this case, it opens an empty document, but still does not give the promised crash report.
Comment 1 John Thomson 2011-11-18 11:55:44 UTC
It's probably necessary to have Angsana New installed to see the problem. I don't know where I got this, but it appears to be a Microsoft font. Properties indicates that it is a True Type font file, version 5.00, created on July 13, 2009 at 9:34:52.
Comment 2 sasha.libreoffice 2012-02-16 07:07:34 UTC
not reproduced crash in 3.3.4, 3.5.0 and 3.6.0 master on Fedora 64 bit
and in 3.4.2 on Windows XP 32 bit

@ John Thomson
This problems still exist?
Comment 3 John Thomson 2012-02-16 08:16:08 UTC
Still happens for me using LO 3.4.4 (build 402) on Windows 7 64-bit.

Did you confirm that you have the Angsana New font installed? I'm not sure where I got it, but found one version here: http://fontzone.net/font-details/Angsana+New/.

However, I was able to confirm that it does NOT happen with 3.5.0rc3, so it seems it has been fixed at some point.
Comment 4 sasha.libreoffice 2012-02-16 21:07:21 UTC
@ Caolan
Please, take look at this problem when will have time. Writer hangs with specific font
Comment 5 Caolán McNamara 2012-02-17 06:32:39 UTC
indeed, crashes 3.4.5, same font under Linux doesn't crash that
Comment 6 Caolán McNamara 2012-02-17 08:02:40 UTC
Works without a crash in libreoffice 3.5.0 under windows
Comment 7 Caolán McNamara 2012-02-17 08:04:16 UTC
given that it appears to work in 3.5.0 while it definitely crashed in 3.4.5 I'll tentatively call this fixed in 3.5.0. Can you try that version now and reopen this if it still crashes for you and my luck with 3.5.0 is coincidental.
Comment 8 John Thomson 2012-02-17 08:21:33 UTC
I'm not sure who you're asking to try it. As the original reporter I've already commented above that I tested it in 3.5.0rc3 and it is fixed there. Should I change the status to verified or closed? I'm not sure what your process is, but I am satisfied this is fixed. Thanks to whoever did it!
Comment 9 Caolán McNamara 2012-02-17 08:37:42 UTC
ah, missed that comment. Sure, no action required. I'm happy enough that its good in 3.5 and not worth investing time finding the fix for backporting to 3.4.6