Firefox problem on Windows 7

On 30/03/2015 21:08:01, choro wrote:
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.

Are you using FF 32 bit edition or 64 bit edition?
I'm using FF 32 bit on Windows 7 64bit, it is more stable.
You can see which version by opening task manager while FF is running.

--
mick

On 30/03/2015 21:23:00, Char Jackson 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/

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.

I did just that when I had multiple instances running. Closed one and
the other six were still running, closed another and five instances
remained running. If you look in Task manager it shows the number of
FF's open in brackets.

--
mick

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.

Add-ons you install will affect the parent process. If an add-on hangs
or crashes when it loads, it will hang or crash Firefox. If an add-on
hangs or crashes when unloaded, it will hang or crash Firefox. Chromium
circumvented this dependency by using separate processes for each tab;
however, that means reloading the same add-on for each tab so if you
have a lot of add-ons and a lot of tabs then they consume memory for all
the duplicate instances of the add-ons. Still, Google Chrome will
likely only crash a tab's process instead of the web browser itself. (I
don't care for Google Chrome and it still has security features missing,
like disabling meta-refresh and letting me see to where a site wants to
redirect me. Both Firefox and Internet Explorer are susceptible to
crappy add-ons either because of poor coding or eventual incompatibility
with newer versions of the web browsers.

More likely you left old versions of add-ons installed as you progressed
through multiple newer versions of Firefox. Add-ons test during their
install if they are within a version range, not after they have been
installed. Do an update check on your add-ons to find out if there are
newer version of them. Else, disable all add-ons by using Firefox's
safe mode and retest. If Firefox behaves after disabling add-ons then
you'll have to disable them all and reenable them one at a time to
retest when the bad behavior returns and then get rid of that add-on.
Although Mozilla claims to review the code for add-ons they proffer at
their add-on site, there are still a ton of crappy add-ons and lots of
add-ons that conflict with each other plus those that don't work under
later versions of Firefox.

See if Firefox's safe mode eliminate the problem. If so, you have your
clue as to the culprit.

On 30-Mar-2015 16:32, mick wrote:
On 30/03/2015 21:23:00, Char Jackson 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/

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.

I did just that when I had multiple instances running. Closed one and
the other six were still running, closed another and five instances
remained running. If you look in Task manager it shows the number of
FF's open in brackets.


In Win8, right click the firefox.exe instead of individual and they will
all close.
In Win7 you can have 15 open and only 1 firefox.exe is showing in task
manager.

On 30 Mar 2015, choro wrote in
alt.windows7.general:

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.

I would disable all add-ons. If it behaves properly, I would enable
them again one-by-one until I discovered the problem one.

On 30 Mar 2015, mick wrote in
alt.windows7.general:

Are you using FF 32 bit edition or 64 bit edition?
I'm using FF 32 bit on Windows 7 64bit, it is more stable.

It should be more stable - the 64-bit Firefox is a test version only
and not officially generally released by Mozilla.

I use the 64-bit Blue Moon browser on my Win7-64 system, and I have had
no problems.

On 30/03/2015 21:23:00, Char Jackson 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/

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.

Well spotted Char, it is indeed win 8.1. I forget which computer I'm
on sometimes.
I have done your experiment on my Win 7 machine. I opened four
instances of FF. Each one was listed in Task Manager. If I close one
instance in task manager the other three remain open.
I have amended the link to show both windows versions.
http://micklord.com/testpage/

--
mick

On 30/03/2015 21:48:41, Disguised wrote:
On 30-Mar-2015 16:32, mick wrote:
On 30/03/2015 21:23:00, Char Jackson 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/

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.

I did just that when I had multiple instances running. Closed one and
the other six were still running, closed another and five instances
remained running. If you look in Task manager it shows the number of
FF's open in brackets.


In Win8, right click the firefox.exe instead of individual and they will all
close.

Agreed.

In Win7 you can have 15 open and only 1 firefox.exe is showing in task
manager.

????
Each instance running shows, or am I not looking in the right place,
see my screen shot http://micklord.com/testpage/

--
mick

On 30/03/2015 21:51:53, Nil wrote:
On 30 Mar 2015, choro wrote in
alt.windows7.general:

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.

