Firefox problem on Windows 7

Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I tick a
link it refuses to start and link up. I have a sneaking suspicion that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly Firefox
started refusing to re-start. It won't even start when I click my
desktop shortcut let alone start when I click a link on the Usenet.

Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off and
then on again.
--
choro
*****

choro wrote:
Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I tick a
link it refuses to start and link up. I have a sneaking suspicion that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly
Firefox started refusing to re-start. It won't even start when I
click my desktop shortcut let alone start when I click a link on the
Usenet.
Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off
and then on again.

Have you checked Task Manager to see if FF is still active after you "click
it off"? If so, perhaps it (FF) won't allow two instances.

--

dadiOH
____________________________

Winters getting colder? Tired of the rat race?
Taxes out of hand? Maybe just ready for a change?
Check it out... http://www.floridaloghouse.net

On Mon, 30 Mar 2015 13:21:39 -0400, "dadiOH" wrote:

choro wrote:
Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I tick a
link it refuses to start and link up. I have a sneaking suspicion that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly
Firefox started refusing to re-start. It won't even start when I
click my desktop shortcut let alone start when I click a link on the
Usenet.
Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off
and then on again.

Have you checked Task Manager to see if FF is still active after you "click
it off"? If so, perhaps it (FF) won't allow two instances.

That was my thought, as well. If he kills it in Task Manager it should
restart without issues. The question, then, is why isn't it fully exiting in
a timely manner? I assume it will eventually drop off, but not as quick as
expected.

--

Char Jackson

On Mon, 30 Mar 2015 12:39:57 -0500, Char Jackson
wrote:

On Mon, 30 Mar 2015 13:21:39 -0400, "dadiOH" wrote:

choro wrote:
Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I tick a
link it refuses to start and link up. I have a sneaking suspicion that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly
Firefox started refusing to re-start. It won't even start when I
click my desktop shortcut let alone start when I click a link on the
Usenet.
Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off
and then on again.

Have you checked Task Manager to see if FF is still active after you "click
it off"? If so, perhaps it (FF) won't allow two instances.

That was my thought, as well. If he kills it in Task Manager it should
restart without issues. The question, then, is why isn't it fully exiting in
a timely manner? I assume it will eventually drop off, but not as quick as
expected.

Maybe an FF update is in progress? I've had a few cases where the
update took an unexpectedly long time.

On 30/03/2015 20:07, Mike Paff wrote:
On Mon, 30 Mar 2015 12:39:57 -0500, Char Jackson
wrote:

On Mon, 30 Mar 2015 13:21:39 -0400, "dadiOH" wrote:

choro wrote:
Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I tick a
link it refuses to start and link up. I have a sneaking suspicion that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly
Firefox started refusing to re-start. It won't even start when I
click my desktop shortcut let alone start when I click a link on the
Usenet.
Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off
and then on again.

Have you checked Task Manager to see if FF is still active after you "click
it off"? If so, perhaps it (FF) won't allow two instances.

That was my thought, as well. If he kills it in Task Manager it should
restart without issues. The question, then, is why isn't it fully exiting in
a timely manner? I assume it will eventually drop off, but not as quick as
expected.

Maybe an FF update is in progress? I've had a few cases where the
update took an unexpectedly long time.


I use FF 36.0.4 on W7 64b Pro fully updated. No problems here.
In a rare occasion FF crashed and I was not able to start it until I
killed FF in the Task Manager. So FF won't let 2 instances run at the
same time. But why is it not exiting in a normal manner? Perhaps
uninstalling completely and a new install?

Fokke

En el artículo , Char
Jackson escribió:

The question, then, is why isn't it fully exiting in
a timely manner?

It takes a while to swap out of the page file when it has been running
for a while (a few days +) with many tabs open. When I close Firefox, I
have to wait for the hard disc activity light to stop flashing before I
can restart it.

--
:: je suis Charlie :: yo soy Charlie :: ik ben Charlie ::

