How can I wait updates til field-tested and de-bugged? I don't want the latest version right away.
This issue has frustrated me long time with Firefox. Some questions:
My update is set to NO, but firefox updates anyway. Why have the "no updates" option that doesn't work?
The "background install" doesn't stay in the background - just now, version 55.0.2, crashed my computer bc of massive memory consumption. Perhaps an "idle install" would help?
My experience is that the latest version often runs into conflicts with sites I visit. After a couple weeks, everything starts to work more smoothly. But the transition period? No thank you.
Many times, I've switched to Chrome, but that's a different kettle of problems, so I come back to firefox. I'd really like to use firefox exclusively, and not ever have to switch to Chrome, if you can get this sorted.
Thanks.
All Replies (6)
I have "Check for updates, but let you choose whether to install them" and that has worked for years. But I personally rarely wait more than a few days, so I don't know what happens if you wait several weeks.
For reference: Advanced panel - Accessibility, browsing, network, updates, and other advanced settings in Firefox.
RuthSmith said
The "background install" doesn't stay in the background - just now, version 55.0.2, crashed my computer bc of massive memory consumption. Perhaps an "idle install" would help?
I don't know what is going on there. Downloading an update is not very onerous for Firefox. ??
Not helpful. You didn't answer my questions about:
. wait til after debugging . "no updates" option being over-ridden . idle state install
Crash likely bc I had six tabs open, one with a player. Obviously not best procedure when updating, but bc it's a background update, I was not notified of update in progress, no request to close firefox.
> wait til after debugging
What debugging do you want to wait for? Firefox does a major version update every 6-8 weeks, after a 3 month test cycle. Only a small percentage of users are updated immediately so Mozilla can monitor for issues. There's often a quick bug fix within 7 days after release to respond to issues detected among the broader user population. Then assuming that tests well, the floodgates open.
> "no updates" option being over-ridden
I have no information on why your setting doesn't work, so I suggested my setting instead.
> idle state install
That doesn't mean anything to me. Perhaps someone else will know the fine details of when Firefox downloads an update which, as I said, is not a large file and should not be very taxing.
RuthSmith said
just now, version 55.0.2, crashed my computer bc of massive memory consumption.
How did that manifest? Did Firefox freeze, did Windows freeze, did Windows blue screen, etc.?
Some info on Firefox crashes: Troubleshoot Firefox crashes (closing or quitting unexpectedly)
Some info on Firefox freezes: Firefox hangs or is not responding - How to fix
Some info on memory usage: Firefox uses too much memory or CPU resources - How to fix
"idle state install" My computer anti-virus in-depth scan runs in "idle time" - those are its words. Idle time, to me, means when the computer is not under heavy demand, by the user, or for other updates, etc.
So what about it? Is it possible to have updates install during idle time?
The crash manifested with progressive, extreme slowing over a few minutes, video stopping, starting, stopping, and then all my tabs started trying to update themselves, or at least they were showing spinning circles, some pages had no content, white screen only. Bewildered, I started closing tabs, and the pages couldn't even close. Firefox was consuming over 2G memory.
I looked at a few of the links you sent, they are not useful. Firefox is not crashing or not responding all the time, it was only in the time that the update was installing.
Thanks.
Try my preferred update setting for a few cycles and see whether that helps.