Recommended Posts

If you really understand as much as you claim to, then look through your list of installed add-ons if you want to troubleshoot your memory issues.

Already done, and I've compared my extensions with many people having the same issue, and the result is a no go. We didn't find the culprit. And since it happened right after 4.0.1 release, we are all blaming the core of Firefox.

And all of you here are mostly using nightly, guess why? :)

I'm sorry, but your logic is completely breaking apart here. How do rapid releases and the quality of each release have anything to do with each other? If anything, rapid release IMPROVES the stability released versions.

Why don't you take a calm down, take a deep breath, and think over what you really want to say instead of just being so desperate to hurl mud at Mozilla?

The rapid release of major version is killing the extensions system as it is now. Mozilla could have released minor version (ex: 4.1.0) instead of a major version imo.

Ho and no need to tell me to calm down, i'm calm since the beginning, but you instead ... :(

Already done, and I've compared my extensions with many people having the same issue, and the result is a no go. We didn't find the culprit. And since it happened right after 4.0.1 release, we are all blaming the core of Firefox.

Sure. And many of us are having zero issues with memory usage, same with many other tech sites performing memory benchmarks.

And all of you here are mostly using nightly, guess why? :)

And why would we need to guess? Of course "we" know perfectly well why "all of us" are "mostly" using future release channels. But I have a feeling that hardly stopped you from coming up with your wild speculations.

The rapid release of major version is killing the extensions system as it is now. Mozilla could have released minor version (ex: 4.1.0) instead of a major version imo.

Ho and no need to tell me to calm down, i'm calm since the beginning, but you instead ... :(

Cool, but that hardly has anything to do with your original tall tale of release quality going down the drain. See how you can actually come up with a legitimate critique of the rapid release system when you calm down instead of just trying to come up with whatever nonsense you can?

All that can be said is that Mozilla is working on the issue (with the Add-on SDK and automatic compat bumping), and there are ways around it on the user's end. Me, I just disable version checks and use Google Reader to keep up with extensions updates. Keep in mind that most extensions work perfectly well, and often all the developer has to do is login to AMO and bump their add-on's maxVersion data in two clicks. If they can't be arsed to do something that simple after 12 weeks of a new release baking in the Aurora and Beta channels, I'm not sure if all the blame should go to Mozilla.

I didn't find UX 64-bit branch, does that mean it's still for 'testing-testing-purposes' only (assuming nightly is for 'testing-purposes' itself :whistle:) or it's official but UX doesn't have it?

There is no 64-bit build of the UX branch. You can download the 32-bit build from here.

Sure. And many of us are having zero issues with memory usage, same with many other tech sites performing memory benchmarks.

I'm running Nightly with 30-40+ tabs for 3 daysnow without restart (ignoring the update, for now) and it's still using around 500mb. I'm really impressed with the current Nightly.

Keep in mind that most extensions work perfectly well, and often all the developer has to do is login to AMO and bump their add-on's maxVersion data in two clicks. If they can't be arsed to do something that simple after 12 weeks of a new release baking in the Aurora and Beta channels, I'm not sure if all the blame should go to Mozilla.

This.

Another speed up coming after a while. It looks promising to me. Now lets see.

https://bugzilla.moz...g.cgi?id=664249

one more memory reporter:

https://bugzilla.mozilla.org/show_bug.cgi?id=674721

Already done, and I've compared my extensions with many people having the same issue, and the result is a no go. We didn't find the culprit. And since it happened right after 4.0.1 release, we are all blaming the core of Firefox.

And all of you here are mostly using nightly, guess why? :)

Have you tried to create a new profile?

As I have said many times in this thread, I've been using FF since v4 was released, both developmental channels and final release versions without any aforementioned issues. There must be something that is only pertinent to you and your friends are experiencing.

The rapid release of major version is killing the extensions system as it is now. Mozilla could have released minor version (ex: 4.1.0) instead of a major version imo.

Ho and no need to tell me to calm down, i'm calm since the beginning, but you instead ... :(

