Bug 80534 - mozilla (Xft enabled) crashes at some sites
mozilla (Xft enabled) crashes at some sites
Product: Red Hat Public Beta
Classification: Retired
Component: mozilla (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Christopher Blizzard
Ben Levenson
Depends On:
Blocks: 79579
  Show dependency treegraph
Reported: 2002-12-27 14:31 EST by Sarantis Paskalis
Modified: 2007-04-18 12:49 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-02-23 23:40:48 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sarantis Paskalis 2002-12-27 14:31:27 EST
Description of problem:

mozilla crashes without any indication at some sites (e.g.
http://news.com.com or http://www.zdnet.com).
This happens only with the Xft enabled builds of mozilla.  I have tried the
non-Xft builds, and they are working fine.

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. startup mozilla
2. go to http://news.com.com
3. mozilla crashes 
Actual results:

Expected results:

Additional info:
Comment 1 Sarantis Paskalis 2002-12-31 12:08:28 EST
I searched in the mozilla bugzilla for this bug, and it seems to be 

mozilla crashes if a .fon fontfile is in some font directory.  I removed the
.fon files, rebuilt the font list, and now mozilla does not crash anymore
consistently at these sites.  I don't know if there is a "correct" fix for it yet.

Comment 2 Warren Togami 2003-02-22 01:55:38 EST
One Xft bug in XFree86 was fixed a few days ago that fixed Bug #83354 which was
a Xft related crash in Mozilla.

You had mentioned that you found a potential fix for your problem and/or perhaps
your problem was fixed by the recent Xft patch.  This issue may be resolved.
Comment 3 Christopher Blizzard 2003-02-23 23:40:48 EST
Yeah, that's the same bug.  Closing since it's filed upstream.

Note You need to log in before you can comment on or make changes to this bug.