And sometimes FF locks s damn, took 10 seconds between typing the K and being able to type the S.

...locks my Macintosh up completely. As above, or as I was going to say, when

crap, had to wait about 10 seconds beween GOIN and the G right there...

...when I want to move the cursor down to the bottom edge of the screen to pop up the menu bar so I can switch to another App while FF goes thru its period of being brain-dead. Cursor moves but won't work to do anything.

Sometimes the "hand" gets stuck & won't turn into a pointer or vertical line (text entry symbol)

Start Firefox in Safe Mode {web Link} by holding down the <Shift>
(Mac Options) key, and then starting Firefox. Is the problem still there?

Start your Computer in safe mode with networking. Then start Firefox. Try Safe web sites.

Starting The Computer In Safe Mode;
Free Online Encyclopedia

Running in un-safe mode right now -- all my security & privacy protections non functional. I'll see how it goes.

Amazon is a safe site. If FF can't work with Amazon its useless.

Something in the last update fucked things up. All my AddOns worked fine and you can't blame the addons if the update screwed them up.

My addons are privacy & security related, stuff that ought to be built into FF in the first place (with toggles & preferences).

Why does FF take many minutes to no shut down & need to be force quit? Here's the error; its a call to Mozilla.org:

3/16/15 2:52:30 PM crashreporter[5500] *** __NSAutoreleaseNoPool(): Object 0x100111120 of class NSCFString autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM [0x0-0x137137].org.mozilla.firefox[2226] 2015-03-16 14:52:30.036 crashreporter[5500:903] *** __NSAutoreleaseNoPool(): Object 0x100111120 of class NSCFString autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM crashreporter[5500] *** __NSAutoreleaseNoPool(): Object 0x100115090 of class NSPathStore2 autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM [0x0-0x137137].org.mozilla.firefox[2226] 2015-03-16 14:52:30.287 crashreporter[5500:903] *** __NSAutoreleaseNoPool(): Object 0x100115090 of class NSPathStore2 autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM crashreporter[5500] *** __NSAutoreleaseNoPool(): Object 0x1001115e0 of class NSPathStore2 autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM [0x0-0x137137].org.mozilla.firefox[2226] 2015-03-16 14:52:30.288 crashreporter[5500:903] *** __NSAutoreleaseNoPool(): Object 0x1001115e0 of class NSPathStore2 autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM crashreporter[5500] *** __NSAutoreleaseNoPool(): Object 0x100115160 of class NSPathStore2 autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM [0x0-0x137137].org.mozilla.firefox[2226] 2015-03-16 14:52:30.288 crashreporter[5500:903] *** __NSAutoreleaseNoPool(): Object 0x100115160 of class NSPathStore2 autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM crashreporter[5500] *** __NSAutoreleaseNoPool(): Object 0x100115210 of class NSPathStore2 autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM [0x0-0x137137].org.mozilla.firefox[2226] 2015-03-16 14:52:30.289 crashreporter[5500:903] *** __NSAutoreleaseNoPool(): Object 0x100115210 of class NSPathStore2 autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM crashreporter[5500] *** __NSAutoreleaseNoPool(): Object 0x1001152b0 of class NSPathStore2 autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM [0x0-0x137137].org.mozilla.firefox[2226] 2015-03-16 14:52:30.289 crashreporter[5500:903] *** __NSAutoreleaseNoPool(): Object 0x1001152b0 of class NSPathStore2 autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM crashreporter[5500] *** __NSAutoreleaseNoPool(): Object 0x100115360 of class NSPathStore2 autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM [0x0-0x137137].org.mozilla.firefox[2226] 2015-03-16 14:52:30.290 crashreporter[5500:903] *** __NSAutoreleaseNoPool(): Object 0x100115360 of class NSPathStore2 autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM crashreporter[5500] *** __NSAutoreleaseNoPool(): Object 0x100115a20 of class NSCFData autoreleased with no pool in place - just leaking 3/16/15 2:52:30 PM [0x0-0x137137].org.mozilla.firefox[2226] 2015-03-16 14:52:30.290 crashreporter[5500:903] *** __NSAutoreleaseNoPool(): Object 0x100115a20 of class NSCFData autoreleased with no pool in place - just leaking

3/16/15 2:52:31 PM com.apple.launchd.peruser.501[111] ([0x0-0x137137].org.mozilla.firefox[2226]) Exited with exit code: 1

Given the extremely low peak packets/sec rate, I have to think that FF is simply going brain dead; it doesn't seem to be loading anything for long stretches of time.

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP in front of the numbers, click it and select Submit.

Using your mouse, mark the most resent 7 - 10 crash reports, and copy them. Now go to the reply box below and paste them in.

Did you place Firefox, then the computer, in Safe Mode as posted above?

When a program is changed, sometimes what worked fine before no longer works properly. That is why we trouble shoot.

Still seemed slow in safe mode. And after restarting FF with Addons back on, some of my settings were wiped out. That shouldn't happen !

Only one crash report is there:

