2005-11-07 Branch builds (Firefox 1.5 RC2)
Fixes:
- Fixed: A few potential security holes.
No known major regressions.
Gecko 1.8 branch checkins between 2005-11-05 06:00 and 2005-11-07 12:00
Fixes:
No known major regressions.
Gecko 1.8 branch checkins between 2005-11-05 06:00 and 2005-11-07 12:00
November 8th, 2005 at 1:02 am
Is it possible to avoid history.dat reset on Firefox upgrade? And what about update service – is it working only on trunk or it “should” be working on branch as well? Starting from some beta or RC1 I updated FF manually because there were no updates via update service.
November 8th, 2005 at 1:18 am
Looks like I used some test version build that caused me problems with history. Not sure but could be this one http://weblogs.mozillazine.org/ben/archives/009210.html
November 8th, 2005 at 12:15 pm
maybe it was mentioned or buglisted…but
whole FF 1.5 branch(1.1+ etc) has some threading bugs or synchro problems or something…
when FF is loading page in backround, not only CPU goes relatively high but main thread(or tab) is frozen for some miliseconds, so if you beggin interacting with main tab window. or save it, or scrolling(try via 3rd button!) or anything it is really fro-fro-fro-zen-now moves-ze-zen-fro-zen.
It gets a little worse oppening multiple tabs, but the main problem here is frozening behaviour is very apparent with just one tab in backround loading…
I have a relatively high machine with relatively enought memmory, so i would expect much worser scenarios on low-end machines, I even heard FF1.07 hadn’t had such problem, sadly I can’t confirm, it has been a very long time I have been on stable branch.
this behaviour doesn’t seem to change in final, but I would like to know what is casing it.
November 11th, 2005 at 7:03 am
i just did a manually check for updates, and it updated from rc1 to rc2. it did not update automatically !!!