MozillaZine

Mozilla 0.9.6 Released

Tuesday November 20th, 2001

mozilla.org today made available for download binaries of the Mozilla 0.9.6 Milestone. The builds are available on the releases page, or you can get them directly from the ftp site.

New to this milestone are fixes for about 1,600 bugs including support for site icons in both the url bar and tabs (expect IE's favicons to show up in 0.9.7), displaying both Windows Bitmap (.bmp) and Windows Icon (.ico) files inline on all platforms, a new print preview implementation, Page Setup improvements on the Macintosh, Mail message 'labels' (Correction: This feature is not fully complete, only parts of the backed have landed.), and a new select and search context menu item, among others. If you are interested in more information on any of these new features, be sure to check out the release notes.

Also, mozilla.org last week released the source code on which Netscape 6.2 was based.


#170 Re: Re: Crash

by asa <asa@mozilla.org>

Friday November 23rd, 2001 4:09 PM

You are replying to this message

Talkback reports for the most part aren't analyzed individually (not until that incident is identified as a 'topcrash'). Talkback sends in a stack trace from your crash. The thousands of traces are catagorized and used to identify high occurance crash problems which get labeled as "topcrash" in bugzilla. Talkback is also used to calculate mean time between failure (the 'uptime' of the browser). Bugzilla is used to report specific problems which should be investigated as a unique issue in the product. If you're crashing and talkback catches the crash it is still important to record that as a bug in Bugzilla (include the talkback incident ID). In the next week or so we'll have a webtool available that will let you look up your talkback incident and retrieve the stack trace that is recorded. You can then query for that specific crash signature and see if it is already reported in Bugzilla. If it is reported then there's no need to report it again. In most cases a comment in the existing bug with details about how you encountered the crash is helpful. But if it isn't already reported and you can reproduce the problem then it should be reported.

--Asa