Firefox Not Quitting--Lots a Logs!

[Doctor X]

I fear the answer--selectively shutting off Add-Ons until I figure it out. Unfortunately, I do not understand log reports, so I am not certain what I will post below will prove useful or just a bunch of code.

My computer stats are as in my signature--I have the latest security update.

I have happily used FF for years. After the last two updates, I have noticed a problem where it will not shut-down. I am currently on FF 3.5.7 I have to force quit. During the this hang, it will run the processor at full.

I have repaired permissions. It seems to be more of a problem the longer I run FF. It happens whether or not other programs are running.

The logs go on forever--particularly the FF crash report. So I will break them up, but I am not certain how much is needed.

The Logs:

Here is the Console report from when FF is started and then quit without a problem:

1/24/10 4:23:09 AM [0x0-0x82082].org.mozilla.firefox[2625] objc[2625]: Class DOMHTMLParamElement is implemented in both /Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock and /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore. One of the two will be used. Which one is undefined.
1/24/10 4:23:09 AM [0x0-0x82082].org.mozilla.firefox[2625] objc[2625]: Class WebBaseNetscapePluginView is implemented in both /Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock and /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit. One of the two will be used. Which one is undefined.
1/24/10 4:23:17 AM [0x0-0x82082].org.mozilla.firefox[2625] !!! [SmartNamer] updateEntry(): TypeError: /^https?:\/\/([^\/]+)/.exec(pageUrl) is null
1/24/10 4:23:21 AM [0x0-0x82082].org.mozilla.firefox[2625] Debugger() was called!
1/24/10 4:23:24 AM [0x0-0x82082].org.mozilla.firefox[2625] !!! [Hook] hook(): title not found
1/24/10 4:24:48 AM [0x0-0x83083].org.mozilla.firefox[2632] objc[2632]: Class DOMHTMLParamElement is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.framework/Versions/A/WebCore and /Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock. One of the two will be used. Which one is undefined.
1/24/10 4:24:48 AM [0x0-0x83083].org.mozilla.firefox[2632] objc[2632]: Class WebBaseNetscapePluginView is implemented in both /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit and /Library/InputManagers/SafariBlock/SafariBlock.bundle/Contents/MacOS/SafariBlock. One of the two will be used. Which one is undefined.
1/24/10 4:24:53 AM [0x0-0x83083].org.mozilla.firefox[2632] !!! [SmartNamer] updateEntry(): TypeError: /^https?:\/\/([^\/]+)/.exec(pageUrl) is null
1/24/10 4:24:57 AM [0x0-0x83083].org.mozilla.firefox[2632] Debugger() was called!
1/24/10 4:24:59 AM [0x0-0x83083].org.mozilla.firefox[2632] !!! [Hook] hook(): title not found
1/24/10 4:25:08 AM [0x0-0x83083].org.mozilla.firefox[2632] !!! [Hook] hook(): title not found

FF was the only program running. Why it is looking for Safari Block I do not know.

--J.D.

 

[Doctor X]

[Melvillian logs unnecessary.--Ed.]

 

[Doctor X]

["Snip!"--Ed.]

 

[Doctor X]

["Snip!"--Ed.]

 

[ElDiabloConCaca]

Try removing "SafariBlock" and see if that helps.

I would need two additional months to look through the rest of the logs.

 

[Doctor X]

Interesting. I thought I had removed that because I use Safari AdBlocker since Safari Block does not work as well anymore.

And . . . there are remnants of it! I will try removing them.

--J.D.

 

[Doctor X]

Unfortunately, that does not seem to help the problem.

The Console report only says:

1/26/10 6:31:39 PM [0x0-0x27027].org.mozilla.firefox[216] !!! [Hook] hook(): title not found

and then I killed the process.

--J.D.

 

[Doctor X]

Solution

'twas one of the add-ons.

Now which one . . .

Unfortunately, turning off the most recent ones added did not solve the problem. I noticed the problem was time and use dependent--the longer I used FF with more tabs and functions such as internet radio--the more likely it would never close and try to fry the processor.

After disabling some, I had the LoooOOOOOoooog quit with less processor frying. So . . . the lesson is it may be more than one.

--J.D.

 

[Doctor X]

t3h R34lz Solution

Actually, none of that worked. I even deleted FF, reinstalled it, et cetera. The longer I ran FF the more likely it would not quit.

So I got into the habit of hitting "command/ -Q"--however you make that key sign!--then clicking on the Dock to Force Quit the immediately unresponsive FF.

Well, earlier today, whilst I was distracted [Surfing bungee porn on Safari.--Ed.] I clicked at the Dock first--hitting "Quit Firefox" rather than the other method.







And FF immediately quit. Poof! Gone.

I restarted it--it had saved my tabs as normal.

Since that time, I have tested it and it works. So there you go. Hopes this bizarre solution helps someone else.

--J.D.