Disabled the auto-crash features for Mac.
Kind Regards,

Anthony Laforge
Technical Program Manager
Mountain View, CA


On Mon, Oct 12, 2009 at 9:44 AM, Mike Pinkerton <[email protected]>wrote:

> I just had crashbot add a totally unrelated stack trace to a bug. I
> emailed anthony about it, we'll see.
>
> Something is clearly wrong.
>
> On Mon, Oct 12, 2009 at 12:41 PM, Scott Hess <[email protected]> wrote:
> >
> > Does this relate to receiving crashbot emails adding "Crash" labels on
> > closed-out bugs where the backtrace doesn't apparently have any
> > relevance to the original backtraces involved with the bug?  I've
> > gotten a couple of these in the past week.
> >
> > -scott
> >
> > [Unfortunately, I don't remember the earlier one, the latter is
> > http://crbug.com/13113 ]
> >
> > On Tue, Oct 6, 2009 at 9:58 PM, John Abd-El-Malek <[email protected]>
> wrote:
> >>
> >>
> >> On Tue, Oct 6, 2009 at 8:57 PM, Anthony LaForge <[email protected]>
> >> wrote:
> >>>
> >>> The short of it:
> >>>
> >>> People manually associated bugs in http:crash
> >>> My tool creates its own map of signatures and for whatever reason that
> bug
> >>> is on all of them
> >>> It goes through each aggregate signature and updates the status of the
> bug
> >>> (which is a flash crasher)
> >>> It's made much worse because we are dealing w/ crashes that don't have
> >>> symbols and cannot be aggregated...
> >>>
> >>> What went wrong:
> >>>
> >>> The limiting function (seeing if crash-VERSION) was applied does not
> >>> happen for priority updates.  This was actually intentional since we
> start
> >>> looking at crash data early on.  However this should no longer be
> needed
> >>> since we wait for enough data that priority should no longer be
> shifting.
> >>>
> >>> What can be done about it?
> >>>
> >>> I will put a limiter on setting the priority
> >>
> >> Thanks.
> >>
> >>>
> >>> Kind Regards,
> >>>
> >>> Anthony Laforge
> >>> Technical Program Manager
> >>> Mountain View, CA
> >>>
> >>>
> >>> On Tue, Oct 6, 2009 at 8:46 PM, Patrick Johnson <[email protected]>
> >>> wrote:
> >>>>
> >>>> John's question is about why it's generating so many issue updates.
> >>>>
> >>>> Patrick
> >>>>
> >>>>
> >>>> On Tue, Oct 6, 2009 at 8:41 PM, Anthony LaForge <[email protected]
> >
> >>>> wrote:
> >>>> > It's the role account that manages crashes and crash related bugs.
> >>>> > Kind Regards,
> >>>> >
> >>>> > Anthony Laforge
> >>>> > Technical Program Manager
> >>>> > Mountain View, CA
> >>>> >
> >>>> >
> >>>> > On Tue, Oct 6, 2009 at 7:26 PM, Patrick Johnson <
> [email protected]>
> >>>> > wrote:
> >>>> >>
> >>>> >> [+laforge]
> >>>> >>
> >>>> >> On Tue, Oct 6, 2009 at 6:51 PM, John Abd-El-Malek <
> [email protected]>
> >>>> >> wrote:
> >>>> >> > I got 21 emails in the last day
> >>>> >> > for http://code.google.com/p/chromium/issues/detail?id=20915
> >>>> >> > >> >
> >>>> >> >
> >>>> >
> >>>> >
> >>>
> >>
> >>
> >> >
> >>
> >
> > > >
> >
>
>
>
> --
> Mike Pinkerton
> Mac Weenie
> [email protected]
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to