BTW, you can tell if a crash report was triggered by this new feature by looking for the presence of the "submitted from infobar" field.
On Sat, Jun 4, 2016 at 2:37 AM, Ehsan Akhgari <[email protected]> wrote: > FYI > > ---------- Forwarded message ---------- > From: Lawrence Mandel <[email protected]> > Date: Thu, Jun 2, 2016 at 6:10 PM > Subject: [desktop] Heads up: Tons of IPCError-browser | ShutDownKill > reports incoming > To: release-drivers <[email protected]> > > > ---------- Forwarded message ---------- > > From: Andrew McCreight <[email protected]> > Date: Thu, Jun 2, 2016 at 5:49 PM > Subject: Heads up: Tons of IPCError-browser | ShutDownKill reports incoming > To: "projectuptime-." <[email protected]> > > > Bug 1269998 landed early today or yesterday, and prompts users to submit > all old unsubmitted crash reports. One consequence of this is that crashes > that happen because shutdown takes too long are now going to be submitted. > Before, because they were happening during shutdown, there was no crash > report UI shown to the users, so they were not being submitted. > > This is a huge % of all crashes. For instance, for the 6/1 hour 3 builds, > they are currently showing up as 30% of all crashes. It also isn't clear > they are really crashes we should care about, as they are really more of a > sign of slow shutdown. > > I think this is going to affect all builds on all channels, so brace > yourselves. > > Andrew > > _______________________________________________ > release-drivers mailing list > [email protected] > https://mail.mozilla.org/listinfo/release-drivers > _______________________________________________ > dev-platform mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
