If you encounter a tab (fake MS ransom) that locks up FF and you have FF set to "Show your windows and tabs from last time" you can't close/reopen FF without that tab taking over all control. If you want to dump it and keep all of your previous tabs:
Delete C:\Users\"yourname"\AppData\Roaming\Mozilla\Firefox\Profiles\********."yourname"\pref.js
Open Firefox and select Restore Previous Session from "right 3 bars"
Open another copy of FF and copy your desired tabs to it, one at a time (carefully avoiding poison tab)
Change FF home screen back to your choice.
Close first copy (w/o saving tabs)
Close second copy after selecting "Show your windows and tabs from last time"
DO NOT call the 800# to tell them to "get bit" as *67 does not work on toll free numbers.
Poison (feeble ransom etc.) tabs
- therube
- Posts: 21714
- Joined: March 10th, 2004, 9:59 pm
- Location: Maryland USA
Re: Poison (feeble ransom etc.) tabs
That's a bit drastic, IMO. (At the least, back it up before doing so.)Delete ... pref.js
You could change the pref within prefs.js that tells it to restore the session (which I don't recall offhand).
Note that (I think it is 3 consecutive) kills of FF will bring up a dialog allowing you to select which tabs/windows you wish to restore.
(Not sure if you can load that dialog manually?)
(Any time you "kill" there stands a chance that something might not have saved correctly... potentially causing corruption...)
By default, FF only loads the "current" tab in each window.Open another copy of FF and copy your desired tabs to it, one at a time (carefully avoiding poison tab)
Others are not loaded until you actually access them.
So if your poison tab did not have focus when the session was saved, potentially you could "just open" FF normally without incident. Though you'd have to be sure not to click on the poisoned tab (though so long as you know here it is, or can figure it out, you could close it).
Alternatively, most likely the poisoned tab relies on JavaScript, so if you opened (a backup of) your session in an instance of FF that had NoScript installed, the poison would be neutralized right there (so long as you didn't allow JavaScript on that page).
Fire 750, bring back 250.
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.19) Gecko/20110420 SeaMonkey/2.0.14 Pinball CopyURL+ FetchTextURL FlashGot NoScript