On 03/30/2015 01:47 PM, Fokke Nauta wrote:
On 30/03/2015 20:07, Mike Paff wrote:
On Mon, 30 Mar 2015 12:39:57 -0500, Char Jackson
wrote:

On Mon, 30 Mar 2015 13:21:39 -0400, "dadiOH" wrote:

choro wrote:
Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I tick a
link it refuses to start and link up. I have a sneaking suspicion that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly
Firefox started refusing to re-start. It won't even start when I
click my desktop shortcut let alone start when I click a link on the
Usenet.
Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off
and then on again.

Have you checked Task Manager to see if FF is still active after you
"click
it off"? If so, perhaps it (FF) won't allow two instances.

That was my thought, as well. If he kills it in Task Manager it should
restart without issues. The question, then, is why isn't it fully
exiting in
a timely manner? I assume it will eventually drop off, but not as
quick as
expected.

Maybe an FF update is in progress? I've had a few cases where the
update took an unexpectedly long time.


I use FF 36.0.4 on W7 64b Pro fully updated. No problems here.
In a rare occasion FF crashed and I was not able to start it until I
killed FF in the Task Manager. So FF won't let 2 instances run at the
same time. But why is it not exiting in a normal manner? Perhaps
uninstalling completely and a new install?

Fokke





Uninstalling and re-installing will do nothing as the profile would need
to be manually deleted. Occasionally I have had a similar problem and
found that clearing cache helps

On 30/03/2015 19:47:13, Fokke Nauta wrote:
On 30/03/2015 20:07, Mike Paff wrote:
On Mon, 30 Mar 2015 12:39:57 -0500, Char Jackson
wrote:

On Mon, 30 Mar 2015 13:21:39 -0400, "dadiOH" wrote:

choro wrote:
Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I tick a
link it refuses to start and link up. I have a sneaking suspicion that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly
Firefox started refusing to re-start. It won't even start when I
click my desktop shortcut let alone start when I click a link on the
Usenet.
Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off
and then on again.

Have you checked Task Manager to see if FF is still active after you
"click
it off"? If so, perhaps it (FF) won't allow two instances.

That was my thought, as well. If he kills it in Task Manager it should
restart without issues. The question, then, is why isn't it fully exiting
in
a timely manner? I assume it will eventually drop off, but not as quick as
expected.

Maybe an FF update is in progress? I've had a few cases where the
update took an unexpectedly long time.


I use FF 36.0.4 on W7 64b Pro fully updated. No problems here.
In a rare occasion FF crashed and I was not able to start it until I killed
FF in the Task Manager. So FF won't let 2 instances run at the same time

I have just tried multiple instances of FireFox on Win 7, I got bored
after opening seven. Photo here http://micklord.com/testpage/

--
mick

On Mon, 30 Mar 2015 20:40:04 +0100, mick wrote:

On 30/03/2015 19:47:13, Fokke Nauta wrote:
On 30/03/2015 20:07, Mike Paff wrote:
On Mon, 30 Mar 2015 12:39:57 -0500, Char Jackson
wrote:

On Mon, 30 Mar 2015 13:21:39 -0400, "dadiOH" wrote:

choro wrote:
Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I tick a
link it refuses to start and link up. I have a sneaking suspicion that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly
Firefox started refusing to re-start. It won't even start when I
click my desktop shortcut let alone start when I click a link on the
Usenet.
Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off
and then on again.

Have you checked Task Manager to see if FF is still active after you
"click
it off"? If so, perhaps it (FF) won't allow two instances.

That was my thought, as well. If he kills it in Task Manager it should
restart without issues. The question, then, is why isn't it fully exiting
in
a timely manner? I assume it will eventually drop off, but not as quick as
expected.

Maybe an FF update is in progress? I've had a few cases where the
update took an unexpectedly long time.


I use FF 36.0.4 on W7 64b Pro fully updated. No problems here.
In a rare occasion FF crashed and I was not able to start it until I killed
FF in the Task Manager. So FF won't let 2 instances run at the same time

I have just tried multiple instances of FireFox on Win 7, I got bored
after opening seven. Photo here http://micklord.com/testpage/

