Another FF3 Freeze when very overloaded

Bug #243664 reported by David Grossberg
2
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: firefox-3.0

This is another apport report like bug 240573 - but I am using the official package now.
Version 3.0+nobinonly-0ubuntu0.8.04.1 and run with --sync
(Still using Tab Mix Plus to keep a very large session open)

Terminal output:

The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadIDChoice (invalid resource ID chosen for this connection)'.
  (Details: serial 988606919 error_code 14 request_code 53 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
Locking assertion failure. Backtrace:
#0 /usr/lib/libxcb-xlib.so.0 [0x7fbfff03497c]
#1 /usr/lib/libxcb-xlib.so.0(xcb_xlib_lock+0x15) [0x7fbfff034a15]
#2 /usr/lib/libX11.so.6 [0x7fc00125f323]
#3 /usr/lib/libX11.so.6(XFreeCursor+0x1a) [0x7fc00123b8ba]
#4 /usr/lib/libqt-mt.so.3(_ZN11QCursorDataD1Ev+0x3a) [0x7fbff7079d4c]
#5 /usr/lib/libqt-mt.so.3(_ZN7QCursorD1Ev+0x5b) [0x7fbff7079f5d]
#6 /usr/lib/libqt-mt.so.3 [0x7fbff7079f9a]
#7 /lib/libc.so.6(exit+0xe0) [0x7fc005974110]
#8 /usr/lib/libgdk-x11-2.0.so.0 [0x7fc0005cc8e1]
#9 /usr/lib/libX11.so.6(_XError+0xed) [0x7fc001258b6d]
#10 /usr/lib/libX11.so.6 [0x7fc00125fc1a]
#11 /usr/lib/libX11.so.6(_XReply+0x165) [0x7fc00125ffa5]
#12 /usr/lib/libX11.so.6(XSync+0x6a) [0x7fc0012548aa]
#13 /usr/lib/libX11.so.6 [0x7fc001254a4b]
#14 /usr/lib/libX11.so.6 [0x7fc0012602db]
#15 /usr/lib/libX11.so.6(XCreatePixmap+0xbe) [0x7fc001236bee]
#16 /usr/lib/libcairo.so.2 [0x7fc0027955db]
#17 /usr/lib/libcairo.so.2 [0x7fc0027977b6]
#18 /usr/lib/libcairo.so.2 [0x7fc00276ccea]
#19 /usr/lib/libcairo.so.2 [0x7fc0027717da]

ProblemType: Bug
Architecture: amd64
Date: Fri Jun 27 19:53:52 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/firefox-3.0/firefox
NonfreeKernelModules: nvidia
Package: firefox-3.0 3.0+nobinonly-0ubuntu0.8.04.1
PackageArchitecture: amd64
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: firefox-3.0
Uname: Linux 2.6.24-19-generic x86_64

Tags: apport-bug
Revision history for this message
David Grossberg (davidgro) wrote :
Revision history for this message
David Grossberg (davidgro) wrote :

I forgot to mention, this bug (and bug 240573 ) left Firefox using 100% of one CPU core - which due to the process and thermal management switching the thread around meant 25% of each of my four cores on average.

Revision history for this message
David Grossberg (davidgro) wrote :

Bug 246163 is a similar freeze, which did not leave it in 100% CPU and had a different backtrace.

Revision history for this message
DarkStar (darkstarmail) wrote :

I have similar problems. I have a bunch of tabs open as well as 4 to 6 firefox windows open with 14 or more tabs open in each firefox. This machine worked perfectly with Ubuntu 8.04 and Firefox 3.0.4 and I never had any problems except for firefox just closing all windows after it had run for 5 or 6 days. I would just restart firefox and restore the session. However since I updated to Ubuntu 8.10, same machine, same hardware memory etc. Firefox locks up and you cannot do anything but 'killall -I firefox' and then restart it. But worse yet is that after firefox is running for more than 10 or so hours it starts to slow down and then again the only way to fix it is to killall. I have checked other applications and they all work and are unaffected, this only seems to happen with firefox. I do find it strange that it is so much worse in Ubuntu 8.10. Any ideas?

Changed in firefox-3.0 (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.