215132 - crash when I load http://www.flipcode.com

Status: RESOLVED DUPLICATE of bug 183729

(Core Graveyard :: GFX: Gtk, defect)

Description

[Nick Monkman]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030714 Debian/1.4-2
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030714 Debian/1.4-2

Nothing too complicated here. When I point the browser to
http://www.flipcode.com, the browser crashes. Same thing for
http://www.seattlemariners.com. This also occurs in two other Gecko-based
browsers I've tried, Galeon and Epiphany.

Reproducible: Always

Steps to Reproduce:
1. Type "http://www.flipcode.com" in the navigation input bar
2. Watch the page start to load
3. Note browser crash

Actual Results:  
The page generally starts to load (progress bar increments, page becomes blank)
then the browser window disappears and the app appears terminated. In
gnome-based browsers, the friendly GNOME crash message appears

Expected Results:  
Mozilla should have correctly displayed the page, as in previous versions

I'm running Debian Sid.

Comment 1

[Bill Mason]

flipcode.com WFM 20030729 PC/WinXP

seattlemariners.com crashes, but for me that may dup the Windows-only bug 213390
(from bug 213453).  My Talkback for crash: TB22490542H

Comment 2

[Mark Phillips]

I am running Solaris Mozilla 1.4, and its ok for me.
I would guess at a plugins issue, probably Flash. I tried with and without Fash,
but on Solaris we only have a very old release available.

Try visiting without any plugins (check about:plugins and the plugins dirs).

Comment 3

[Mitch]

Works fine for me. Linux with moz cvs 20030802 - gtk2 based. All plugins
enabled.

Reporter, please provide a useful stack trace from your crash.

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

Comment 4

[Andrew Schultz]

> Reporter, please provide a useful stack trace from your crash.

Debian builds are stripped, so the stack isn't going to be that useful.

this is probably another xft problem.
Nick: can you verify that all of your ttf fonts are world-readable?
if you start Mozilla from a terminal, does it print any message when it crashes?

Comment 5

[Nick Monkman]

Oops sorry...GDB is a bit new to me.  Here's what I could come up with

0  0x4069bf73 in XftLockFace () from /usr/X11R6/lib/libXft.so.2
#1  0x412b19f6 in nsFontMetricsXft::CacheFontMetrics() () from
/usr/lib/mozilla/components/libgfx_gtk.so
#2  0x412b19aa in nsFontMetricsXft::RealizeFont() () from
/usr/lib/mozilla/components/libgfx_gtk.so
#3  0x412b12aa in nsFontMetricsXft::Init(nsFont const&, nsIAtom*,
nsIDeviceContext*) () from /usr/lib/mozilla/components/libgfx_gtk.so
#4  0x4093a947 in nsFontCache::GetMetricsFor(nsFont const&, nsIAtom*,
nsIFontMetrics*&) () from /usr/lib/libgkgfx.so
#5  0x40939bf3 in DeviceContextImpl::GetMetricsFor(nsFont const&, nsIAtom*,
nsIFontMetrics*&) () from /usr/lib/libgkgfx.so
#6  0x412927b0 in nsRenderingContextGTK::SetFont(nsFont const&, nsIAtom*) ()
from /usr/lib/mozilla/components/libgfx_gtk.so

...long chain of NSGetModule calls into libgklayout.so (about 100)

then
#119 0x408bd943 in PL_HandleEvent () from /usr/lib/mozilla/libxpcom.so
#120 0x408bd85d in PL_ProcessPendingEvents () from /usr/lib/mozilla/libxpcom.so
#121 0x408be91e in nsEventQueueImpl::ProcessPendingEvents() () from
/usr/lib/mozilla/libxpcom.so
#122 0x410aee02 in NS_GetSpecialDirectory(char const*, nsIFile**) () from
/usr/lib/mozilla/components/libwidget_gtk2.so
#123 0x40472cf7 in g_vsnprintf () from /usr/lib/libglib-2.0.so.0
#124 0x404561bb in unblock_source () from /usr/lib/libglib-2.0.so.0
#125 0x404570ad in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#126 0x404573af in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#127 0x404579de in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#128 0x401cda77 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#129 0x410af19c in nsAppShell::Run() () from
/usr/lib/mozilla/components/libwidget_gtk2.so
#130 0x41082cb6 in NSGetModule () from /usr/lib/mozilla/components/libnsappshell.so
#131 0x08057b6a in getCountry(nsAString const&, nsAString&) ()
#132 0x08058340 in main ()
#133 0x4057ba51 in __libc_start_main () from /lib/libc.so.6
#134 0x08054699 in _start ()

This does indeed look like some kind for gtk/xft font rendering madness. I'll
check my ttf readability. There is not output from the console.

hope that helps...let me know if I can provide anything else

thanks

Comment 6

[Nick Monkman]

Well what do you know, my Tahoma and Tahomabd fonts were only user-readable
(only two that were for some reason). Works fine now...thanks for the help. Want
me to find the dupe (I'm assuming there is at least one) and close it out, or is
that someone else's job?

Thanks a lot for your help.

Comment 7

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

->Gtk

Comment 8

[Andrew Schultz]

dupe of "Segmentation fault in XftLockFace (.ttf files need to be world-readable)"

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