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

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 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
*****

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 ::

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/03/2015 21:44, VanguardLH 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.

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.

Thanx for your detailed explanation which I found useful. I have finally
sorted things out and my F/Fx seems to be behaving at least for the time
being. Here is what procedure I followed which I posted in response to
another suggestion. It may be a duplication but I'll post it here as well.

Remainder of my message is a Copy and Paste job from a bit higher up the
thread..

Cleared F/Fx cache first. It still refused to start after sex. ;-)
(I mean x off!). I feel at this stage I should have restarted the
machine and try F/Fx again but I didn't.

Anyway, then I disabled all add-ons and enabled more or less all the
add-ons one by one. Everything seems to be running smoothly for the time
being. Though I believe all the add-ons that I have re-enabled had been
enabled earlier when F/Fx was misbehaving. One or two add-ons are still
disabled but I think those were actually disabled to begin with.

Problem soved but the enigma remains! So I decided not to trouble
trouble any further.

All's well that ends well, as they say. Thanks to everybody for all
your helpful suggestions.
--
choro
*****

"choro" wrote in message ...

On 30/03/2015 21:44, VanguardLH 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.

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.

Thanx for your detailed explanation which I found useful. I have finally
sorted things out and my F/Fx seems to be behaving at least for the time
being. Here is what procedure I followed which I posted in response to
another suggestion. It may be a duplication but I'll post it here as well.

Remainder of my message is a Copy and Paste job from a bit higher up the
thread..

Cleared F/Fx cache first. It still refused to start after sex. ;-)
(I mean x off!). I feel at this stage I should have restarted the machine
and try F/Fx again but I didn't.

Anyway, then I disabled all add-ons and enabled more or less all the
add-ons one by one. Everything seems to be running smoothly for the time
being. Though I believe all the add-ons that I have re-enabled had been
enabled earlier when F/Fx was misbehaving. One or two add-ons are still
disabled but I think those were actually disabled to begin with.

Problem soved but the enigma remains! So I decided not to trouble
trouble any further.

All's well that ends well, as they say. Thanks to everybody for all
your helpful suggestions.
--
choro
*****
FF 37.0 is now the latest version. Just installed it a few minutes ago. I
have FF set for Manual Update.
--
Buffalo

On Tue, 31 Mar 2015 09:16:19 -0600, Buffalo wrote:

"choro" wrote in message ...

On 30/03/2015 21:44, VanguardLH 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.

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.

Thanx for your detailed explanation which I found useful. I have finally
sorted things out and my F/Fx seems to be behaving at least for the time
being. Here is what procedure I followed which I posted in response to
another suggestion. It may be a duplication but I'll post it here as well.

Remainder of my message is a Copy and Paste job from a bit higher up the
thread..

Cleared F/Fx cache first. It still refused to start after sex. ;-)
(I mean x off!). I feel at this stage I should have restarted the machine
and try F/Fx again but I didn't.

Anyway, then I disabled all add-ons and enabled more or less all the
add-ons one by one. Everything seems to be running smoothly for the time
being. Though I believe all the add-ons that I have re-enabled had been
enabled earlier when F/Fx was misbehaving. One or two add-ons are still
disabled but I think those were actually disabled to begin with.

Problem soved but the enigma remains! So I decided not to trouble
trouble any further.

All's well that ends well, as they say. Thanks to everybody for all
your helpful suggestions.
--
choro
*****
FF 37.0 is now the latest version. Just installed it a few minutes ago. I
have FF set for Manual Update.

I thought I set FF to tell me, but it didn't. You led me to look, and it
seems 27.0 is ready for me.

While I'm at it, I'll check my settings too :-)

--
Gene E. Bloch (Stumbling Bloch)

On Tue, 31 Mar 2015 14:50:52 -0700, Gene E. Bloch wrote:

FF 37.0 is now the latest version. Just installed it a few minutes ago. I
have FF set for Manual Update.

I thought I set FF to tell me, but it didn't. You led me to look, and it
seems 27.0 is ready for me.

While I'm at it, I'll check my settings too :-)

The choices are limited. Auto update, Check but let me decide, and Don't
check.

The middle one is what I had (and still have) checked. Apparently it
does *not* include "notify me" :-)

--
Gene E. Bloch (Stumbling Bloch)

PROBLEM I REPORTED WAS SOLVED CROPPED UP AGAIN AND WITH A VENGEANCE!!!
Read on...

After I reported problem solved, it came back with a vengeance only a
few hours later. Forget about it not responding AFTER I had turned
Firefox off, Firefox (latest edition) refused to open any URL from
newsgroups EVEN WHILE it was up and running. Cost me a lot of time and
wasted effort trying anything I could think of. The only way I could get
Firefox to start again after being turned off was EITHER to reinstall it
OR Restart the computer. But I need Firefox for running a program that
Google Chrome has banned! It just won't allow IDM to run off Google
Chrome with Google accusing IDM of everything that Google is so famously
notorious about -- spying on users!!!

Finally I decided that the culprit must be the latest versions of
Firefox. SO, I installed version 34 instead and for the time being it is
working perfectly. No misbehaving! But I'll keep my fingers crossed.

So much for the so-called updates that tend to mess things up. I have
naturally configured Firefox NOT to update in any shape or form.

--
choro
*****

On 31/03/2015 00:44, choro wrote:
On 30/03/2015 21:44, VanguardLH 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.

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.

Thanx for your detailed explanation which I found useful. I have finally
sorted things out and my F/Fx seems to be behaving at least for the time
being. Here is what procedure I followed which I posted in response to
another suggestion. It may be a duplication but I'll post it here as well.

Remainder of my message is a Copy and Paste job from a bit higher up the
thread..

Cleared F/Fx cache first. It still refused to start after sex. ;-)
(I mean x off!). I feel at this stage I should have restarted the
machine and try F/Fx again but I didn't.

Anyway, then I disabled all add-ons and enabled more or less all the
add-ons one by one. Everything seems to be running smoothly for the time
being. Though I believe all the add-ons that I have re-enabled had been
enabled earlier when F/Fx was misbehaving. One or two add-ons are still
disabled but I think those were actually disabled to begin with.

Problem soved but the enigma remains! So I decided not to trouble
trouble any further.

All's well that ends well, as they say. Thanks to everybody for all
your helpful suggestions.
--
choro
*****