Special BugDay Marks Start of CrashWeek Effort to Clean Up Bugzilla Crash Bug Reports
Monday March 29th, 2004
Asa Dotzler wrote in to tell us more about CrashWeek, which starts with this Tuesday's BugDay. The aim is to clean up the crash bug reports in the Bugzilla database by reproducing and triaging the unresolved crashers. This will help the developers see which crashes are the most common and what the likely causes are. To get involved, join the latest BugDay in the #mozillazine channel on irc.mozilla.org throughout Tuesday (US time). Read the full article for more details from Asa.
#1 Help out beforehand if you can't then...
Monday March 29th, 2004 9:24 PM
Use this Bugzilla search to give crasher bugs the "crash" keyword (how I assume we're finding the bugs to triage). I assume when the bugs are being reproduced that we'll find the ones that are INVALID or WORKSFORMEs.
Be careful what you do, tho: some (many of the first few, for example) don't appear to be crashers but rather about crashing in general (or similar, unpredictable topics).
#2 Re: Help out beforehand if you can't then...
Monday March 29th, 2004 9:31 PM
Please also mark them Critical if they haven't been already. The crash keyword is for "A Critical Severity bug which causes a crash."
#3 Re: Help out beforehand if you can't then...
Monday March 29th, 2004 10:15 PM
Or just download the latest nightly build of Firefox or Mozilla 1.7b and enable talkback if the browser crashes. That will help determine which crashes are occurring most often.
#5 Re: Re: Help out beforehand if you can't then...
Tuesday March 30th, 2004 2:07 AM
Except that most of the "latest nightly builds" don't have talkback, so you can't enable it. As the article says, the Mozilla Windows 1.7 beta installer has talkback, and the current Firefox Linux GTK2+KFT nightly builds have talkback.
They're still working on restoring talkback to the other nightly builds.
#6 Re: Help out beforehand if you can't then...
Tuesday March 30th, 2004 5:54 AM
I marked ~80 or so of those bugs with the crash keyword last night...about halfway through I started only marking the confirmed ones. In retrospect I'm not sure if it's a good idea to mark *unconfirmed* crashers, but seeing as the reporter could have marked them as such himself, I think it's hard to say it was a bad idea.
This is probably a better query to use...it's only the confirmed bugs that are in this list.
As a user of FireFox 0.8 on Win2k, I haven't experienced any classical crashes.
What does happen from time to time is that the FireFox process hangs around after closing the last window and I have no way to open a new one or to restart the app.
this happens to me as well. closing Firefox leaves the process hanging. but i don't wait longer than 30 seconds before i kill it.
The crash bugs have already been biting the dust for the past week. The #1 and #2 1.7b crash bugs bit the dust last week. And yesterday a big bug in my book bit the dust: <http://bugzilla.mozilla.org/show_bug.cgi?id=238219> . Now Adobe's SVG plugin version 3 works in Mozilla. I tried last night's firefox build to see for myself. This will carry SVG until the native support comes in. Go Moz!
I would like to comment that I have never used Bugzilla (I had an account; never did more than read bugs) before today. Now, after helping out with BugDay, I was able to learn a little bit more about it.
It is very simple, Asa and Co make it very easy to join in and help out! It seems to be a very good resource, Asa said that around 200 bugs have been resolved today alone, a very good number! With #mozillazine to back me up, I was indeed able to reproduce a crash on one of the bugs, submit a Talkback report, and have the bug resolved as a duplicate! Not bad for having never used Bugzilla before!
I am just trying to urge people who use Firefox (or Mozilla, or Thunderbird...you get the idea) to see if they can help out with Bug Day, and everyday. ANY questions you have can and more than likely will be answered, and in a friendly way also! Everybody has that ONE (probably more ;) ) bug that they just can't stand, so if you want to see yours fixed then try and help with BugDay/CrashWeek...it helps the developers spend more time developing instead of trying to see if bugs still exist.