I didn't believe you, so I tried it.

But I stopped after only two windows :-)

Task Manager show two instances of Firefox, so now I believe you.

--
Gene E. Bloch (Stumbling Bloch)

On 30/03/2015 21:47, Gene E. Bloch wrote:
On Mon, 30 Mar 2015 20:40:04 +0100, mick wrote:

On 30/03/2015 19:47:13, Fokke Nauta wrote:
On 30/03/2015 20:07, Mike Paff wrote:
On Mon, 30 Mar 2015 12:39:57 -0500, Char Jackson
wrote:

On Mon, 30 Mar 2015 13:21:39 -0400, "dadiOH" wrote:

choro wrote:
Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I tick a
link it refuses to start and link up. I have a sneaking suspicion that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly
Firefox started refusing to re-start. It won't even start when I
click my desktop shortcut let alone start when I click a link on the
Usenet.
Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off
and then on again.

Have you checked Task Manager to see if FF is still active after you
"click
it off"? If so, perhaps it (FF) won't allow two instances.

That was my thought, as well. If he kills it in Task Manager it should
restart without issues. The question, then, is why isn't it fully exiting
in
a timely manner? I assume it will eventually drop off, but not as quick as
expected.

Maybe an FF update is in progress? I've had a few cases where the
update took an unexpectedly long time.


I use FF 36.0.4 on W7 64b Pro fully updated. No problems here.
In a rare occasion FF crashed and I was not able to start it until I killed
FF in the Task Manager. So FF won't let 2 instances run at the same time

I have just tried multiple instances of FireFox on Win 7, I got bored
after opening seven. Photo here http://micklord.com/testpage/

I didn't believe you, so I tried it.

But I stopped after only two windows :-)

Task Manager show two instances of Firefox, so now I believe you.


Yes, FF allows you to run multiple instances, but what I tried to say is
this: When it exites in a normal way, you can restart it again. But when
it crashes and an instance is still running in the Task Mgr, it will not
start again. Only when that instance that runs in the Task Mgr is
killed, you can start FF again. I've been there.

Fokke

On 30/03/2015 20:51, philo wrote:
On 03/30/2015 01:47 PM, Fokke Nauta wrote:
On 30/03/2015 20:07, Mike Paff wrote:
On Mon, 30 Mar 2015 12:39:57 -0500, Char Jackson
wrote:

On Mon, 30 Mar 2015 13:21:39 -0400, "dadiOH"
wrote:

choro wrote:
Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I
tick a
link it refuses to start and link up. I have a sneaking suspicion
that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly
Firefox started refusing to re-start. It won't even start when I
click my desktop shortcut let alone start when I click a link on the
Usenet.
Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off
and then on again.

Have you checked Task Manager to see if FF is still active after you
"click
it off"? If so, perhaps it (FF) won't allow two instances.

That was my thought, as well. If he kills it in Task Manager it should
restart without issues. The question, then, is why isn't it fully
exiting in
a timely manner? I assume it will eventually drop off, but not as
quick as
expected.

Maybe an FF update is in progress? I've had a few cases where the
update took an unexpectedly long time.


I use FF 36.0.4 on W7 64b Pro fully updated. No problems here.
In a rare occasion FF crashed and I was not able to start it until I
killed FF in the Task Manager. So FF won't let 2 instances run at the
same time. But why is it not exiting in a normal manner? Perhaps
uninstalling completely and a new install?

Fokke





Uninstalling and re-installing will do nothing as the profile would need
to be manually deleted. Occasionally I have had a similar problem and
found that clearing cache helps

Ofcourse you'll need to delete the profile. That's why I wrote
"uninstalling completely". But perhaps I wasn't clear enough.

On 30/03/2015 19:47, Fokke Nauta wrote:
On 30/03/2015 20:07, Mike Paff wrote:
On Mon, 30 Mar 2015 12:39:57 -0500, Char Jackson
wrote:

On Mon, 30 Mar 2015 13:21:39 -0400, "dadiOH" wrote:

