[webkit-dev] Crash reports which show extensions enabled: what to do?

[David D. Kilzer]

Apple engineers have weighed in on this topic as well:

   AcidSearch crashes WebKit
   http://bugzilla.opendarwin.org/show_bug.cgi?id=9468#c4

   WebKit crashes upon launch
   http://bugzilla.opendarwin.org/show_bug.cgi?id=9604#c1

The point is that if you're seeing a crash in Safari+WebKit and  
you're running extensions, try Safari+WebKit with all of your  
extensions disabled first.  If there is still a crash, please report  
it at http://bugzilla.opendarwin.org/ with a full crash log.

Thanks!

Dave


On Jul 7, 2006, at 7:51 AM, Joost 'AlthA' de Valk wrote:

> Hi all,
>
> there seems to be some discussion going on what to do with bugs  
> when they have crash reports with them, which show enabled  
> extensions. My view on this is VERY simple: I close each and every  
> such bug as INVALID. We have neither the time or the resources to  
> do anything else, and i'd like to keep confirming bugs as easy as  
> possible. Now I know I have no "official" right to decide on this,  
> but I hope you will all agree with me and do the same.
>
> There's been some hard work the last few days to get the  
> UNCONFIRMED list under 100 again, we have succeeded in that, and  
> have 67 unconfirmed bugs at this moment. I want to thank everybody  
> who's been doing that work, it's the first step in getting our bug  
> reporters to feel that their bugs are being looked at and taken  
> care of, which is very important IMHO.
>
> Regards,
> Joost