Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | openoffice crashes with these fonts | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Writer | Reporter: | Unknown <non-migrated> | ||||||||||
Component: | ui | Assignee: | hdu <hdu> | ||||||||||
Status: | CLOSED IRREPRODUCIBLE | QA Contact: | issues@sw <issues> | ||||||||||
Severity: | Trivial | ||||||||||||
Priority: | P2 | CC: | issues | ||||||||||
Version: | OOo 1.0.1 | Keywords: | oooqa | ||||||||||
Target Milestone: | --- | ||||||||||||
Hardware: | PC | ||||||||||||
OS: | Linux, all | ||||||||||||
Issue Type: | DEFECT | Latest Confirmation in: | --- | ||||||||||
Developer Difficulty: | --- | ||||||||||||
Attachments: |
|
Description
Unknown
2002-09-11 23:24:57 UTC
Created attachment 2822 [details]
Metrics file for the font Sumdumgoi
Created attachment 2823 [details]
Font Sumdumgoi
Created attachment 2824 [details]
Font Burgundian
Can you give us a stack dump of the crash happening in OOo1.1beta2? See http://kegel.com/openoffice/#dump (or wait for OOo1.1rc1, which will have a built-in crash logger) Thanks! I'm adding the "oooqa" keyword & setting the priority to P1 from P3. I see that the version is 1.0.3. Would you be willing to upgrade to see if a new version works better? Reassigned to Ulf. No reporter-activity for months No votes No other one who confirmed the problem I think we should close that issue as WFM, if someone still sees the problem, the issue can be reopened If I will not see any further action as votes, attachments or confirmations in this issue, I will have to close this issue 2003-08-31 as WFM. Rainer Created attachment 8014 [details]
font metrics for Burgundian
Sumdumgoi does not crash OOo in current inhouse version (srx645_m14s1.8665), but Burgundian does. Test: formatted a dummy text with the font. Created afm file for Burgundian with pf2afm (GNU Ghostscript 6.51). Attaching bu_____.afm file for easier reproduction. @ RainerBielefeld: pls. be patient or better reproduce the issue and confirm it. Thx. @ Eugene T.S. Wong: you see promoting the Prio does not help. Only reproducing and confirming an issue *does* matter. BTW: P1 is inappropriate. Crashes are P2. P1 is for severe damage caused by OOo. Example: OOo would remove user's home directory on deinstall, or the like. Thanks for contributing OOo anyway, guys! pl->us: P1 was perfectly right when the issue was created ;-) pl->hdu: no crash in 645m14; but it seems that freetype doesn't like to render that font (please note the less than perfect behaviour in normal as well as in online view). pl->hdu: i have to correct myself; burgundian does crash as Ulf reported. It does so somewhere inside FreetypeServerFont Crash in Freetype: #0 in ps2_hints_apply () #1 in ps3_hints_apply () #2 in RepadBitmap () #3 in gray_raster_render () #4 in gray_raster_render () I'll look if the the crash in the FT lib is low hanging fruit... Freetype's demo applications font checker FTLINT also doesn't like these fonts: "ftlint 20 bu______.pfb" results in a Segmentation fault at glyph 29 (probably due to memory overwrite in t1_decoder_parse_charstrings() "ftline 20 sumdumgo.pfb" tells us that glyphs 28 and 54 fail The two solutions are: - fixing the fonts - make freetype's type1 hinter handle problematic fonts more gracefully HDU->US: ok to close? us->hdu: could you pls. submit a bug against FreeType. A crash is always unpleasant from user's perspective. And a solid freetype seems to be desireable for any application, nut just OOo. Furthermore, I am convinced that as long as I live there will be broken fonts gathering around :-( @submitter: would you pls. log a bug against debian to not include this broken font? Thanks, a lot. Just an idea, but if OpenOffice crashes when using bad/corrupted fonts, shouldnt we at least make OpenOffice handle this gracefully ? The fact that it's the fault of the font and not of OpenOffice wont matter a bit to the average end-user. For example, stop OpenOffice from loading the font if it does not like it and display an error message for the user instead of just dumping core ? Just my 2$... I agree that OOo shouldn't crash if a library we are based upon like glibc or libfreetype crash or when the OS dies or when RAM got bad. Unfortunately this is much easier said than done. Not using fonts that crash freetype is also difficult, because it is not known in advance which fonts these would be and it is extremely dependend on the version and options of the system freetype. If every app that uses the font through the same libfreetype crashes too it is best to remove the font or to upgrade to a freetype version that doesn't have the problem with the font. Freetype version 2.1.5 doesn't crash on Burgundian anymore. . Works for me when using freetype 2.1.5 Closing. |