Firefox 3.0.9 hang when trying to load a page with a lot of image or flash

Bug #365454 reported by Hassan El Jacifi
4
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: firefox-3.0

I have a crash several time per day when I'm surfing with firefox. I can't close firefox after it hangs, I can only kill the process and restart it again.

I collect some information, I don't know if it will help or not:

/usr/lib/firefox-3.0.9% ./run-mozilla.sh -g firefox -d gdb
MOZILLA_FIVE_HOME=.
  LD_LIBRARY_PATH=.:./plugins:.
DISPLAY=:0.0
DYLD_LIBRARY_PATH=.:.
     LIBRARY_PATH=.:./components:.
       SHLIB_PATH=.:.
          LIBPATH=.:.
       ADDON_PATH=.
      MOZ_PROGRAM=firefox
      MOZ_TOOLKIT=
        moz_debug=1
     moz_debugger=
/usr/bin/gdb firefox -x /tmp/mozargs.wkZkxx
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu"...
(no debugging symbols found)
Function "main" not defined.
Make breakpoint pending on future shared library load? (y or [n]) n
Starting program: /usr/lib/firefox-3.0.9/firefox '-d' 'gdb'
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread 0x7fc734bdc700 (LWP 8656)]
(no debugging symbols found)
[New Thread 0x7fc7318fb950 (LWP 8657)]
[New Thread 0x7fc730ef0950 (LWP 8658)]
[New Thread 0x7fc730371950 (LWP 8659)]
[Thread 0x7fc730371950 (LWP 8659) exited]
[New Thread 0x7fc730371950 (LWP 8660)]
[New Thread 0x7fc72f90a950 (LWP 8661)]
[New Thread 0x7fc72f109950 (LWP 8662)]
[Thread 0x7fc72f90a950 (LWP 8661) exited]
[New Thread 0x7fc72f90a950 (LWP 8663)]
[Thread 0x7fc72f109950 (LWP 8662) exited]
[Thread 0x7fc72f90a950 (LWP 8663) exited]
[New Thread 0x7fc72f90a950 (LWP 8664)]
[New Thread 0x7fc72f109950 (LWP 8665)]
[New Thread 0x7fc72cdf1950 (LWP 8666)]
[Thread 0x7fc730371950 (LWP 8660) exited]
[New Thread 0x7fc730371950 (LWP 8667)]
[New Thread 0x7fc7277df950 (LWP 8668)]
Program received signal SIGINT, Interrupt.
[Switching to Thread 0x7fc734bdc700 (LWP 8656)]
0x000000341260da94 in __lll_lock_wait () from /lib/libpthread.so.0
(gdb) backtrace
#0 0x000000341260da94 in __lll_lock_wait () from /lib/libpthread.so.0
#1 0x00000034126091fc in _L_lock_1078 () from /lib/libpthread.so.0
#2 0x00000034126090d0 in pthread_mutex_lock () from /lib/libpthread.so.0
#3 0x0000003421c251e9 in PR_Lock (lock=<value optimized out>) at ptsynch.c:206
#4 0x00007fc733a63fc4 in ?? () from /usr/lib/xulrunner-1.9.0.9/libxul.so
#5 0x00007fc7341784f4 in NS_InvokeByIndex_P () from /usr/lib/xulrunner-1.9.0.9/libxul.so
#6 0x00007fc733a12e91 in ?? () from /usr/lib/xulrunner-1.9.0.9/libxul.so
#7 0x00007fc733a1ac21 in ?? () from /usr/lib/xulrunner-1.9.0.9/libxul.so
#8 0x00007fc734976074 in js_Invoke () from /usr/lib/xulrunner-1.9.0.9/libmozjs.so
#9 0x00007fc734968e17 in ?? () from /usr/lib/xulrunner-1.9.0.9/libmozjs.so
#10 0x00007fc7349760bb in js_Invoke () from /usr/lib/xulrunner-1.9.0.9/libmozjs.so
#11 0x00007fc733a103f3 in ?? () from /usr/lib/xulrunner-1.9.0.9/libxul.so
#12 0x00007fc7341790e1 in ?? () from /usr/lib/xulrunner-1.9.0.9/libxul.so
#13 0x00007fc73417858f in ?? () from /usr/lib/xulrunner-1.9.0.9/libxul.so
#14 0x00007fc7293a5f10 in ?? ()
#15 0x00007fc73432e29f in ?? () from /usr/lib/xulrunner-1.9.0.9/libxul.so
#16 0x00007fc72942b5d0 in ?? ()
#17 0x00007fff3cbf33ac in ?? ()
#18 0x00000000f8c08c4b in ?? ()
#19 0x0000000000000000 in ?? ()

% uname -a
Linux Terra 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux

% lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 9.04
Release: 9.04
Codename: jaunty

% dpkg -l \*firefox\* | grep ^ii
ii firefox 3.0.9+nobinonly-0ubuntu0.9.04.1
ii firefox-3.0 3.0.9+nobinonly-0ubuntu0.9.04.1
ii firefox-3.0-branding 3.0.9+nobinonly-0ubuntu0.9.04.1
ii firefox-3.0-gnome-support 3.0.9+nobinonly-0ubuntu0.9.04.1
ii firefox-gnome-support 3.0.9+nobinonly-0ubuntu0.9.04.1
ii firefox-launchpad-plugin 0.4

% dpkg -l \*xulrunner\* | grep ^ii
ii xulrunner-1.9 1.9.0.9+nobinonly-0ubuntu0.9.04.1
ii xulrunner-1.9-gnome-support 1.9.0.9+nobinonly-0ubuntu0.9.04.1

Eyal Mamo (emamo91)
Changed in firefox-3.0 (Ubuntu):
status: New → Confirmed
Revision history for this message
eugenez (eugene-zvyagintsev) wrote :

Firefox 3.09 not unloaded from memory when close and can not start again until "killall firefox" (Kubuntu 9.04 32 bit / KDE 4.2.2). Create a new clean profile and disabling all the addons & plugins do not solve the problem.

$ uname -a
Linux linux 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux

Packets are:
firefox-3.0_3.0.9+nobinonly-0ubuntu0.9.04.1_i386.deb
firefox-3.0-branding-3.0.9+nobinonly-0ubuntu0.9.04.1_i386.deb
xulrunner-1.9_1.9.0.9+nobinonly-0ubuntu0.9.04.1_i386.deb

Revision history for this message
Alexander Sack (asac) wrote :

can you still reproduce when disabling flash and your extensions?

Revision history for this message
eugenez (eugene-zvyagintsev) wrote :

If the question to me, I'll try to answer in more detail

1. When using a default working profile
a) with enabled flash plugin: firefox remains in memory after closing
b) with disabled flash plugin: firefox remains in memory after closing
c) and flash plugin was removed (apt-get remove flashplugin-nonfree): firefox remains in memory after closing

2. When using a new "clean" profile without any user addons
a) with enabled or disabled flash plugin: firefox remains in memory after closing

PS: In Kubuntu 8.10 / KDE 4.2.2 the same version of Mozilla Firefox (3.0.9 Gran Paradiso) is working OK.

Revision history for this message
eugenez (eugene-zvyagintsev) wrote :

I solved my problem with Firefox. After removal of a gtk-qt-engine package Firefox behaves as expected. Sorry to trouble you...

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.