Closed Bug 298084 Opened 20 years ago Closed 20 years ago

Tabbed browser preferences update 1.2.7 causes continual but unsuccessful attempt of Firefox to open

Categories

(Firefox :: Tabbed Browser, defect)

x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: archants, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.7) Gecko/20050414 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.7) Gecko/20050414 Firefox/1.0.4

I received a pop-up in the bottom right of my browser window saying there was an
update to the tabbed browsing plugin so I installed it, closed Firefox and
reopened, at least tried to. Trouble is that Firefox has gone mad and instead of
opening it just keeps on trying to open ceaslessly. All I can see is in the
Processes tab of the Windows Task Manager where Firefox appears in the list and
keeps jumping up and down in the list continuously without ever opening the
program. It does not stay there long enough to highlight and close before
jumping to a new position in the list again. CPU is running at 100% all the time.

The only way of closing Firefox from its mad antics is to try opening it a
second or third time which shows two/three instances of the program in the
Processes tab and then for some reason it gives me a chance to click Firefox and
end the process. Often have to do this two or three times.

See my posting here: http://forums.mozillazine.org/viewtopic.php?p=1548286#1548286


Reproducible: Didn't try

Steps to Reproduce:
1.Have several tabs open & (I think) Outlook (& possibly another program
running). A pop-up at the bottom right of my window tells me of a new update to
Tabbed Browsing preferences (1.2.7).
2.Click to download.
3.Close all Firefox tabs & Firefox
4.Try to open Firefox.

Actual Results:  
Firefox failed to open but there was a regularly spaced HDD activity (say at
one-second intervals) as Firefox failed to load. I pressed Alt+Ctrl+Del to open
the Windows Task Manager. No applications were running but under the Processes
tab firefox.exe kept appearing, just momentarily, at one position in the list
and then appearing in another position. This in unison with the HDD activity.
Never stationary so I was never able to highlight it and click End Process. The
Performance tab showed CPU Usage at 100%. Eventually I tried starting Firefox
again by clicking on my Desktop icon so two (and eventually 3) instances of
Firefox appeared in the Processes tab. This slowed the process down long enough
for me to select the name and end the process. I tried to open Firefox again but
had exactly the same result. I restarted the computer but the fault persisted.
Eventually I posted a query to the Firefox general forum (see my previous
reference to the thread) but in the end I did a System Restore to 16th June and
it has fixed the problem. I presume the update to tabbed browsing is no longer
there. Firefox opens as normal. Thank God!

Expected Results:  
Firefox should have opened normally with the preferences installed.
You can open firefox in safe mode
http://kb.mozillazine.org/Safe_mode

And then uninstall the extension.

INVALID? as this is an extension problem?
(In reply to comment #1)
> You can open firefox in safe mode
> http://kb.mozillazine.org/Safe_mode
> 
> And then uninstall the extension.
> 
> INVALID? as this is an extension problem?

If you read my original forum posting you will see that the bug prevented me
from opening Firefox in Safe Mode. I don't know if this is an extension problem.
Note forum message from flanagan:

...When you observe that a process is moving up and down the list and is
difficult to click, it is because the list is sorted by CPU%. As the amount of
CPU usage changes, processes fly up and down the list. Just click on the Image
Name column header to sort by name and your process will stay put.
This is a TBP problem
read https://addons.mozilla.org/extensions/moreinfo.php?id=158&application=firefox

Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.