Mozilla has put in a lot of effort to make the addon dev platform easier to use and allow devs to update them quicker to accommodate the changes in the released. But again, you cannot blame Mozilla if an addon breaks. It's up to the addon dev to troubleshoot the code and update it four times a year. Just about every popular addon has dedicated devs who are always on top of the latest changes in the code, which is why I have never come across an addon I use regularly that I am forced to disable.

As Samurizer mentioned, most popular apps utilize areas of FF core code that hardly changes between each release and all the addon needs is a version number change just so that it will pass FF compatibility check to let it install. How do you think all these addons are working perfectly on nightly/aurora builds without any issues that are already 2-3 releases ahead?

:angry: Backout:

https://bugzilla.moz...g.cgi?id=664249

Got one more point in HTMLTest because of https://bugzilla.moz...g.cgi?id=613662 fixed.

Awesome memory bug fix landed on mozilla-inbound branch:

https://bugzilla.moz...g.cgi?id=675132

I just wish I could get TabGroups Manager working properly with the Panorama feature in Aurora. I can get TabGroups Manager working, but it won't show the correct group title on the titlebar. There seems to be a conflict there. I have to go into Panorama and re-order my tab groups to fix it. Slightly annoying bug, but not bad enough to make me stop using Aurora. It's clearly waaaay better than Firefox 5 or even 6 beta. I'm thinking of trying Nightly again since I'm loving Aurora so much. How much faster is nightly compared to Aurora? I keep hearing numbers like it's 20% faster than Firefox 5, but I want to know how much faster it is compared to Aurora. Is it that much of a difference?

Hi

can someone give me link to change logs for Nightly 8.0a x64, I like to know what is landing in, what would be implement in future etc.

BTW. Since some time I'm use Nightly x64 and it is quite stable and fast, there is problem with Silverlight but Flash x64 beta is working without any problem ;)

Hi

can someone give me link to change logs for Nightly 8.0a x64, I like to know what is landing in, what would be implement in future etc.

BTW. Since some time I'm use Nightly x64 and it is quite stable and fast, there is problem with Silverlight but Flash x64 beta is working without any problem ;)

http://hg.mozilla.org/mozilla-central/pushloghtml?startdate=1+day+ago&enddate=now

Anyone else having problems viewing pics on facebook?

They stop loading after you see 5-15 pics.

yes and FB is being very laggy. has been for 2 wks. I think it's thier problem.

I'm havin that wierd glitch as well:

tAq4g.jpg

  • Like 2

The thing is that I have the issue only in firefox, tested with Opera 12 and the pics load fine.

I use latest Firefox Nightly and Stable version, the issue is in both.

I have disabled all add-ons, cleared cache, cookies... and the issue is still there.

And works fine in Safe Mode, tested now.

What I can do to see what is causing the problem?

open it in console mode and report here:

"C:\Program Files (x86)\Mozilla Firefox\firefox.exe" -p -no-remote -console

and post anything erratic

also you may want to go through process of elimination on your addons and see if any of them are the cause.

also you may want to: ipconfig /flushdns as well.

If you have noscript you may want to allow fbcdn.net as it's thier Content Distrubution Network and that's what they use for images.

if you've isolated all causes please file a bug report.

Time for 'Spot-the-change-in-the-default-theme':

<images here>

They removed the line left of the refresh button? ... I thought one of the reasons they made the site identity box the way it is now was to be symmetric with the refresh button... Not it's no longer symmetric and I don't see why they had to take the line out.

open it in console mode and report here:

"C:\Program Files (x86)\Mozilla Firefox\firefox.exe" -p -no-remote -console

and post anything erratic

also you may want to go through process of elimination on your addons and see if any of them are the cause.

also you may want to: ipconfig /flushdns as well.

If you have noscript you may want to allow fbcdn.net as it's thier Content Distrubution Network and that's what they use for images.

if you've isolated all causes please file a bug report.

The console is black, no info.

flushdns did not solve it

