Comments on: 2005-11-07 Branch builds (Firefox 1.5 RC2) http://www.squarefree.com/burningedge/2005/11/07/2005-11-07-branch-builds/ Developments in nightly builds of Mozilla Firefox Sat, 05 Jul 2008 08:43:02 +0000 http://wordpress.org/?v=2.5 By: costin http://www.squarefree.com/burningedge/2005/11/07/2005-11-07-branch-builds/#comment-2995 costin Fri, 11 Nov 2005 15:03:12 +0000 http://www.squarefree.com/burningedge/2005/11/07/2005-11-07-branch-builds/#comment-2995 i just did a manually check for updates, and it updated from rc1 to rc2. it did not update automatically !!! i just did a manually check for updates, and it updated from rc1 to rc2. it did not update automatically !!!

]]> By: nestastnik http://www.squarefree.com/burningedge/2005/11/07/2005-11-07-branch-builds/#comment-2980 nestastnik Tue, 08 Nov 2005 20:15:18 +0000 http://www.squarefree.com/burningedge/2005/11/07/2005-11-07-branch-builds/#comment-2980 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. 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.

]]> By: CooLynX http://www.squarefree.com/burningedge/2005/11/07/2005-11-07-branch-builds/#comment-2975 CooLynX Tue, 08 Nov 2005 09:18:04 +0000 http://www.squarefree.com/burningedge/2005/11/07/2005-11-07-branch-builds/#comment-2975 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 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

]]> By: CooLynX http://www.squarefree.com/burningedge/2005/11/07/2005-11-07-branch-builds/#comment-2974 CooLynX Tue, 08 Nov 2005 09:02:45 +0000 http://www.squarefree.com/burningedge/2005/11/07/2005-11-07-branch-builds/#comment-2974 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. 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.

]]>