Closed Bug 229860 Opened 20 years ago Closed 18 years ago

odd glyphs crashes window


(Core :: Layout: Text and Fonts, defect)

Not set





(Reporter: fr, Unassigned)



(Keywords: crash, stackwanted)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 Firebird/0.7

Some strange symbols might crash the window at rendering. This happens in
Mozilla 1.5 and Firebird 0.7 +gtk2 +xft on Gentoo 1.4 linux kernel 2.6 gnome 2.4

Reproducible: Always

Steps to Reproduce:
1. copy this text in a text file
 i r c . e r oRAW:  l s . c o m i r c . e r oRAW:  l s . c o mi r c . e r
oRAW:  l s . c o m i r c . e r oRAW:  l s . c o m

Actual Results:  
mozilla window crash

Expected Results:  
not to crash :)

It's not usual to have this kind of characters, but it could be used to crash
user application
this should be fixed with either 1.6b or latest Firebird + XFT (which you can try
easily since it's a simple tarball, no deps needed):

Possibly dupe of bug 213734.

If still crashing, can you get a stack and attach it via "create a new attachment" ?

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)

do you have Microsoft .fon fonts in your fonts directories ? Does deleting (or
archiving) them prevent from crashing ?
Otherwise, do you have non-readable (with current user) TTF fonts ?
Blocks: xft_tracking
Severity: normal → critical
Keywords: crash, stackwanted
do you crash with 1.7rc2 ?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Tested on Firefox 1.5 Beta 1, working great.
Closed: 18 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.