--Asa
John
_______________________________________________
Mozilla-seamonkey mailing list
Mozilla-...@mozilla.org
http://mail.mozilla.org/listinfo/mozilla-seamonkey
I've tried the latest 1.6 nightly builds under XP. They are nice in
general, but they don't seem as stable as the 1.5 release. I get ~1-3
crashes per day of heavy usage of the browser and mail/news. Sadly, they
are all non-repeatable crashes most likely due to thread safety, memory
overwrites, network timing, multiple tabs opening, etc. I think one
problem is that without a talkback server, it is harder for Mozilla.org to
determine how stable the nightly builds are. I realize the Talkback
servers are in the works, but it might be worth trying to release a few 1.6
builds with talkback enabled and ask the testers to bang on it hard to work
out any remaining easy topcrashers (even if it causes a release delay). I
know the 1.6 release cycle can't stretch forever, but it is something to
consider.
Erik
I just want to 'second' that. I think Erik has a very good idea here.
Everyone wants 1.6 to be at least as stable (or more so) as previous
milestones. Talkback would be a very valuable tool to make this happen.
--
joe reasor
"We're losing the war on AIDS. And drugs. And poverty. And terror. But
we sure took it to those Nazis. Man, those were the days."
Asa,
I am using Mozilla nightly 2003121505 with MacOS X 10.3.2 (bug also
seen on 10.3.1). Too often while surfing some events in the browser
become unresponsive such as clicking on a url or posting form data.
The only way to restore the events is to relaunch Mozilla (sometimes
requiring a force-quit). I am bringing this bug to your attention
because I am not sure if this is a bug which should be fixed before
1.6 final.
I filled a bug 228801
http://bugzilla.mozilla.org/show_bug.cgi?id=228801 and it is still
listed as unconfirmed.