Sunday, March 1st 2009

Mozilla Firefox 3.1 Delayed, New Beta Release in the Works

Last week Mozilla developers confirmed that they will add another beta to the Firefox 3.1 development schedule, meaning that Mozilla users will have to wait a bit longer for the new final release. The reason hiding behind this delay is the recently found critical bug in the browser's TraceMonkey java script engine."We're going to wrap up Beta 3 in the next week regardless of 'upvar' status," said Mike Shaver, Mozilla's vice president of engineering. "A fourth beta will follow approximately six weeks after, as a vehicle for more testing of TraceMonkey, video, Places and other eagerly-awaited improvements, as well as feedback from Beta 3," he added.
Originally Mozilla Firefox 3.1 was slated to launch in late 2008, but the browser's progress has been much slower than planned. With this last update on the development schedule, the browser will possibly ship in the second quarter of this year or even later.Source: PCWorld
Add your own comment

14 Comments on Mozilla Firefox 3.1 Delayed, New Beta Release in the Works

#1
CrAsHnBuRnXp
What's new that 3.1 is supposed to bring anyway?
Posted on Reply
#2
AlCabone
by: CrAsHnBuRnXp
What's new that 3.1 is supposed to bring anyway?
pr0n button.
Posted on Reply
#3
eidairaman1
i wonder if they will get a clue and fix the memory hole it has.
Posted on Reply
#4
thebeephaha
by: eidairaman1
i wonder if they will get a clue and fix the memory hole it has.
RAM is cheap, get over it.

/rant
Posted on Reply
#5
eidairaman1
listen dude i didn't encroach a fight so don't try to start one, I'm getting at users with Mid Range systems etc, Also even if you have plentiful of ram, doesn't mean they shouldn't fix the Memory Leak, because eventually it will get to the point where even those with plentiful ram do run out, Memory Leaks are very problematic for any machine, just like how unclean software can cause the fastest machine to slow to a machine from 4 years ago.
Posted on Reply
#6
to6ko91
critical bug in the browser's TraceMonkey java script
Thats been there for ages and they just fix it now :eek:
when you open a new java tab with scroll click
Posted on Reply
#7
eidairaman1
do you think this flaw also pertains to the memory leak FF 3 and later versions of 2 have?
Posted on Reply
#8
CrAsHnBuRnXp
by: eidairaman1
listen dude i didn't encroach a fight so don't try to start one, I'm getting at users with Mid Range systems etc, Also even if you have plentiful of ram, doesn't mean they shouldn't fix the Memory Leak, because eventually it will get to the point where even those with plentiful ram do run out, Memory Leaks are very problematic for any machine, just like how unclean software can cause the fastest machine to slow to a machine from 4 years ago.
I agree with you. But i thought that memory leak was fixed when they released FF3?

----------------
Now playing: Finch - Ink
via FoxyTunes
Posted on Reply
#9
Solaris17
Creator Solaris Utility DVD
by: CrAsHnBuRnXp
I agree with you. But i thought that memory leak was fixed when they released FF3?

----------------
Now playing: Finch - Ink
via FoxyTunes
that was my understanding. regardless of fixed or not...uses less ram doing the same stuff IE does. tested it myself.
Posted on Reply
#10
eidairaman1
by: CrAsHnBuRnXp
I agree with you. But i thought that memory leak was fixed when they released FF3?

----------------
Now playing: Finch - Ink
via FoxyTunes
the problem mainly is Tabs, if you Open one and then close it, Firefox doesn't release the used ram, and then some.
Posted on Reply
#11
NamesDontMatter
by: CrAsHnBuRnXp
I agree with you. But i thought that memory leak was fixed when they released FF3?

----------------
Now playing: Finch - Ink
via FoxyTunes
Firefox has terrible memory leak errors, Its been horrible for me lately, I actually can't stand it anymore. I only use firefox when i have to, for certain firefox plugins I use. Yesterday I had it use up 500mb of RAM and bring my entire rig to a screeching halt, the day before that it got up to 2.5 GB, too bad firefox won't do what google chrome did where each tab is its own processor. Its kind of one of those DUH, why wouldnt we do that things?
Posted on Reply
#12
eidairaman1
that is just like having IE open in multiple instances, nothing changed, but one thing, the Memory needs to be released or actually have a maximum cap no matter how many tabs are open.
Posted on Reply
#13
spearman914
by: eidairaman1
the problem mainly is Tabs, if you Open one and then close it, Firefox doesn't release the used ram, and then some.
If u get deeper in the settings, type "about :config" in the address bar. Find out how to fix it urself. :o
Posted on Reply
#14
mdm-adph
Firefox has no memory leaks -- extensions have tons.

I run Firefox on tons of computers in "vanilla" mode (without any extensions) and it always runs with less RAM than any other browser, save Opera.
Posted on Reply
Add your own comment