I don't use addons, I have only admuncher extension and .net

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Posts

    • OpenAI is rolling out a major upgrade to ChatGPT memory by Pradeep Viswanathan OpenAI is rolling out a major upgrade to ChatGPT's memory, making the system more capable, current, and scalable across long-term use. Memory allows ChatGPT to remember useful details about users, including their preferences, projects, and constraints. Instead of starting every conversation from scratch, ChatGPT can use this context to provide more relevant responses in future chats. OpenAI first launched saved memories in February 2024. That feature allowed users to explicitly ask ChatGPT to save information into its memory, such as travel plans or writing preferences. However, this system had limits because it depended heavily on users giving clear instructions to remember something. Additionally, saved memories could become stale over time. In April 2025, OpenAI expanded memory by allowing ChatGPT to reference past chat context outside the saved memories list. This was powered by a background process called “dreaming,” which automatically curates memories from chat history. This made ChatGPT better at learning from natural conversation without requiring users to manually save every detail. Today, OpenAI announced a more capable and compute-efficient memory architecture built on top of dreaming. This new system improves ChatGPT’s ability to carry forward useful context, follow user preferences, and remain accurate as time passes. According to OpenAI’s internal evaluations, the new system improves factual recall from 67.9% in 2025 to 82.8% in 2026. Preference adherence improves from 55.3% to 71.3%, while accuracy over time improves from 52.2% to 75.1%. The best part of this new system is a new memory summary page where users can review ChatGPT's memories. Users can even update details, correct information, or give instructions on what topics ChatGPT should bring up and when. This new, improved memory system is available to ChatGPT Plus and Pro users in the US starting today. It will roll out to more countries, as well as Free and Go users, in the coming weeks.
    • I work for a video production company in Australia. The camera operators shoot footage and then pass the SD card over to the editors. Much easier than handing over the entire camera. Plus, on a busy day you can hand off the SD card and then pop another in for the next shoot. Or, you might have used multiple SD cards because you need the extra space for a long shoot. I also use USB cables and wifi for transferring footage, but in many cases an SD card reader is the easiest method.
    • Microsoft Edge 149.0.4022.52 by Razvan Serea Microsoft Edge is a super fast and secure web browser from Microsoft. It works on almost any device, including PCs, iPhones and Androids. It keeps you safe online, protects your privacy, and lets you browse the web quickly. You can even use it on all your devices and keep your browsing history and favorites synced up. Built on the same technology as Chrome, Microsoft Edge has additional built-in features like Startup boost and Sleeping tabs, which boost your browsing experience with world class performance and speed that are optimized to work best with Windows. Microsoft Edge security and privacy features such as Microsoft Defender SmartScreen, Password Monitor, InPrivate search, and Kids Mode help keep you and your loved ones protected and secure online. Microsoft Edge has features to keep both you and your family protected. Enable content filters and access activity reports with your Microsoft Family Safety account and experience a kid-friendly web with Kids Mode. The new Microsoft Edge is now compatible with your favorite extensions, so it’s easy to personalize your browsing experience. Microsoft Edge 149.0.4022.52 changelog: Migration to improved V2 architecture for Workspaces. Workspaces, introduced in Edge in 2022, allows users to create durable sets of tabs that can be saved and shared with others. In order to improve reliability and performance of this feature, the following changes are being made: Migrating data for saved Workspaces from OneDrive/SharePoint to Edge Sync service Removing the collaboration/share functionality of this feature For organizations who have disabled Sync through policy, the existing v1 Workspace data will still be migrated to the new architecture. New v2 Workspaces created after migration won't sync across devices and will remain local to each device. This update occurs on a progressive rollout beginning in Edge Stable v145 and will continue rolling out in Edge v149. For more information, see Getting started with Microsoft Edge Workspaces. Feature Updates Passkey Sync for Enterprise Users. Microsoft Edge is introducing support for passkey synchronization for enterprise users, enabling secure, passwordless authentication across devices. Passkeys created in Edge can now be synced seamlessly, improving sign-in experience while maintaining strong security standards. Note: This is a controlled feature rollout. If you don't see this change, check back as we continue the rollout. Enterprise WebView2 runtime downgrade via DowngradeVersion policy. Administrators can temporarily roll back specific applications to a previous WebView2 Evergreen Runtime version (N-1 or N-2) using the new DowngradeVersion policy in msedgewebview2.admx. The Downgrade Version policy allows enterprises to mitigate critical regressions by specifying per-application exe-to-version mappings. The Edge Updater installs the target version side-by-side, and the WebView2 Loader redirects targeted apps accordingly. Downgrades auto-expire with each new WebView2 release: apps pinned to N-1 remain on the same version (now becoming N-2) and will auto-update in the next release, while apps pinned to N-2 will revert to the current Evergreen version. The policy applies only to enterprise-managed devices (domain-joined or MDM-enrolled). For more information, see Microsoft Edge WebView2 Policy Documentation | Microsoft Learn. Collections retirement. Collections has been removed in this update. Users can no longer access or use the feature. To keep saved content, users can export it, or move all pages to Favorites before updating to Microsoft Edge Stable 149. For more information, see Organize your ideas with Collections in Microsoft Edge - Microsoft Support. Modern, unified, and updated Look and Feel. Microsoft Edge has updated the Look and Feel to give customers a unified experience across all of Microsoft AI surfaces including Copilot and Bing. This changes multiple elements of the UX such as spacing, corners, fonts, default colors, etc. Clarify choices surrounding third-party cookie settings. Language under Settings > Privacy, search, and services > Cookies are clarified to better describe the choices users have in managing third-party cookies. Custom primary password retirement. Users are no longer able to create a new custom primary password in Edge Settings edge://settings/autofill/passwords/settings. Any users who are still using a custom primary password will be automatically migrated to device authentication. Additionally, the PrimaryPasswordSetting policy will no longer support the WithCustomPrimaryPassword option. For more information, see Keep your saved passwords private in Microsoft Edge | Microsoft Support. Unifying Copilot Chat policy controls. The Microsoft365CopilotChatIconEnabled policy is the standard for configuring Copilot Chat. Previously, this behavior was controlled by blocking the Copilot extension, either explicitly or by using the * wildcard via the ExtensionSettings or ExtensionInstallBlockList policies. Extension and sidebar policies no longer affect the appearance or functionality of Copilot Chat. Copilot address bar suggestions were also tied to extension policy settings. Starting in Microsoft Edge version 149, admins can use the CopilotAddressBarSuggestionsEnabled policy to manage this behavior. Intune MAM Protected Downloads. The protected downloads feature for Intune MAM is now available for BYOD (Bring Your Own Device) devices, which aren't managed by a tenant. Policy Updates / New policies CopilotAddressBarSuggestionsEnabled - Enable Copilot address bar suggestions CpuPerformanceTierOverride - Override for the CPU performance tier DataUrlInWebWorkerOpaqueOriginEnabled - Enable opaque origins for data URLs in Web Workers DefaultLocalFontsSetting - Default Local Fonts permission setting ForceForegroundPriorityForUrls - Force foreground priority for specific URLs LocalFontsAllowedForUrls - Allow Local Fonts permission on these sites LocalFontsBlockedForUrls - Block Local Fonts permission on these sites Deprecated policies WalletDonationEnabled - Wallet Donation Enabled (deprecated) EdgeWalletEtreeEnabled - Edge Wallet E-Tree Enabled (deprecated) Additional policy changes ForceForegroundPriorityForUrls - ForceForegroundPriorityForOrigins is renamed to ForceForegroundPriorityForUrls OnSecurityEventEnterpriseConnector - Add macOS platform support ProtectedContentIdentifiersAllowed - Remove macOS platform support Download: Microsoft Edge (64-bit) | 193.0 MB (Freeware) Download: Microsoft Edge (32-bit) | 170.0 MB Download: Microsoft Edge (ARM64) | 188.0 MB View: Microsoft Edge Website | Release History Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • User: "But is it good?" Microsoft: "Well, no. But it is less bad."
  • Recent Achievements

    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
    • Very Popular
      s0nic69 earned a badge
      Very Popular
    • Collaborator
      Asgardi earned a badge
      Collaborator
  • Popular Contributors

    1. 1
      +primortal
      471
    2. 2
      PsYcHoKiLLa
      247
    3. 3
      Skyfrog
      80
    4. 4
      FloatingFatMan
      67
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!