Firefox Looking To Lose The Flab - And The Flaw
Memory leaks and code exploits are a fact of life for both browser developers and their users — regardless of the specific browser in question. For the developers at Mozilla, both issues have been on their minds this week, as browser bugs of both sorts have been all over the news.
Perhaps because it's the second most-widely-used web browser in the world, not to mention being Open Source — and because expectations for the "market-leading" browser aren't particularly high — Firefox takes a good bit of flak whenever a new security hole or resource sink is discovered. The Mozilla devs — or, at least some of them — intended this week to be about memory management, and Mozilla's Co-Director of Developer Tools, Ben Galbraith, got the ball rolling on Monday with a blog post laying out plans for a new tool intended to make the process known as "garbage collection" — freeing up resources by clearing out objects no longer required in memory — a more transparent and manageable process.
According to Galbraith, the tool being proposed would make it possible to view current unrecoverable JavaScript objects, known as "the heap," along with the ability to determine why they are "noncollectable," as well as providing the opportunity to understand when collection starts and finishes, and by extension, how long it is taking. His blog post ended by encouraging members of the Mozilla community to step up and offer feedback on the proposal, something they likely were doing through Wednesday, when everyone's attention was redirected by a critical security glitch that apparently threatens every Firefox 3 user, regardless of platform.
Security researchers published code on Wednesday that reportedly would allow an attacker to load
unauthorized software on a target's computer simply by having the target view a specially-coded XML file. According to reports, Mozilla developers were blindsided by the bug and immediately raced to find a patch, a task they'd completed by this morning, adding it to next-week's Firefox 3.0.8 release. Because of the exploit, that release is now considered a "high-priority fire-drill security update" for all users.
Justin Ryan is a Contributing Editor for Linux Journal.
Trending Topics
| You Need A Budget | Feb 10, 2012 |
| The Linux powered LAN Gaming House | Feb 08, 2012 |
| Creating a vDSO: the Colonel's Other Chicken | Feb 06, 2012 |
| Your CMS Is Not Your Web Site | Feb 01, 2012 |
| Casper, the Friendly (and Persistent) Ghost | Jan 31, 2012 |
| Razor-qt 0.4 - Qt based Desktop Environment | Jan 30, 2012 |
- Linux-Based X Terminals with XDMCP
- Readers' Choice Awards 2011
- 100% disappointed with the decision to go all digital.
- Parallel Programming with NVIDIA CUDA
- You Need A Budget
- Validate an E-Mail Address with PHP, the Right Way
- Python for Android
- The Linux RAID-1, 4, 5 Code
- The Linux powered LAN Gaming House
- RSS Feeds
- Gnome3 is such a POS. No one
11 min 39 sec ago - Gnome 3 is the biggest POS
22 min 16 sec ago - I didn't knew this thing by
6 hours 26 min ago - Author's reply
9 hours 50 min ago - Link to modlys
10 hours 57 min ago - I use YNAB because of the
11 hours 9 min ago - Search
16 hours 12 min ago - Question
16 hours 35 min ago - for the record
16 hours 37 min ago - That's disappointing. Thanks
19 hours 1 min ago





Comments
It is about time. After
It is about time. After Firefox 3.0.6 came out I nearly stopped using it. I started looking into other browsers like Opera, Konqueror, Galeon, ect...
But after the release of 3.0.7 it wasn't as bad. The memory leaks in Firefox are horrendous.
bout time firefox loses the
bout time firefox loses the bloat it eats like 20% of my ram or more when its running. seems the longer its left on the worse it gets.
none
@ the previous guy, actually you didn't read it properly. firefox won the poll, but the actual usage of firefox is much less than IE and it has been mentioned in the article.
2nd? Do you guys read each other?
The article you linked to placed Firefox first, not second. Did you read it?