You are not logged in.

#1 2009-10-20 21:21:22

brazzmonkey
Member
From: between keyboard and chair
Registered: 2006-03-16
Posts: 818

Firefox goes 100% CPU when closed

Hi here,

Firefox works properly, but once it's closed, top reports it to use 100% CPU. Everything's back to normal after I kill Firefox.

Anyone else seing this behaviour with Firefox? BTW, my system is a fully updated x86_64, in case that matters.

Thanks.


what goes up must come down

Offline

#2 2009-10-21 08:30:41

ebl
Member
Registered: 2009-10-21
Posts: 1

Re: Firefox goes 100% CPU when closed

I have the same problem here, i have tried to remove the .mozilla to start from scratch, and the problem is still there.

The backtrace gives me :
#3  0x00007fb19d46b993 in poll () from /lib/libc.so.6                 
#4  0x00007fb195f1689a in _xcb_conn_wait () from /usr/lib/libxcb.so.1 
#5  0x00007fb195f16e37 in _xcb_out_send () from /usr/lib/libxcb.so.1
#6  0x00007fb195f170e5 in xcb_writev () from /usr/lib/libxcb.so.1
#7  0x00007fb19940a7aa in _XSend () from /usr/lib/libX11.so.6
#8  0x00007fb1993f84cb in XQueryExtension () from /usr/lib/libX11.so.6
#9  0x00007fb1993ecbc2 in XInitExtension () from /usr/lib/libX11.so.6
#10 0x00007fb1996fce8c in XRenderFindDisplay () from /usr/lib/libXrender.so.1
#11 0x00007fb1996faa1e in XRenderFreePicture () from /usr/lib/libXrender.so.1
#12 0x00007fb18d14fe9d in QX11PixmapData::release() () from /usr/lib/libQtGui.so.4
#13 0x00007fb18d1505d4 in QX11PixmapData::~QX11PixmapData() () from /usr/lib/libQtGui.so.4
#14 0x00007fb18d14143b in QPixmap::deref() () from /usr/lib/libQtGui.so.4
#15 0x00007fb18d14163b in QPixmap::~QPixmap() () from /usr/lib/libQtGui.so.4
#16 0x00007fb18cccd12c in TileSet::~TileSet() () from /usr/lib/kde4/plugins/styles/oxygen.so
#17 0x00007fb18ccd9c37 in QCache<unsigned long long, TileSet>::clear() () from /usr/lib/kde4/plugins/styles/oxygen.so
#18 0x00007fb18ccd9e67 in OxygenStyleHelper::~OxygenStyleHelper() () from /usr/lib/kde4/plugins/styles/oxygen.so
#19 0x00007fb19d3dd9e2 in __run_exit_handlers () from /lib/libc.so.6
#20 0x00007fb19d3dda35 in exit () from /lib/libc.so.6
#21 0x00007fb19d3c79f4 in __libc_start_main () from /lib/libc.so.6

Nothing really helpful.

Offline

#3 2009-10-21 08:57:20

brazzmonkey
Member
From: between keyboard and chair
Registered: 2006-03-16
Posts: 818

Re: Firefox goes 100% CPU when closed

Looks like you use KDE4 as well., maybe this is related?
I noticed similar reports on Fedora, but couldn't find a workaround.


what goes up must come down

Offline

#4 2009-10-21 09:59:55

Bubla
Member
From: Rosice [CZ]
Registered: 2006-12-24
Posts: 26
Website

Re: Firefox goes 100% CPU when closed

I also have this issue sometimes and I use GNOME, so it probably doesn't matter what desktop environement you use.

However, I also use the vimperator extension and I wasn't sure whether it is not because of that.

Last edited by Bubla (2009-10-21 10:00:58)

Offline

#5 2009-10-21 10:02:09

brazzmonkey
Member
From: between keyboard and chair
Registered: 2006-03-16
Posts: 818

Re: Firefox goes 100% CPU when closed

I don't use any extension...


what goes up must come down

Offline

#6 2009-10-21 11:15:47

byte
Member
From: Düsseldorf (DE)
Registered: 2006-05-01
Posts: 2,046

Re: Firefox goes 100% CPU when closed

Any plugins? about:plugins


1000

Offline

#7 2009-10-21 12:44:26

brazzmonkey
Member
From: between keyboard and chair
Registered: 2006-03-16
Posts: 818

Re: Firefox goes 100% CPU when closed

I have the following plugins:
- Skype Buttons for Kopete
- Shockwave Flash
- IcedTea Java Web Browser Plugin


what goes up must come down

Offline

#8 2009-10-21 14:25:14

JGC
Developer
Registered: 2003-12-03
Posts: 1,664

Re: Firefox goes 100% CPU when closed

Gtk application that shows Qt in backtraces... looks like it's caused by gtk-qt-engine or whatever plugin/extension you installed that pulls it in.

Offline

#9 2009-10-21 19:00:48

brazzmonkey
Member
From: between keyboard and chair
Registered: 2006-03-16
Posts: 818

Re: Firefox goes 100% CPU when closed

Yup, JGC got it right. Disabling gtk-qt-engine is the actual workaround. Do you think I should file a bug?


what goes up must come down

Offline

Board footer

Powered by FluxBB