mozilla hangs with 100% cpu usage on that url

RESOLVED INVALID

Status

SeaMonkey
General
--
critical
RESOLVED INVALID
15 years ago
13 years ago

People

(Reporter: Arwed von Merkatz, Assigned: asa)

Tracking

({hang})

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686) Gecko/0 Galeon/1.3.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686) Gecko/0 Galeon/1.3.3

mozilla reproducably hangs on the release notes of mozilla 1.4a
That also happens for other pages, but that's the one i remember.

This is a gtk2 mozilla 1.4a with xft enabled. Happens in mozilla, galeon and
epiphany.

Reproducible: Always

Steps to Reproduce:




This is a gtk2 mozilla 1.4a with xft enabled. Happens in mozilla, galeon and
epiphany.
(Reporter)

Comment 1

15 years ago
Created attachment 119335 [details]
gdb backtrace

i ran mozilla in gdb and suspended it when it hang, then did a backtrace
not sure if that gives any usable info, if you want me to do something else to
produce a more usable trace, please tell me.

Comment 2

15 years ago
what build options did you use?
Keywords: hang
(Reporter)

Comment 3

15 years ago
my build options:
CFLAGS='-march=athlon -mmmx -m3dnow -O3 -z combreloc'
CXXFLAGS=CFLAGS

configured with
--prefix=/usr
--with-x
--with-pthreads
--enable-xft
--enable-reorder
--enable-strip
--enable-optimize="$CFLAGS"
--disable-debug
--disable-tests
--disable-installer
--enable-crypto
--disable-mailnews
--disable-chat
--with-system-zlib
--with-system-jpeg
--with-system-png
--with-system-mng
--enable-toolkit-gtk2
--enable-default-toolkit=gtk2
(Reporter)

Comment 4

15 years ago
Sorry for the false alarm, seems to have been my system.
I'm not exactly sure what solved the problem, but it's gone now. I upgraded
freetype2 to 2.1.4 and fontconfig to 2.1.94 and installed the newest bitstream
vera fonts.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → INVALID
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.