486115 - FireFox Don't Unload When Close

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Evengard]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.9.2a1pre) Gecko/20090331 Minefield/3.6a1pre
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.9.2a1pre) Gecko/20090331 Minefield/3.6a1pre

When I try to close Minefield on Linux (Debian squeeze + KDE 4.2 amd64) and then reopen it says me that Firefox is currently running and it don't load me the main screen. When I do ps aux | grep firefox i have this:
evengard@TriOp:~$ ps aux | grep firefox
evengard  4718  0.0  0.0  10208  1300 ?        S    18:03   0:00 /bin/sh /home/evengard/firefox/firefox
evengard  4721  0.0  0.0  10268  1392 ?        S    18:03   0:00 /bin/sh /home/evengard/firefox/run-mozilla.sh /home/evengard/firefox/firefox-bin
evengard  4725  3.9  2.9 488284 92512 ?        Sl   18:03   0:08 /home/evengard/firefox/firefox-bin
evengard  4748  0.0  0.0   5216   808 pts/1    R+   18:06   0:00 grep firefox
And this is AFTER the shutdown of Minefeild and it doesn't matter by the close button on the right top corner or by File - Close

Reproducible: Always

Steps to Reproduce:
1. Install latest nightly build x86_64
2. Run Minefield
3. Close Minefield
4. Wait 10 minutes
5. Try to reopen Minefield
6. See the error
Actual Results:  
"The browser is currently running but not responding."

Expected Results:  
It should just start

Comment 1

[Matthias Versen [:Matti]]

Do you get the same in the Firefox safemode ?
http://support.mozilla.com/en-US/kb/Safe+Mode

Comment 2

[Evengard]

Yes it is the case. I'll add some screenshots

Comment 3

[Evengard]

Attachment: Screenshot with error

As you can see there, FireFox is closed, I try to start it but without success...

Comment 4

[Evengard]

Comment on attachment 370243 [details]
Screenshot with error

On the screenshot above FireFox is started from the second coonsole, closed by the button of the top right corner and then typed ps aux | grep firefox and then tried to start FireFox

Comment 5

[Evengard]

Build 20090401042545 - NOT FIXED

Comment 6

[Evengard]

Build 20090403041403 still not fixed...

Comment 7

[Evengard]

Build 20090404031205 not fixed...

Comment 8

[Matthias Versen [:Matti]]

wfm on win32

Comment 9

[Evengard]

Yes it don't work only in Linux... Maybe even only on x86_64... Latest build - still not fixed

Comment 10

[Tyler Downer [He/Him]]

This is reported on a bunch of other bugs:
Bug 444915, bug 403623, bug 416348 and more.

Comment 11

[Evengard]

Probably enough to make it confirmed? Still not fixed on latest trunk build. Tried just after reinstalling my system (clear profile of course) and no addons - still here... It is probably a bug inside browser, not of our systems

Comment 12

[Tyler Downer [He/Him]]

Oh, no. Please look at those bugs. If one is like yours, mark this bug a dupe of it. Someone with canconfirm status needs to be able to reliably reproduce this to set it to NEW.

Comment 13

[Evengard]

I think those bugs aren't exactly the same, because:
1. They are too old and probably corrected
2. While using the same build on Windows I don't get this bug, only Linux

And... We need someone with canconfirm status under linux (x86_64) to confirm probably...

Comment 14

[Matthias Versen [:Matti]]

We don't need someone with canconfirm, we need just _someone_ for a start

Comment 15

[Evengard]

The error is still here... In the 1st may nightly build

Comment 16

[Evengard]

Still there... Gecko/20090610 Minefield/3.6a1pre

Comment 17

[Evengard]

Another information detected: when I close Firefox and it doesn't unload, it begins to use a huge amount of processor time... About 50% on my dual core processor (probably 1 core is used completely)
Sometimes (very rare) it exits as it must exit, but the most of the time it exits by non unloading and using the processor...

Comment 18

[Evengard]

Mozilla/5.0 (X11; U; Linux x86_64; ru; rv:1.9.2a1pre) Gecko/20090619 Minefield/3.6a1pre

PROBABLY FIXED. After some runs I don't get the problem. Will test more to be sure

Comment 19

[Evengard]

After doing some tests, restarting system, upgrading to latest nightly build I'm happy to say that THE BUG IS GONE ) Great work, thank you very much )

Comment 20

[Matthias Versen [:Matti]]

Great that it works now but fixed can only be used with a patch in the bug, marking wfm

Comment 21

[Evengard]

Sorry... I didn't know the rules... )

Comment 22

[Evengard]

UPD: I found why I had this problem... It is not a bug of Firefox but a bug of gtk-qt-engine in KDE4 using Oxygen as default theme for GTK applications... Just set any other theme (the best is qtcurve) and the problem will be fixed.