choro wrote:
Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I tick a
link it refuses to start and link up. I have a sneaking suspicion that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly
Firefox started refusing to re-start. It won't even start when I
click my desktop shortcut let alone start when I click a link on the
Usenet.
Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off
and then on again.

Have you checked Task Manager to see if FF is still active after you
"click
it off"? If so, perhaps it (FF) won't allow two instances.

That was my thought, as well. If he kills it in Task Manager it should
restart without issues. The question, then, is why isn't it fully
exiting in
a timely manner? I assume it will eventually drop off, but not as
quick as
expected.

Maybe an FF update is in progress? I've had a few cases where the
update took an unexpectedly long time.


I use FF 36.0.4 on W7 64b Pro fully updated. No problems here.
In a rare occasion FF crashed and I was not able to start it until I
killed FF in the Task Manager. So FF won't let 2 instances run at the
same time. But why is it not exiting in a normal manner? Perhaps
uninstalling completely and a new install?

Fokke

No, it does NOT show up on Task Manager. Not once it is X'ed off. I've
also tried uninstall and reinstall. It soon reverts to its old tricks
again. I know all I have to do is to minimize it rather that X it off
but old habits die hard. It is really annoying.

As for not being allowed to run in 2 instances, Firefox does and run in
more just 2 but in multiple instances just by opening another completely
new run with each instance with actually with quite a few tabs. In that
respect Firefox is really versatile.

I believe the problem arises because my Firefox does not fully shut down
when it is X'ed off even though it is not shown as a running program in
Task Manager.
--
choro
*****

On 30/03/2015 20:47:17, Gene E. Bloch wrote:
On Mon, 30 Mar 2015 20:40:04 +0100, mick wrote:

On 30/03/2015 19:47:13, Fokke Nauta wrote:
On 30/03/2015 20:07, Mike Paff wrote:
On Mon, 30 Mar 2015 12:39:57 -0500, Char Jackson
wrote:

On Mon, 30 Mar 2015 13:21:39 -0400, "dadiOH" wrote:

choro wrote:
Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I tick a
link it refuses to start and link up. I have a sneaking suspicion that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly
Firefox started refusing to re-start. It won't even start when I
click my desktop shortcut let alone start when I click a link on the
Usenet.
Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off
and then on again.

Have you checked Task Manager to see if FF is still active after you
"click
it off"? If so, perhaps it (FF) won't allow two instances.

That was my thought, as well. If he kills it in Task Manager it should
restart without issues. The question, then, is why isn't it fully exiting
in
a timely manner? I assume it will eventually drop off, but not as quick
as expected.

Maybe an FF update is in progress? I've had a few cases where the
update took an unexpectedly long time.


I use FF 36.0.4 on W7 64b Pro fully updated. No problems here.
In a rare occasion FF crashed and I was not able to start it until I killed
FF in the Task Manager. So FF won't let 2 instances run at the same time

I have just tried multiple instances of FireFox on Win 7, I got bored
after opening seven. Photo here http://micklord.com/testpage/

I didn't believe you, so I tried it.

But I stopped after only two windows :-)

Task Manager show two instances of Firefox, so now I believe you.

:-)

--
mick

On 30/03/2015 20:53:21, Fokke Nauta wrote:
On 30/03/2015 21:47, Gene E. Bloch wrote:
On Mon, 30 Mar 2015 20:40:04 +0100, mick wrote:

On 30/03/2015 19:47:13, Fokke Nauta wrote:
On 30/03/2015 20:07, Mike Paff wrote:
On Mon, 30 Mar 2015 12:39:57 -0500, Char Jackson
wrote:

On Mon, 30 Mar 2015 13:21:39 -0400, "dadiOH"
wrote:

choro wrote:
Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I tick
a
link it refuses to start and link up. I have a sneaking suspicion
that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly
Firefox started refusing to re-start. It won't even start when I
click my desktop shortcut let alone start when I click a link on the
Usenet.
Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off
and then on again.

