Bug 73054 - mozilla can crash metacity
Summary: mozilla can crash metacity
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: Xft
Version: 8.0
Hardware: i386
OS: Linux
medium
high
Target Milestone: ---
Assignee: Owen Taylor
QA Contact:
URL: http://1stline.com.br
Whiteboard:
Depends On:
Blocks: 67218
TreeView+ depends on / blocked
 
Reported: 2002-08-30 07:01 UTC by Alexandre Oliva
Modified: 2007-04-18 16:46 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-08-28 17:00:32 UTC
Embargoed:


Attachments (Terms of Use)

Description Alexandre Oliva 2002-08-30 07:01:54 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020826

Description of problem:
Browsing to http://1stline.com.br in mozilla causes metacity to crash.  It
restarts, but if mozilla is on a different virtual desktop, whenever you switch
to that desktop again, it crashes.  I haven't had the guts to see what happens
if mozilla is in the first virtual terminal.

Version-Release number of selected component (if applicable):
metacity-2.4.0.92-4
mozilla-1.0.1-22

How reproducible:
Always

Steps to Reproduce:
1.Browse to http://1stline.com.br in mozilla
	

Actual Results:  metacity crashes

Expected Results:  erhm...

Additional info:

Comment 1 Havoc Pennington 2002-08-30 22:20:41 UTC
Problem is Xft crashing on huge strings

Comment 2 Owen Taylor 2003-01-14 21:27:02 UTC
There might still be a problem with Xft and long strings, but the
length of the loong string is much longer, and I couldn't crash
metacity by setting enormous titles with gtk_window_set_title(),
which is what Mozilla uses.

Moving off target, since it is basically an item for upstream.


Comment 3 Owen Taylor 2003-08-28 17:00:32 UTC
Actually, the problem with much longer strings never actually existed 
for metacity. Pango never feeds Xft more than 1024 glyphs at a time.

I've filed it as:

 http://www.fontconfig.org/cgi-bin/bugzilla/show_bug.cgi?id=108

however, just so that the issue doesn't get forgotten.



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