Any word if Firefox 17 is going to come out tomorrow the 20th


Recommended Posts

Hope my extensions are ready.

Quite a lot of changes in FF17, better read this: https://blog.mozilla.org/addons/2012/11/08/compatibility-for-firefox-17/

and confirm about compatibility yourself.

I really don't like the social features they are integrating into it, even if they are optional there are already addons that do that stuff. No need to build it right into the browser, that's just pointless feature creep. Have they forgotten what made Firefox popular in the first place?

Extended is probably the one that they're doing for businesses, i.e. it'll be extended support.

You know, when mozilla said businesses shouldn't be using firefox and made releases very fast so all business dumped firefox, they lost a lot of market share and now want it back again so said it was a little misunderstanding?

Actually Mozilla didn't say that. Mozilla said that businesses should be on the ESR channel, not the release channel.

As such they release a new version every 7 major builds that is an ESR build...and it will automatically take those businesses from 10 to 17.

Ok, I have tried the normal 17.0 release from a clean install of FF, not as an update and within a few moments, it froze and then crashed. Crashing my system also. I uninstalled it, ran Ccleaner and installed the ESR and I have been running the the ESR for over an hour now and no issues. Sorry to all you FF fans, but there is a differnce. ESR is much more stable and I would say it is probably meant for businesses. Businesses need a stable release, not a fly-by-night-bang-out-the-numbers-release and the release channel is crap.

Ok, I have tried the normal 17.0 release from a clean install of FF, not as an update and within a few moments, it froze and then crashed. Crashing my system also. I uninstalled it, ran Ccleaner and installed the ESR and I have been running the the ESR for over an hour now and no issues. Sorry to all you FF fans, but there is a differnce. ESR is much more stable and I would say it is probably meant for businesses. Businesses need a stable release, not a fly-by-night-bang-out-the-numbers-release and the release channel is crap.

sounds like you should have just upgraded instead of the clean install. ive been running 17 all afternoon w/o issue.

Ok, I have tried the normal 17.0 release from a clean install of FF, not as an update and within a few moments, it froze and then crashed. Crashing my system also. I uninstalled it, ran Ccleaner and installed the ESR and I have been running the the ESR for over an hour now and no issues. Sorry to all you FF fans, but there is a differnce. ESR is much more stable and I would say it is probably meant for businesses. Businesses need a stable release, not a fly-by-night-bang-out-the-numbers-release and the release channel is crap.

The ESR and standard release are the same, other than the update channel that they point to.

If the machine crashed then something in the system caused that...and Firefox runs in Userland...so you might want to look at that.

sounds like you should have just upgraded instead of the clean install. ive been running 17 all afternoon w/o issue.

I'll stick with the ESR release.

The ESR and standard release are the same, other than the update channel that they point to.

If the machine crashed then something in the system caused that...and Firefox runs in Userland...so you might want to look at that.

See above. It works for me.

I'll stick with the ESR release.

See above. It works for me.

I did see above. :p

My point was that if the whole system went down then something at the system level took it down...a driver or Windows service of some sort.

The browser itself runs in 'Userland' and can't take down the OS on its own...now it may have made a call to something...and that something failed and took the system down...but it still means you need to find out what caused it...since it is likely to happen again at some point.

I did see above. :p

My point was that if the whole system went down then something at the system level took it down...a driver or Windows service of some sort.

The browser itself runs in 'Userland' and can't take down the OS on its own...now it may have made a call to something...and that something failed and took the system down...but it still means you need to find out what caused it...since it is likely to happen again at some point.

Where would you like me to check?

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!