I would disable all add-ons. If it behaves properly, I would enable
them again one-by-one until I discovered the problem one.

Agreed.

--
mick

On 30-Mar-2015 17:13, mick wrote:
On 30/03/2015 21:48:41, Disguised wrote:
On 30-Mar-2015 16:32, mick wrote:
On 30/03/2015 21:23:00, Char Jackson 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/

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.

I did just that when I had multiple instances running. Closed one and
the other six were still running, closed another and five instances
remained running. If you look in Task manager it shows the number of
FF's open in brackets.


In Win8, right click the firefox.exe instead of individual and they
will all close.

Agreed.

In Win7 you can have 15 open and only 1 firefox.exe is showing in task
manager.

????
Each instance running shows, or am I not looking in the right place, see
my screen shot http://micklord.com/testpage/


If you look under process there should be only 1 showing. It does in mine.

On Mon, 30 Mar 2015 21:53:21 +0200, 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

Me too, so consider mick's reply to this to apply to me as well :-)

--
Gene E. Bloch (Stumbling Bloch)

On 30/03/2015 22:24:51, Disguised wrote:
On 30-Mar-2015 17:13, mick wrote:
On 30/03/2015 21:48:41, Disguised wrote:
On 30-Mar-2015 16:32, mick wrote:
On 30/03/2015 21:23:00, Char Jackson 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/

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.

I did just that when I had multiple instances running. Closed one and
the other six were still running, closed another and five instances
remained running. If you look in Task manager it shows the number of
FF's open in brackets.


In Win8, right click the firefox.exe instead of individual and they
will all close.

Agreed.

In Win7 you can have 15 open and only 1 firefox.exe is showing in task
manager.

????
Each instance running shows, or am I not looking in the right place, see
my screen shot http://micklord.com/testpage/


If you look under process there should be only 1 showing. It does in mine.

That was interesting. I closed FF in the process tab of task manager
and it shut all four instances that were open. I then clicked the FF
icon on the task bar and it opened all four instances again with the
same web pages showing in each window. I was only expecting a new FF
window to open. Learn something new every day :-)

--
mick

On 30-Mar-2015 16:58, Nil wrote:
On 30 Mar 2015, mick wrote in
alt.windows7.general:

Are you using FF 32 bit edition or 64 bit edition?
I'm using FF 32 bit on Windows 7 64bit, it is more stable.

It should be more stable - the 64-bit Firefox is a test version only
and not officially generally released by Mozilla.

I use the 64-bit Blue Moon browser on my Win7-64 system, and I have had
no problems.


I know the moon is blue but the browser is called Palemoon. :-)

On 30-Mar-2015 17:44, mick wrote:
On 30/03/2015 22:24:51, Disguised wrote:
On 30-Mar-2015 17:13, mick wrote:
On 30/03/2015 21:48:41, Disguised wrote:
On 30-Mar-2015 16:32, mick wrote:
On 30/03/2015 21:23:00, Char Jackson 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/

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.

I did just that when I had multiple instances running. Closed one and
the other six were still running, closed another and five instances
remained running. If you look in Task manager it shows the number of
FF's open in brackets.


In Win8, right click the firefox.exe instead of individual and they
will all close.

Agreed.

In Win7 you can have 15 open and only 1 firefox.exe is showing in task
manager.

????
Each instance running shows, or am I not looking in the right place, see
my screen shot http://micklord.com/testpage/


If you look under process there should be only 1 showing. It does in
mine.

That was interesting. I closed FF in the process tab of task manager
and it shut all four instances that were open. I then clicked the FF
icon on the task bar and it opened all four instances again with the
same web pages showing in each window. I was only expecting a new FF
window to open. Learn something new every day :-)


That's the auto recovery part of FF when it's not shut down properly
(crash).

There will always be only 1 process running what you see in Applications
are off-shout of the firefox.exe process.

Like having a main folder with sub-folders. You can delete the
sub-folders individually but if you delete the main folder then all the
subs are gone.

On 30 Mar 2015, Disguised wrote in
alt.windows7.general:

I know the moon is blue but the browser is called Palemoon. :-)

Oops! I had my web browser and last night's beer all mashed up in my
brain. No wonder the bartender was looking at me funny.