Mozilla Crash Reports Search

   Product: 

Select Version: Report:

Super Search Firefox 36.0.1 Crash Report [@ shutdownhang | js::gc::Chunk::fetchNextDecommittedArena() ] Search Mozilla Support for Help ID: 52c8b966-4089-4edc-8b60-d4bf52150316 Signature: shutdownhang | js::gc::Chunk::fetchNextDecommittedArena()

   Details
   Metadata
   Modules
   Raw Dump
   Extensions

Signature shutdownhang | js::gc::Chunk::fetchNextDecommittedArena() More Reports Search UUID 52c8b966-4089-4edc-8b60-d4bf52150316 Date Processed 2015-03-16 19:11:11.816079 Uptime 260352 Last Crash 2919101 seconds before submission Install Age 602041 since version was first installed. Install Time 2015-03-09 19:38:28 Product Firefox Version 36.0.1 Build ID 20150305021524 Release Channel release OS Mac OS X OS Version 10.6.8 10K549 Build Architecture amd64 Build Architecture Info family 6 model 37 stepping 5 | 4 Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS Crash Address 0x0 User Comments FF running glacially slow; very low network packet rate indicates that FF is simply DOING anything.

Did not shutdown after several minutes so force quit. App Notes

AdapterVendorID: 0x10de, AdapterDeviceID: 0x a29WebGL? GL Context? GL Context+ WebGL+

Processor Notes sp-processor10_phx1_mozilla_com.9668:2015; MozillaProcessorAlgorithm2015; skunk_classifier: reject - not a plugin hang EMCheckCompatibility

True

Winsock LSP

Adapter Vendor ID

0x10de

Adapter Device ID

0x a29

Bugzilla - Report this bug in Firefox Core Plugins Toolkit Related Bugs

Crashing Thread Frame Module Signature Source 0 XUL mozilla::(anonymous namespace)::RunWatchdog(void*) toolkit/components/terminator/nsTerminator.cpp 1 libnss3.dylib _pt_root nsprpub/pr/src/pthreads/ptthread.c 2 libSystem.B.dylib _pthread_start 3 libSystem.B.dylib thread_start 4 libnss3.dylib libnss3.dylib@0x203a3f

Show other threads Mozilla Crash Reports - Powered by Socorro - All dates are UTC

   Server Status
   Source
   Docs
   API
   Privacy Policy

   Sign in

The crash report is several pages long, and has data we need to look at. Please post the crash report number starting with BP.

The crash report is here:

• bp-52c8b966-4089-4edc-8b60-d4bf52150316
• Firefox 36.0.1 Crash Report [@ shutdownhang | js::gc::Chunk::fetchNextDecommittedArena() ]

Try to disable IPv6 (check for other possible causes as well).

• http://kb.mozillazine.org/Error_loading_websites

You can reload web page(s) and bypass the cache to refresh possibly outdated or corrupted files.

• Hold down the Shift key and left-click the Reload button
• Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
• Press "Command + Shift + R" (Mac)

Another thing. FF seems to be able to only do one thing at a time. If I open a link in another tab, the current tab becomes non responsive until the new tab finishes opening. Closing tabs can take 5-10 seconds as well.

I read you ran Firefox in Safe Mode. Have you; Start your Computer in safe mode with networking. Then start Firefox. Try Safe web sites. Is the problem still there?

Starting The Computer In Safe Mode;
Free Online Encyclopedia

Right after going into Safe Mode, Flash wanted to do an update so having to start over again in normal mode, things seem to be faster.

Why doesn't Safe Mode allow you to restart addons one at a time so you can see when things suddenly go bad?

Seems to be better since the Flash update.

So how come the FF update got out of whack with Flash?

Mozilla changed something about Firefox. Now all sub-programs, (like flash, add-ons, and so on) need to make sure they still work.

If Adobe thought they needed to adapt their product to an open source project, they would be doing it during the development of the update, not responding weeks after an update. No, it was the update that broke FF.

And just when I get FF working again, another FF update request... Is there an easy way to undo these if they don't work?

And today Javascript is locking up the whole computer (needed to hard restart). I was hovering over the main image in Ebay, so the image zooms around, and it locked up, repeatedly, on different images, longer each time, until it locked the Mac completely.

So maybe nothing to lose by installing the FF update...

I have not yet installed the latest security update. FF is "idling" at 30-90 % CPU. How can this be? Is there a tab in the background sucking CPU cycles?

Some time ago I toggled something that is supposed to prevent loading tabs in the background. Don't recall if it was a FF Preference or an Addon.

FF needs to allow the user to control background CPU usage. For instance, a tab in the background should not be allowed to do anything after X minutes. So the user can allow a movie to load in the background by upping the timeout period, but generally prevent useless page refreshing. This function should also aggregate CPU usage by Addons.

FF also needs a pane which will show the %CPU usage on a per-tab basis, so the user can determine which tabs are causing problems. The user needs to know which tabs are making the largest number of calls.

Go to the Mozilla Add-ons Web Page {web link} (There’s a lot of good stuff here) and search for what you want.