Bug 512487 - Firefox does not shut down on x86_64 and i586
Summary: Firefox does not shut down on x86_64 and i586
Keywords:
Status: CLOSED DUPLICATE of bug 501427
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 11
Hardware: All
OS: Linux
low
high
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 501427
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-17 23:07 UTC by Peter Gückel
Modified: 2018-04-11 07:17 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-08-11 22:43:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
The output produced by the directions given (7.55 KB, text/plain)
2009-07-20 18:43 UTC, Peter Gückel
no flags Details
stacktrace from firefox exhibiting high cpu on exit (firefox-3.5-1.fc11.i586) (3.10 KB, text/plain)
2009-08-10 20:05 UTC, Oliver Henshaw
no flags Details
stacktrace from firefox exhibiting zero cpu on exit (firefox-3.5-1.fc11.i586) (4.11 KB, text/plain)
2009-08-10 20:06 UTC, Oliver Henshaw
no flags Details

Description Peter Gückel 2009-07-17 23:07:14 UTC
Description of problem:
When shutting down firefox, about 80% of the time, the window closes, but the application remains running and consumes about 50-80% of processor power.

Version-Release number of selected component (if applicable):
3.5-1.fc11

How reproducible:
Open, then terminate firefox. Lauch krunner and observe that firefox is still running. Try to restart firefox and a message window appears, stating that this is not possible, as another instance is already running (but it is impossible to get this other instance to open a window, only to kill it). Then it will be possible to lauch a new firefox.

Steps to Reproduce:
1. Open and close firefox.
2. Try to restart firefox and be told that another istance is already running, hence kill the running instance.
3. Now new instance will start.
  
Actual results:
as described

Expected results:
It should quit when the last window is closed.

Additional info:
As stated above, this happens about 80% of the time and I have been unable to deternine why it sometimes works normally. This problem has been around since fedora 11 alpha and is still not resolved.

Comment 1 Matěj Cepl 2009-07-20 08:13:42 UTC
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

First of all, could we get output of the command

	rpm -qa *xulrun* *firefox* *mozilla* *flash* nsplugin*

Please also install firefox-debuginfo (debuginfo-install is from
yum-utils package).

	debuginfo-install firefox

Then run firefox with a parameter -g. That will start firefox running inside of gdb debugger. Then use command run and try to reproduce the issue. When it happens, you should go back to the gdb and run

	(gdb) thread apply all backtrace

This produces usually many screens of the text. Copy all of them into a text editor and attach the file to the bug as an uncompressed attachment.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Comment 2 Peter Gückel 2009-07-20 17:56:20 UTC
Running rpm -qa xulrun firefox mozilla flash nsplugin*:

firefox-3.5-1.fc11.x86_64
nspluginwrapper-1.3.0-6.fc11.x86_64

I will install the debuginfo and get back later.

Comment 3 Peter Gückel 2009-07-20 18:18:39 UTC
I looked at that command again and I presume you meant xulrunner, not xulrun, so here it is again:

firefox-3.5-1.fc11.x86_64
nspluginwrapper-1.3.0-6.fc11.x86_64
xulrunner-1.9.1-1.fc11.x86_64

Also, I should point out that, as there is no 64-bit flash, I am using the experimental (10.0.22.87) 64-bit tarball from the adobe site. Note, however, that the laptop, an intel x586 fedora system, also has the problem, and it is using the rpm flash, namely version 10.0.22.87.

Comment 4 Peter Gückel 2009-07-20 18:43:00 UTC
Created attachment 354377 [details]
The output produced by the directions given

Comment 5 Matěj Cepl 2009-07-23 21:22:36 UTC
Thanks a lot.

Comment 6 Peter Gückel 2009-07-23 22:52:58 UTC
There were updates today.

rpm -qa xulrunner firefox mozilla flash nsplugin* produces:

nspluginwrapper-1.3.0-6.fc11.x86_64
firefox-3.5.1-1.fc11.x86_64
nspluginwrapper-debuginfo-1.3.0-6.fc11.x86_64
xulrunner-1.9.1.1-1.fc11.x86_64

Comment 7 info 2009-07-30 21:33:18 UTC
Same problem here. Have to kill firefox most of the time after closing it, otherwise laptop overheats.

$ rpm -qa xulrunner firefox mozilla flash nsplugin* 
firefox-3.5.1-1.fc11.x86_64
xulrunner-1.9.1.1-1.fc11.x86_64

Instead of flash I have gnash-0.8.5-3.fc11.x86_64 but the problem doesn not seem to be related to visiting flash sites.

Comment 8 J. Randall Owens 2009-08-01 22:05:19 UTC
I get this in almost exactly the same way in both Firefox and Thunderbird, which suggests to me that it's a problem in one of the underlying libraries, likely in xulrunner (which was also recently updated).  It seems to happen more consistently in Thunderbird than in Firefox, though.

mozilla-filesystem-1.9-4.fc11.i586
flash-plugin-10.0.32.18-release.i386
nspluginwrapper-1.3.0-6.fc11.i586
swfdec-mozilla-0.9.2-2.fc11.i586
firefox-3.5.1-3.fc11.i586
openvrml-mozilla-plugin-0.17.12-1.fc11.i586
xulrunner-devel-1.9.1.1-1.fc11.i586
mozilla-vlc-1.0.0-1.fc11.i586
xulrunner-1.9.1.1-1.fc11.i586

