Ian Thomas wrote: >>topcrash is totally relative - you will always have topcrashers. If you >>have a single crasher, then that is a topcrasher.
barney wrote: > I'm not sure I follow you on this, at least in this case. Somebody even > commented in the bug "This is a topcrasher with recent MozillaTrunk > builds on Win2k, XP and NT" so it's very unlikely to be a "single > crasher", unless I'm misinterpretting what this means. Since I'm on > Win98, it isn't limited to any particular Win version, either. The > number of duplicate bugs also indicate it's not a couple of isolated > incidents. I'm not talking about this bug, I'm talking about in general. If you have a single bug which causes a crash (i.e. it is the only way to crash the application), then, even if it is really rare, then it will be classified as a topcrash. Therefore, milestones will always be released with topcrashers - there is no way to avoid it. Ian
