Language Selection

English French German Italian Portuguese Spanish

Firefox 15 Beta Tackles Memory Leaks

Filed under
Moz/FF

Mozilla has released a beta version of the next version of its Firefox browser with better memory management and significant speed improvements.

"Firefox 15 prevents most memory leaks caused by add-ons, including Firebug," Nicholas Nethercote writes in a Mozilla blog. Firebug is a Firefox add-on for debugging web pages.

"For many users with add-ons installed, this will significantly reduce Firefox’s memory consumption, without requiring upgrades to those add-ons," he adds. "For those users, Firefox 15 is likely to be faster (sometimes drastically so) and less likely to crash, especially if they have multiple add-ons installed and/or keep Firefox running for a long time between restarts."

Rest here

Also: Mozilla Releases Test Version of Firefox OS




Firefox 15

Mozilla needs to get a new buzzword list, EVERY release according to them has better memory management and is significantly faster.

I've yet to update Firefox and go WOWEE that's fast, which to me, would be the appropriate reaction to a truly SIGNIFICANTLY faster browser.

Nor in 14 release have they fixed their ginormous memory sieve problems, so I won't hold my breath. And that's a basic no-addon's install, so nice try Mozilla, but I don't think Addon's are the root of your memory problems.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Leftovers: OSS and Sharing

  • Wal-Mart Proves Open Source Is Big Business
  • Keeping the FCC and Open Source Happy
    The FCC is worried. You and they spend all this time and energy getting your radio certified, and then some bozo hacks in, changes how the radio works, and puts you out of spec. And so, back in early 2015, the FCC issued some guidelines or questions regarding WiFi devices – particularly home routers – in an effort to ensure that your radio isn’t hackable. The result has been that some router makers have simply locked down the platform so that it’s no longer possible to do after-market modifications, and this has caused an outcry by after-market modifiers. The reason why it’s an issue is that these open-source developers have used the platform for adding apps or other software that, presumably, have nothing to do with the radio. In an attempt to find the magic middle way, the prpl organization, headed by Imagination Technologies (IMG) and featuring the MIPS architecture, recently put out a proof of concept that they say gives both assurance to the FCC and freedom to open-source developers. Questions from the FCC
  • Wire open-sources messaging client, woos developers
    Communications startup Wire has open-sourced the full codebase for its Wire app, so it's easier for developers to build their own encrypted messaging clients. Wire open-sourced the rest of the client base that wasn't initially publicly available, including components related to the user interface, the web and native clients, and some internal developer tools. The company always planned to open-source the codebase, but didn't start out that way initially "because we were still working on other features," Alan Duric, co-founder and CTO of Wire, wrote in a Medium post.
  • TUG 2016 – Day 1 – Routers and Reading
  • OpenStack Pico and Questa set to Debut in 2017 and 2018.
    Members of the OpenStack Foundation have been voting on upcoming release names and the results are now in.
  • Partnerships Ensure That OpenStack's Future is Running Containers on Kubernetes
  • Open source & cloud computing
    Today’s interview is with David Egts, chief technologist, North America Public Sector at Red Hat. Red Hat has been around for twenty-five years and has hit over two billion on annual revenue. Topics range from open source to partnering with Microsoft to the up and coming DevNationFederal. In the federal government circles, Red Had made a big splash years ago by working with NASA to have incredibly fast systems. Red Hat has expanded so much in the past decade that the conversation with Egts didn’t even get to NASA.
  • Open source project on Facebook will allow you to design apps [Ed: React is NOT "open source", Facebook maintains or reserves rights to revoke licence from competition]
  • Austria awards 'Open Data Oscars'
    Last month, the Austrian State Secretary Muna Duzdar handed out the 'Oscars of the Open Data Community'. The awards were part of the 'open4data.at challenge 2016' organised earlier this year. The annual challenge aims to bring open data and ideas together in innovative and creative solutions.
  • Open data platform on Emilia-Romagna reconstruction
    After the two earthquakes that caused multiple casualties and widespread damage in the Italian region of Emilia-Romagna in 2012, multiple programmes were launched to reconstruct the affected areas. To make these efforts more transparent, a team from the Gran Sasso Science Institute last week presented an Open Data platform that will provide all information on who is responsible, which company is doing what, and how the money is being spent. The 'Open Data Ricostruzione' initiative was presented last week at the Italian Festival of Participation. The platform will bring together all the numbers, figures and information on the reconstruction, and allow visitors to visualise, filter, track and map the available data. All information will be made available as open data, in the original database format as well as JSON.

Open Hardware

  • AArch64 desktop hardware?
    Soon there will be four years since I started working on AArch64 architecture. Lot of software things changed during that time. Lot in a hardware too. But machines availability still sucks badly. In 2012 all we had was software model. It was slow, terribly slow. Common joke was AArch64 developers standing in a queue for 10GHz x86-64 cpus. So I was generating working binaries by using cross compilation. But many distributions only do native builds. In models. Imagine Qt4 building for 3-4 days… In 2013 I got access to first server hardware. With first silicon version of CPU. Highly unstable, we could use just one core etc. GCC was crashing like hell but we managed to get stable build results from it. Qt4 was building in few hours now.
  • RISC-V on an FPGA, pt. 1
    Last year I had open source instruction set RISC-V running Linux emulated in qemu. However to really get into the architecture, and restore my very rusty FPGA skills, wouldn’t it be fun to have RISC-V working in real hardware. The world of RISC-V is pretty confusing for outsiders. There are a bunch of affiliated companies, researchers who are producing actual silicon (nothing you can buy of course), and the affiliated(?) lowRISC project which is trying to produce a fully open source chip. I’m starting with lowRISC since they have three iterations of a design that you can install on reasonably cheap FPGA development boards like the one above. (I’m going to try to install “Untether 0.2” which is the second iteration of their FPGA design.)
  • RISC-V on an FPGA, pt. 2
  • RISC-V on an FPGA, pt. 3
  • RISC-V on an FPGA, pt. 4
  • RISC-V on an FPGA, pt. 5

Security Leftovers

  • Tuesday's security updates
  • Oops: Bounty-hunter found Vine's source code in plain sight
    A bounty-hunter has gone public with a complete howler made by Vine, the six-second-video-loop app Twitter acquired in 2012. According to this post by @avicoder (Vjex at GitHub), Vine's source code was for a while available on what was supposed to be a private Docker registry. While docker.vineapp.com, hosted at Amazon, wasn't meant to be available, @avicoder found he was able to download images with a simple pull request.
  • US standards lab says SMS is no good for authentication
    America's National Institute for Standards and Technology has advised abandonment of SMS-based two-factor authentication. That's the gist of the latest draft of its Digital Authentication Guideline, here. Down in section 5.1.3.2, the document says out-of-band verification using SMS is deprecated and won't appear in future releases of NIST's guidance.

Android Leftovers