And, for good measure:
thunderbird-enigmail-0.96a-0.3.cvs20090521.fc11.i586
thunderbird-lightning-1.0-0.3.20090302hg.fc11.i586
thunderbird-3.0-2.3.beta2.fc11.i586

Comment 9 Eli Wapniarski 2009-08-10 19:58:12 UTC
I have the same issue

Comment 10 Oliver Henshaw 2009-08-10 20:03:23 UTC
Is this due to gtk-qt-engine? I had problems with exiting firefox until I changed from using my kde theme (which is oxygen) as my gtk style to using clearlooks. I have two stack traces saved, both of which look similar to the one in comment #4 (Qt -> X -> xcb).

I also use the kfirefox theme, but IIRC I saw problems even without it. I also think I've only seen this problem in firefox 3.5 / F11 - not with firefox 3.0 / F10.

See also https://bugzilla.redhat.com/show_bug.cgi?id=501427 and http://code.google.com/p/gtk-qt-engine/issues/detail?id=39

Comment 11 Oliver Henshaw 2009-08-10 20:05:44 UTC
Created attachment 356949 [details]
stacktrace from firefox exhibiting high cpu on exit (firefox-3.5-1.fc11.i586)

Comment 12 Oliver Henshaw 2009-08-10 20:06:32 UTC
Created attachment 356950 [details]
stacktrace from firefox exhibiting zero cpu on exit (firefox-3.5-1.fc11.i586)

Comment 13 Peter Gückel 2009-08-10 23:53:20 UTC
(In reply to comment #10)
> Is this due to gtk-qt-engine? I had problems with exiting firefox until I
> changed from using my kde theme (which is oxygen) as my gtk style to using
> clearlooks.

By Jove, I think that is it! I switched from Oxygen to Clearlooks (damn, are firefox and openoffice ugly now!) and opened and closed firefox a good number of times, after browsing some, and not once did it fail to shut down.

PS: I use the gtk-qt-engine, but I do not use kfirefox or any other hacks/extensions/add-ons.

Comment 14 Matěj Cepl 2009-08-11 08:27:15 UTC
OK, reassigning.

Comment 15 Rex Dieter 2009-08-11 11:44:53 UTC
*shock*, just because folks are using gtk-qt-engine, that's what is attributed blame?

Comment 16 Bill McGonigle 2009-08-11 13:28:49 UTC
Petrus, since yours is very reproducable, maybe you could get it back to hanging, uninstall the gtk-qt-engine, check for hangs, re-install gtk-qt-engine, and retest?

Comment 17 Rex Dieter 2009-08-11 13:41:46 UTC
OK, I'm lame, sorry for the outburst, no need to uninstall, just disable it, ie, goto systemsettings->Appearance.. -> GTK Syltes... -> Use Another Style != Qt4

At least that'll provide some data to go on...

Comment 18 Rex Dieter 2009-08-11 15:32:27 UTC
Maybe related to bug #501427 " gtk-qt-engine causes GTK apps to hang/crash when "Use my KDE style" is selected"

Feel free to dup on that one when/if you feel there's sufficient evidence to believe that's it.

Comment 19 Peter Gückel 2009-08-11 15:43:51 UTC
Well, referring back to my comment#13, I did disable it by not selecting qt4, but the hideously ugly clearlooks and...

I have not had one problem. I used the computer all last night and this morning and firefox got opened a good number of times.

It really would appear to be gtk-qt-engine.

I will try reselecting qt4 and get back in a second.

Comment 20 Peter Gückel 2009-08-11 15:47:21 UTC
It seems pretty obvious. I just switched to qt4, opened and closed firefox and the problem was there immediately. Then I changed back to clearlooks and it is gone.

Comment 21 Oliver Henshaw 2009-08-11 16:23:58 UTC
I've just re-tested and found that the hangs can also be avoided by keeping "Qt4" for gtk-qt-engine and some other widget style (e.g. Cleanlooks or Nodoka) as the kde style (in System Settings -> Style).

I think the reason I settled for Clearlooks in gtk-qt-engine was to avoid badly rendered tabs and checkboxes/textboxes in firefox (see http://code.google.com/p/gtk-qt-engine/issues/detail?id=68 and http://code.google.com/p/gtk-qt-engine/issues/detail?id=66). With the kfirefox theme it doesn't look that bad, at least IMO.


NB. Selecting Gtk+ as the kde style made System Settings and Konsole fall over and refuse to start until I edited .kde/share/config/kdeglobals from another virtual terminal.

Comment 22 J. Randall Owens 2009-08-11 22:27:43 UTC
This also, completely unsurprisingly, seems to fix Thunderbird hanging & spinning when closing, bug #501139.

Comment 23 Matěj Cepl 2009-08-11 22:43:15 UTC
(In reply to comment #18)
> Maybe related to bug #501427 " gtk-qt-engine causes GTK apps to hang/crash when
> "Use my KDE style" is selected"
> 
> Feel free to dup on that one when/if you feel there's sufficient evidence to
> believe that's it.  

From the further comments it seems obvious to me that there is something wrong with gtk-qt-engine, and I don't understand the logic of pushing this bug back to firefox component.

Closing as duplicate of bug 501427

Comment 24 Matěj Cepl 2009-08-11 22:43:38 UTC

*** This bug has been marked as a duplicate of bug 501427 ***


Note You need to log in before you can comment on or make changes to this bug.