2005-12-24 Firefox 1.5.0.x builds
Firefox 1.5.0.x will be released from this branch, MOZILLA_1_8_0_BRANCH. Most of the changes on this branch will address security holes and reliability issues (crashes, hangs, and memory leaks), but major regressions and site-compatibility bugs will be considered too.
If you use Firefox 1.5, please switch to one of these builds if you're affected by one of the bugs below or if you want to help test that the fixes didn't break anything.
Fixes:
- Fixed: 305970 - [Linux] Certain UI operations (opening dialogs, drag and drop) cause refresh, prolonged hang (with new versions of GTK).
- Fixed: 311480 - "Firefox could not install this item because of a failure in Chrome Registration. Please contact the author about this problem." (This bug is responsible for the release note: "If Firefox 1.5 is installed on a multi-user system in a location which is not writable by users, Firefox must be run once by a privileged user. If this is not desirable, an empty file must be created in the following directory: <install-directory>/extensions/talkback@mozilla.org/chrome.manifest")
- Fixed: 316775 - Leak when selecting.
- Fixed: 317478 - Leaks due to global scope polluter being removed from not enough (?) prototype chains. (Large leak on any page that relies on seeing element IDs in the global scope.)
- Fixed: 318922 - E4X: invalid syntax to use a memory variable crashes Firefox.
- Fixed: 319391 - "eval('...') = ..." gives "invalid assignment lefthand side" as a compile-time error instead of as a runtime error (regression).
MOZILLA_1_8_0_BRANCH checkins between branch creation and 2005-12-24 06:00
Windows nightly,
Windows hourly
(discussion)
No Linux nightly
December 24th, 2005 at 6:38 pm
I’m still thinking about how I should title posts for each of the two active branches. “2005-12-24 1.8.0.x branch builds” is ugly because the date runs into the branch name. “2005-12-24 Fx150x builds” is even more ugly. “2005-12-24 security-branch builds” makes it sound like only security fixes are considered for fixing on the branch. Tell me if you have other ideas.
December 24th, 2005 at 11:02 pm
Windows hourly doesn’t point to the 1.5 branch, plus the Windows nightly executable is broken.
December 25th, 2005 at 12:24 am
Hourly links fixed, I think.
December 25th, 2005 at 12:26 am
The Windows installer does look broken at 52K. Does the Windows zip build work? Do you know if there’s a bug filed?
December 25th, 2005 at 1:55 am
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8) Gecko/20051224 Firefox/1.5
properties of Firefox.exe: 1.8: 2005122404
The zip build seems to be ok, gmail is working
herman
December 25th, 2005 at 4:43 am
does anyone know if all of these fixes will be applied to the MOZILLA_1_8_BRANCH too?
December 25th, 2005 at 6:31 am
largie: All the bugs listed above has the fixed1.8.1 keyword as well as fixed1.8.0.1. So that would be a yes.
December 25th, 2005 at 5:27 pm
why do still some pages still load forever? Using Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8) Gecko/20051225 Firefox/1.5 ID:2005122503
December 26th, 2005 at 8:04 am
Same thing with Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.8) Gecko/20051226 Firefox/1.5 ID:2005122603.
December 26th, 2005 at 9:13 am
Stable Branch, Development Branch, Trunk.
MOZILLA_1_8_0_BRANCH, MOZILLA_1_8_BRANCH, and TRUNK respectively.
December 27th, 2005 at 9:54 am
ok bugs bugs bugs, some sites broken that wasn’t before, like:
http://www.dotnetbips.com/articles/displayarticle.aspx?id=487
and my favorite http://www.asp.net FORUM is funny again. E.G. try this:
load forum in 3 tabs and some windows, and let it be…after 5min or 10min or sometimes 1 min ?!? (depending on something) the whole windows of FF will go BLANK WHITE, you now have 2 options:
1.bad -> to do it worse, you will try to make BIG RESPONSES, clicking like mad, crying and pressing CTRL+ALT+DEL till OS Windows won’t tell you *Firefox is not responding* and you will try to shoot it off.
2. better -> wait a bit, in 80% of cases it will go O.K. after 3 minutes!!! Or you can close one window via Right Click button on taskbar and wait till other get responses.
WOW, that’s great. And many sites reported before that make crash/memmory do it again. And I like the most that we have 1.8.0 branch when we had 1.8! Could someone explain me WHY I WAS TRYING every night 1.8, when I thought it does change, when they call it stable ?? (and make builds every night like crazy?:?!?_) and changes are only in 1.8.0?
this development was sick at begining (release plans exceding 1 year!!!!!!), but now it sicker then ever before…with FF 2.0 being completely something else what it meant to be, and FF3.0 comming out when the world will be hit by asteroid (don’t be foolish and believe moz developers plans, FF30 won’t be out until 2008!) I am somewhat sad.
btw, Marry Christmas and Happy New Year…it will be, we’ll get IE7 afterall =)
December 27th, 2005 at 4:25 pm
The plan they have for 1.5.0.1 looks very promising and I hope they’ll be able to improve the browser because at the moment the huge memory usage and the slowness after having browsed for a while is becoming really frustrating.
Don’t get me wrong I really like Firefox but I’m not a blind fanboy though I can’t see me using another browser at the moment.
For me personlly IE is an too big of a security risk and isn’t as configurable/extentionable as Firefox + crappy rendering engine, while Opera is nice it has way too much bloat in the menu’s for me and again it lacks the configurability. The next best thing would be K-Meleon but sadly there aren’t any active core devs and it’s still missing some features (like drag & drop links) to be bable to replace Firefox for me.
nestastnik: Yes I have seen that blank window problem too but rarely and it clears here out too after a minute or so (depending on how much processing power is free).
December 27th, 2005 at 4:37 pm
As of branch respin on December 27 2005 14:39 to 15:54 Windows installer build bug was corrected.
December 29th, 2005 at 5:02 pm
nestastnik: regarding your everlasting memoryproblem check out: http://forums.amd.com/lofiversion/index.php/t43224.html
FIREFOX MEMORY USAGE FIX
This tweak forces Firefox to use less memory.
1. Type “about:config” in the address field.
2: Right-click and create a new Integer
3: Name the new integer “browser.cache.memory.capacity”
4: Set the value to 16384 (this is 16MB)
5: Restart Firefox.
Have no time to test it…..hitting zzzzzzz now……..best of luck.zz…….zzzzzzzzzzzz……
December 31st, 2005 at 5:58 am
That won’t help much sadly enough peakshysteria, mine is set at 307200 (300MB) and the browser still uses way more after some surfing.
December 31st, 2005 at 6:31 am
Err. Precisely? The point is to throttle memory usage.
January 1st, 2006 at 8:40 am
You can’t really throttle memory usage since Firefox leaks like crazy.
Currently I have 5 tech websites opened in tabs, memory usage is:
– Mem Usage: 561.996K
– VM Mem Size: 565.765K
This looks way more then the 300MB I’ve set in my user.js ;)
Besides that Firefox is starting to crawl again, using way more cpu power to load pages in new tabs then just after a fresh start.
Have a look: http://img405.imageshack.us/img405/9190/firefoxmemoryusage0101200617h3.png
January 4th, 2006 at 8:33 am
FF 1.5.0.1 is still crashes and this is ths ID # TB13568424Z I get in talkback.
January 8th, 2006 at 4:47 pm
I’ve been getting random crashes under OS X since 1.5 came out and they continue. The latest 1.5.0.1 is no better. Plus, the memory usage is insane. My little G3 iBook chokes like crazy after a while.
January 11th, 2006 at 5:15 pm
Would be great to focus on memory usage enhancements.