In looking into this, I found that just about all my logins worked OK except for a few. Over time, a loooong time, every now and then the Logins manager has prompted to save login data for sites I already had in Saved Logins. I never thought much of this, more of an annoyance than a bug. For example, I had two for the Wilders URL - one for username and username@email... Same password. This and a bunch of others were the ones that failed to populate fields in v49 after entering the Master password. Once I purged the duplicates, everything is back to normal. My logins.json is ancient and contained data migrated from the previous logins scheme. Which ages ago was sqlite, if I remember correctly. So the convolutions in my data tolerated in 48 and much earlier is no longer tolerated. Which is good. Users heavily dependent on Saved Logins should check their listing for multiple entries for the same URL. (And no, I don't use any browser password manager for anything important. Forums, news, entertainment sites and the like are it.)
Whats New In Cyberfox? Release Type: Major Update! Latest Build Info: Cyberfox 49.0.1 Reference link to Cyberfox 49.0 release notes New: Show notifications page on first install and after update. Fixed: Passed patch for Bug 1282750 - Convert AboutCache to use AsyncOpen2() Cyberfox Installer Updated: Installer script to version 2.5.4
Did this new version fix your issue? Re: https://www.wilderssecurity.com/threads/mozilla-firefox.388154/page-4#post-2625276
Hi JR, Sadly, no. I've made a few changes with my extensions since then but even disabling uBO and temporarily allowing all in NoScript the stations won't play.
You sir just saved me lots of time wasting and digging! You deserve a hug! EDIT: I'd even go so far as to say that restoring to default is not a good idea, cos default means being able to undo 10 closed tabs and 3 closed windows - well, not sure if there's anything wrong with what I did but I set it to be able to restore way many more tabs than the default 10 and also more than 3 window ...
For a coder, Toady sure gets a lot of sleep. 50 should be interesting. I can hardly handle the suspense...
Release Pending. Released! Whats New In Cyberfox? Release Type: Major Update! Latest Build Info: Cyberfox 50.0 Fixed: [MDC] Identity popup icon Updated: Preference popup window back end Updated: User-agent default overrides list Updated: agents.json New: Clone tab url to private window Adjusted: Update and unify cyberfox custom icons Fixed: App menu restart browser missing icon Fixed: [MDC] Update extensions patch, Missing Preferences.jsm import Fixed: Build failure with mochitest enabled New: [Optional] User controlled flash plugin (Restart Required) See FAQ article New: Internal update system, Learn more here Fixed: Increase time between startup update checks Added: Show update information page on browser startup Fixed: Make notifications page powered by user preference See FAQ article New: Make release notes page powered by user preference See FAQ article Added: Add option to toggle SHA512 verification of updates See FAQ article Updated: language auto patch files Fixed: Regex filter with double digets in beta update checking Updated: Updated: Ru (Russian) localization (Thanks @Eroppo) Updated: Update Pl (Polish) localization (Thanks @hawkeye116477) Fixed: Issue with update.ini generation for archived version New: Plugin free Netflix, Stan and other services using HTML5 video Updated: Default shipped blocklist Cyberfox Installer Updated: Apply changes for visual elements xml New: Installers dual signed with SHA1 & SHA256 signatures Fixed: Remove SHA512SUMS due to hash generation changes New: Add files for new internal updater New: --run command line argument to installer, Learn more here Fixed: Updater.exe not been digitally signed during installer generation Added: Check if cpu supports SSE2 New: Skip license page if already installed (Faster Installations) Added: Update callback command to installer Updated: Updated: Ru (Russian) installer localization (Thanks @Eroppo) Updated: Update Pl (Polish) installer localization (Thanks @hawkeye116477) Updated: Installer script to version 2.5.7
Messing with browser.tabs.remote aka e10s aka Electrolysis aka multiprocess... (Don't you love the way terminology is standardized in the Mozilla universe?) • Cyberfox Portable 50.0 Intel x64 - Windows 7 HP SP1 x64 Multiprocess in 48 was sad in my setup. With 50 I thought I'd give it another shot. There've been plenty of updates to the 21 extensions I use since 48. I set browser.tabs.remote.autostart to true and restarted. about:support reports "disabled by add-ons" for Mutliprocess Windows So I created browser.tabs.remote.force-enable, set to true and restarted. about:support now reports "Enabled by user" The Add-on Compatibility Reporter extension shows seven of my add-ons as multiprocess incompatible but gives all of them a green check mark and all seven of them work A-OK. During my intuhnetz surfing for about an hour last night and a couple of hours this morning there have been no issues. Without running for real benchmarks, my seat-of-pants test reports a nicely snappier browsing experience. So, an add-on can be incompatible and still continue to function which was not the result I got back in 48. I don't know if that's because of 50, the add-ons themselves or a combination of the two. Either way, time has yet to tell but I'm thinking I'll be hanging with multiprocess from now on.
RE Secunia PSI - I tried to explain that Cyberfox had an inbuilt update system now and at first I was told, "Please uninstall cyberfox update manager after updating to Cyberfox 50”. After explaining to Flexera that I never installed Cyberfox Update Manager and that the program I suggested them only installed with CF50 they completely ignored my advice, so they can go jump off a short plank!
Release Type: Security Update! Latest Build Info: Cyberfox 50.0.1 Reference link to Cyberfox 50.0 release notes Fixed: Enable plugins.asyncdrawing by default. Updated: Default shipped blocklist This is the first version that has updated on my machines using the new updater built into Cyberfox.
Refer to my post above regarding e10s aka Electrolysis aka multiprocess. Having set browser.tabs.remote.autostart and browser.tabs.remote.force-enable to true and running as such without issue since then, the next step is: dom.ipc.processCount - I bumped the default from 1 to 2. No issues after three days. (Note this setting should not exceed the number of your processor threads.) Cyberfox is considerably snappier. Content bloated sites I've been visiting daily for years that took a blink or two to render now render near-instantly. Cyberfox Portable 50.0.2 Intel x64 - Windows 7 HP SP1 x64 I should also note hardware is i7-3770K on a Z77 mobo and 16MB RAM. Using on-board Intel graphics, no GPU card. And an i5-2430M/HM65 laptop, 4GB RAM. Your experience may vary.
I tried to activate multiprocess, but could not do so because some addons were disabling it. I used the force-enable option, and it worked, but embedded Youtube videos did not show up quickly in some forums. After disabling it, I went back to this thread, found out about the ACR and installed it, and found out that all addons have green check marks. Edit: Sorry, I got confused by the check marks. Several of the addons are not compatible, so I have to disable the process. However, the browser worked fine as long as I don't activate the dom process count.
Whats New In Cyberfox? Release Type: Security Update! Latest Build Info: Cyberfox 50.1.0 Reference link to Cyberfox 50.0 release notes Reference link to Cyberfox 50.0.1 release notes Reference link to Cyberfox 50.0.2 release notes Fixed: Search engine removal
Latest Build Info: Cyberfox 50.1.1 Release Type: Minor Update! Cyberfox 50.1.1 Reference link to Cyberfox 50.0 release notes Reference link to Cyberfox 50.0.1 release notes Reference link to Cyberfox 50.0.2 release notes Reference link to Cyberfox 50.1.0 release notes Fixed: Web extensions ID requirement to install Revert: Increase time between startup update checks Fixed: Restart browser Panel-UI button hover Adjusted: about:home gui when resized smaller than 540px wide Updated: Default shipped blocklist Updated: windowed preference sync back-end Updated: windowed preferences back-end Fixed: Added back plugin check see Updated: language patches Moved: update options to updates tab
Using new internal updater, it starts downloadng (very slowly), but then I get 'SHA512 validation of package has failed ...' (see below). Anyone else experiencing this?
#74 follow up It took 6 minutes to download. Apparently stuck after verification completed. It seems VS blocked the process without giving any warning for the first 3 trials. VS gave two warnings at the fourth attempt, I allowed. Update successful now.