[Libreoffice-bugs] [Bug 112180] Writer crashes with TTF font installed

bugzilla-daemon at bugs.documentfoundation.org bugzilla-daemon at bugs.documentfoundation.org
Sun Sep 3 02:25:52 UTC 2017


https://bugs.documentfoundation.org/show_bug.cgi?id=112180

V Stuart Foote <vstuart.foote at utsa.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |chris.sherlock79 at gmail.com,
                   |                            |khaledhosny at eglug.org,
                   |                            |markus.mohrhard at googlemail.
                   |                            |com, vstuart.foote at utsa.edu
     Ever confirmed|0                           |1

--- Comment #2 from V Stuart Foote <vstuart.foote at utsa.edu> ---
Confirming on Windows 10 Pro 64-bit en-US with
Version: 5.4.1.2 (x64)
Build ID: ea7cb86e6eeb2bf3a5af73a8f7777ac570321527
CPU threads: 8; OS: Windows 6.19; UI render: GL; 
Locale: en-US (en_US); Calc: group

and on recent master
Version: 6.0.0.0.alpha0+
Build ID: 9d4fc496d498f2f5c7fedba94f656ef3189b85dd
CPU threads: 8; OS: Windows 6.19; UI render: GL; 
TinderBox: Win-x86 at 39, Branch:master, Time: 2017-09-02_23:59:12
Locale: en-US (en_US); Calc: CL

It is not linked to the FontPreview droplist--bug 106265, there is no movement
of GDI count. And Tools -> Options -> View: unchecking "Show preview of fonts"
has no effect on the immediate "Bad allocation" crash. Likewise, the Sidebar
Properties -> Character content panel drop list, the Special Character dialog,
and the Character dialog Font tab preview all will crash LO when the font is
selected. So no GDI overflow.

Rather, the font itself seems to be rather badly broken. Suspect there is some
invalid/illegal Unicode mapping. In fact, if I use FontCreator and export the
font into a PUA Symbol font it is handled without issue in all locations of the
UI.

Unclear the origin of the font, but it seems to be a MS Symbol encoded font
that was converted to Unicode--just badly.  Would say NOTOURBUG, but the crash
here is a little disconcerting, seems we should be more graceful about it.
Also, this Windows crash is not kicking off the mini-dump needed for
crashreport.


Khaled, Chris?

Markus--fyi on this crash not triggering the minidump/crashreport.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice-bugs/attachments/20170903/c823bc3c/attachment-0001.html>


More information about the Libreoffice-bugs mailing list