I've had this come up on 3 occasions now. The first 2 times, Firefox would just crash (reproduceable until I cleared saved form data). The most recent time, it hung when autocompleting something on a web site, preventing any input from reaching other X apps (numlock still worked, mouse still moved around, xmms was still moving its spectrum analyzer, I just couldn't click on anything or give keyboard input to anything, including fluxbox). Retrying this after killing X (keyboard input to X itself obviously worked, as I could switch back to vc1 and ctrl-c to kill X somewhat politely) resulted in only firefox hanging. Unfortunately, I cleared the data before deciding to submit this bug. This has happened w/ various 0.8 and 0.9 versions, with both -bin and normal versions. Reproducible: Always Steps to Reproduce: 1. start typing in whatever the broken autocomplete data is associated with 2. 3. Actual Results: firefox hangs or crashes Expected Results: firefox doesn't hang Portage 2.0.51_pre13 (gcc34-amd64-2004.1, gcc-3.4.1, glibc-2.3.4.20040619-r0, 2.6.7-gentoo-r8 x86_64 5) ================================================================= System uname: 2.6.7-gentoo-r8 x86_64 5 Gentoo Base System version 1.5.1 Autoconf: sys-devel/autoconf-2.59-r4 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.91.0.1-r1 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aac aim alsa amd64 apm avi berkdb cddb cdr crypt cups dvd dvdr encode fbcon flac foomaticdb gdbm gif gimpprint gpm gtk gtk2 imap imlib javascript joystick jpeg kerberos libg++ libwww mad mikmod motif mozilla mpeg ncurses nls oggvorbis opengl oss pam pdflib perl png python quicktime readline sdl slang spell ssl tcpd threads tiff truetype xml2 xmms xv xvid zlib ~arch"
Sorry, should have clarified. I had this problem while running x86 (athlon-xp) Gentoo on this machine, too.
No amd64 bug, see Comment #1. Reassigning to bug-wranglers.
shoulda just reassigned to amd64
Again, this is not an amd64-specific bug. I was experiencing problems when running an IA32 (athlon-xp) installation on this machine.
Hi, Few days ago, I found this bug http://bugzilla.mozilla.org/show_bug.cgi?id=248442 on mozilla's bugzilla. I applied the patch, and 'til then, I didn't had any crashes of my beloved Firefox :-)
Hm sounds good. I did however have the same problem (albeit with 0.8) running an athlon-xp setup on this same hardware. I'm still kicking myself for *not* backup up my ~/,mozilla and ~/.phoenix dirs before fixing the problem this last time. Hopefully it comes back soon :/ Of course, there's no clear mention as to whether the patch prevents the behavior or the creation of the condition which causes the behavior, making a recurrence of the problem potentially useless as a test for this patch. OTOH, it's only happened 3 times in the last 6 months, so I'll just wait for it to make its way into Portage and see if it breaks ever again, I suppose. Thanks again!
Yay, it broke again! (yes, I'm odd.) Gonna go try the patch...
recompile + no clean-out of saved form data fixed it, so this patch does indeed solve the problem even after the problematic form data exists.
Having looked into this a bit more I would have to say that what I experienced before was isolated to 0.8* so all of my 0.9* problems COULD have been isolated to amd64 (which is exactly what the patch fixes).
uhhh... i just fixed this bug and had no idea there was an open bug report about it. and yes, this is isolated to 64bit machines only. everyone sync up and re-emerge mozilla firefox 0.9.1. if any of you are on x86 with 0.9, then you're probably seeing a different problem...