Have you checked Task Manager to see if FF is still active after you
"click
it off"? If so, perhaps it (FF) won't allow two instances.

That was my thought, as well. If he kills it in Task Manager it should
restart without issues. The question, then, is why isn't it fully
exiting
in
a timely manner? I assume it will eventually drop off, but not as quick
as
expected.

Maybe an FF update is in progress? I've had a few cases where the
update took an unexpectedly long time.


I use FF 36.0.4 on W7 64b Pro fully updated. No problems here.
In a rare occasion FF crashed and I was not able to start it until I
killed
FF in the Task Manager. So FF won't let 2 instances run at the same time

I have just tried multiple instances of FireFox on Win 7, I got bored
after opening seven. Photo here http://micklord.com/testpage/

I didn't believe you, so I tried it.

But I stopped after only two windows :-)

Task Manager show two instances of Firefox, so now I believe you.


Yes, FF allows you to run multiple instances, but what I tried to say is
this: When it exites in a normal way, you can restart it again. But when it
crashes and an instance is still running in the Task Mgr, it will not start
again. Only when that instance that runs in the Task Mgr is killed, you can
start FF again. I've been there.

Fokke

Ah yes Fokke, I have been there and now understand what you meant to
say originally. If one instance of FF crashes you cannot open another
until that instance it is killed in Task Manager. :-)

--
mick

On Mon, 30 Mar 2015 20:40:04 +0100, mick wrote:

On 30/03/2015 19:47:13, Fokke Nauta wrote:
On 30/03/2015 20:07, Mike Paff wrote:
On Mon, 30 Mar 2015 12:39:57 -0500, Char Jackson
wrote:

On Mon, 30 Mar 2015 13:21:39 -0400, "dadiOH" wrote:

choro wrote:
Recently Mozilla Firefox has started misbehaving on my Windows 7 Pro
machine. Both Windows and Firefox fully updated.

Firefox will function normally until it is x'ed off. After that it
refuses to restart and although it is my default browser when I tick a
link it refuses to start and link up. I have a sneaking suspicion that
this is a clash between the latest updates of Windows 7 and Firefox
because until recently everything ran very smoothly and suddenly
Firefox started refusing to re-start. It won't even start when I
click my desktop shortcut let alone start when I click a link on the
Usenet.
Any others with this problem? Firefox is OK after I first start the
machine or do a restart. But once I click Firefox off, that's it. It
will NOT come up again until a Restart or until I turn my mahine off
and then on again.

Have you checked Task Manager to see if FF is still active after you
"click
it off"? If so, perhaps it (FF) won't allow two instances.

That was my thought, as well. If he kills it in Task Manager it should
restart without issues. The question, then, is why isn't it fully exiting
in
a timely manner? I assume it will eventually drop off, but not as quick as
expected.

Maybe an FF update is in progress? I've had a few cases where the
update took an unexpectedly long time.


I use FF 36.0.4 on W7 64b Pro fully updated. No problems here.
In a rare occasion FF crashed and I was not able to start it until I killed
FF in the Task Manager. So FF won't let 2 instances run at the same time

I have just tried multiple instances of FireFox on Win 7, I got bored
after opening seven. Photo here http://micklord.com/testpage/

For me on Win 7, I have 6 instances of Firefox on the Taskbar and combined
they have about 45-50 tabs open, but Task Manager shows just a single
instance of Firefox running. That's how Firefox has always worked here. With
Firefox running, if I try to start it again I just get another window and of
course another Taskbar icon. It's still just a single instance of the
running program, however, or at least that's how it looks here. The Task
Manager pic in the link above seems to show the same thing, although it
looks more like Win 8 in the pic.

I would conclude that Firefox only allows a single instance of the program
to run at a time. You can stack multiple windows (tabbed or not) on top of
that one instance, but I'd say it's still a single instance. Try this as an
experiment: kill the one instance of Firefox in Task Manager and see if all
of your Firefox windows don't all collapse at once. They do, here. If
multiple instances of the program were running, some windows would survive.

--

Char Jackson