228783 - Crash while starting up XFT build with non-readable fonts [@ GetNormalLineHeight ]

Status: RESOLVED DUPLICATE of bug 183729

(Core Graveyard :: GFX: Gtk, defect)

Description

[Jens Hatlak (:InvisibleSmiley)]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.6b) Gecko/20031216 MultiZilla/1.6.0.0d
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.6b) Gecko/20031216 MultiZilla/1.6.0.0d

If you use TrueType fonts that are not readable by the user executing Mozilla
(XFT build) you'll experience a crash at startup but see no output at all.

Reproducible: Always

Steps to Reproduce:
1. Build XFT Mozilla
2. Edit chrome/userChrome.css (profile), add:
   * {font: 11pt Arial ! important;}
   (or any other TTF font)
3. Make sure the font used above is not readable by the user executing Mozilla
4. Start Mozilla (use strace if you like)
Actual Results:  
Mozilla crashes (exit code 11) because the font cannot be opened

Expected Results:  
Mozilla should start up

This may be connected to Bug 183729 but it's not the same since I built after
the fix for that bug went in.

I could supply strace output but I think this is clear. The most annoying about
this is that you don't know what's wrong unless you know how to use strace...

Comment 1

[Olivier Cahagne]

can you get a stack and attach it via "create a new attachment" ?

http://www.mozilla.org/unix/debugging-faq.html

if you're using the standard mozilla startup script, just do
% mozilla -g -d gdb
(gdb) run
[wait for mozilla to crash]
(gdb) bt
(attach the output from "bt" here)

Comment 2

[Jens Hatlak (:InvisibleSmiley)]

Attachment: bt output

The bt output requested - HTH

Comment 3

[Olivier Cahagne]

you'll probably to recompile a build with the debugging symbols to get a more
detailed stack unless someone can reproduce.

Comment 4

[Jens Hatlak (:InvisibleSmiley)]

I'll recompile and try again unless someone else can verify this - which should
be very easy for anyone with a debug- and XFT-enabled Linux build.

Comment 5

[Mats Palmgren (inactive)]

Dupe of bug 180309?

Comment 6

[Jens Hatlak (:InvisibleSmiley)]

Attachment: New stack using 22003-12-17 build with debug on

Next try, HTH

Comment 7

[Olivier Cahagne]

do you have Microsoft .fon fonts in your fonts directories ? Does deleting (or
archiving) them prevent from crashing ?

Comment 8

[Jens Hatlak (:InvisibleSmiley)]

I have no .fon files in any of the Linux fonts directories. The crash does not
happen if you simply make all .ttf files readable by the user executing Mozilla.

Comment 9

[Olivier Cahagne]

marking dupe since it's been reopened since.
Can you attach full stack trace in bug 183729 ?

*** This bug has been marked as a duplicate of 183729 ***