Mozilla 1.4 Release Candidate 3 Coming Early Next Week
Friday June 20th, 2003
In a weblog posting, Asa Dotzler has confirmed that there will be a third release candidate of Mozilla 1.4. RC3, which is likely to ship on Monday, will contain fixes for several bugs, including a major memory leak that mainly affects Windows 95/98/ME users. There will also be several Mac OS X improvements. New 1.4 branch builds — which will very likely become the final RC3 binaries — are now available for Windows, Linux and Mac OS X.
I think it's great that Mozilla.org is willing to go the extra mile (or RC) to make sure 1.4 is as good as it can be. Personally I can hardly wait for 1.4 because the next Netscape is waiting on it, but I can wait for quality. Open source rules!
The lack of Java support on MacOs X may be a big blocker for Netscape to release a new version on that platform (bug <http://bugzilla.mozilla.org/show_bug.cgi?id=97613>). Further, I consider MacOs X version of Mozilla very late compared to its windows counterpart, especially in term of performance (Bugs <http://bugzilla.mozilla.org/show_bug.cgi?id=189649> and <http://bugzilla.mozilla.org/show_bug.cgi?id=188208> - they may be dupplicates)
#17 Re: No Java at all on MacOs X
Monday June 23rd, 2003 11:42 AM
"The lack of Java support on MacOs X may be a big blocker for Netscape...."
Mozilla for Mac OS X does not "lack" Java. Mozilla uses the Apple Java plug-in that ships with the OS. It is lacking in LiveConnect but not basic Java.
I use Windows ME. Since 1.2, I've been having problems with crashes on heavy flash sites (multitasking is severely restricted--even running word can cause stability issues in combination with Mozilla.)
Hopefully, this fixes it.
Deinstalling Mozilla Deleting the Directory Mozilla* in C:Programm Files Installing Mozilla
(If you install Mozilla you shouldn't install it in the Directory of an other Version of Mozilla.
Ever since 1.4 I've had to close Mozilla dn start it again since my resources would disappear. I'm using win 98 so i hope this is the leak they fixed
i'm not sure which resources you mean. it's possible that you're running out of the GDI resources. the a bug <http://bugzilla.mozilla.org/show_bug.cgi?id=204374> has some problem workarounds.
#3 Please take as much time as needed!
by Wolf <WinterWolf@myway.com>
Saturday June 21st, 2003 3:04 PM
I hope this release will go through a lot more intense testing than even the big 1.0 release has undergone. Mozilla 1.4 will be the basis of the next Netscape, the new componetized Mozilla 1.5 and even the basis of may important Mozilla based companies like OEOne.
Please developers take as much time as you need, I will consider it early if its even released in August.
#4 Re: Please take as much time as needed!
Saturday June 21st, 2003 3:25 PM
Your point is generally a good one, but one thing - this Mozilla 1.4 release won't be the basis for the componentised Mozilla 1.5. Mozilla 1.4 split off from the trunk back on 24th May. All the fixes that go into 1.4 are going into the pre-1.5alpha builds as well, but the state of the 1.4 code does not directly affect Firebird and the future stuff.
Unless something serious crops up with RC3, I don't imagine it will be too much longer - lesser bugs will get pushed out to make a 1.4.1.
It is kind of amazing that an RC of a Mozilla release has generated so little interest. It points to Mozilla's stability, Firebird's popularity and the fact that Mozilla has just every feature ever conceived for a browser.
The "likely to become 1.4rc3 build" still have memory leaks on Win9x or whatever is the reason for chrome update corrupts after a little "heavy surfing". So if it really becomes rc3 I wouldn't mind a rc4 too before its final..
These leaks occur in all OSes; its just that Win9x doesn't manage its memory very well so the problem is exacerbated there. I agree that it would be nice to get these leaks fixed before 1.4 final, but I seriously doubt that will happen...especially when many of these leaks have existed since 1.0 and earlier.
#9 a crash that should be fixed before 1.4 final !
Monday June 23rd, 2003 5:50 AM
i can't believe 1.4 could be released with this bug in it :
this is a crasher, and a highly visible one. no reaction. very disappointing...
#11 Re: a crash that should be fixed before 1.4 final
Monday June 23rd, 2003 8:21 AM
Zero votes. Only two Cc addresses. Reporter using a 6-month-old build. Difficult to reproduce (WFM, for instance).
It may be a crasher, but it hardly meets the criteria for "highly visible". And with sspitzer on vacation, I see no reason to hold 1.4 up for this bug.
#13 Re: Re: a crash that should be fixed before 1.4 fi
Monday June 23rd, 2003 9:21 AM
"WFM"... really ? did you check "Forward as : Inline" in the prefs ? are you on linux ?
and i mean "highly visible" because you juste have to select 2 messages in your inbox, and hit that big "forward" button in the toolbar to get a crash... (not an obscure function in a right click context menu, you see ?)
#14 Re: Re: Re: a crash that should be fixed before 1.
Monday June 23rd, 2003 10:40 AM
Hmm, I've never forwarded more than one message... I've simply never needed it. But such bugs shouldn't exist for sure.
I'm using RedHat8 + Mozilla 1.4 RC2. I've tried your instruction. It "looks like" it crashed, but after "some time", two email composer appears (the two forwards, each in each composer).
It's slow, but work.
#21 Re: a crash that should be fixed before 1.4 final
by croddy <firstname.lastname@example.org>
Tuesday June 24th, 2003 3:12 AM
try it with a clean profile. it works fine for me in rc2, unless I use an old dirty profile.
In the buglist above there are a couple of important OS X bugs that are missing.
The most important one is 203343 (disappearing bookmarks.html). I just tested the 1.4 RC_3 from the link above, and it still has the problem on NFS home directories. 203343 contains a description that is consistant and reproducible. The bookmarks.html file is not written/maintained across launches of Mozilla. Dataloss like this should be sufficient to block 1.4, but I haven't seen any activity on this bug (probably because there are too many separate reports. This meta-bug started to consolidate them all, but there is no recent activity on it. Several later reports (many by the same reporter) were marked as 'duplicate'. However, they were marked as duplicate of OTHER issues and not linked back to the meta-bug.
The other one that is of major concern to me is 166369 (Download fails at 100% with 'sorry about that' message). This seems to be a regression to a bug that existed in 1.2.1 but which has been fixed for a while. Again, it's only reproducible for me on NFS, not HFS+ filesystems.
I'm willing to test patches (as Conrad well knows - Thanks, Conrad ;-> ). This is a huge problem for me and might drive me to use <whisper>s-a-f-a-r-i</whisper> rather than explain to my users how great Mozilla is, and why we use a browser that can't download or bookmark ;-(.
Not that I'm ungrateful - 1.4 is faster, more stable, renders better and is all-around more polished than the 1.3 and 1.2 series. I truely appreciate all the hard work, I'm just afraid that these issues may be slipping unintentionally through a crack.
#18 Mailnews plain text compose still broken
by Ascaris <email@example.com>
Monday June 23rd, 2003 3:32 PM
I was hoping this would be fixed soon... it was a problem in 1.0 and it has only gotten worse, not better. Every email I send (using the plaintext editor) that has a line ending with a period (in the rightmost column) still indents the next line twice when it wraps (bug 91608). And recently, Mozilla has started adding a CR/LF after cited text. And sometimes while deleting selected text with the delete key, the cursor fails to move upward as the text below does. The last two happen with the HTML editor as well as the plaintext. The result is that a high percentage of mail sent with Mozilla looks like hamburger when it gets to where it is going. This is a high-visibility bug... not a crasher, but it really makes Mozilla look crappy.
by sgifford <firstname.lastname@example.org>
Tuesday June 24th, 2003 2:52 AM
I've had 1.4rc2 crash on me twice in the last week (TB21305940Q and TB21269061M); before this, I hadn't had Mozilla crash in months. Is the 1.4 series a bit crashy for anybody else, or is it just me?
pheraps you are visiting sites with some Flash animations? It's a known bug, already fixed in nightly release (and in 1.4rc3)