The authors of the fix can explain in details what is going on, but since the 
users will experience (great, but new) results with currently processed crash 
reports, it was suggested I should mention it to a larger audience.

https://bugzilla.mozilla.org/show_bug.cgi?id=1274345 
<https://bugzilla.mozilla.org/show_bug.cgi?id=1274345>

This is now live, which means that the new reports coming in are going to skip 
the DLLs without symbols, which means that, for example, driver crashes will 
start getting grouped together, and we will see what’s actually going on.

It also means we will start seeing the driver crashes that were processed 
before this change start dropping in frequency - probably a good idea not to 
dismiss them as “this got fixed somehow”, but instead look to see if they are 
now subsumed by a new, more awesome bug.

As an example tracked here https://bugzilla.mozilla.org/show_bug.cgi?id=1267970 
<https://bugzilla.mozilla.org/show_bug.cgi?id=1267970> - the crash went from 
411th to 19th (in 47) once all the different driver versions were aggregated 
and the DLLs without symbols were ignored.

And, yes, chances are we will see some over-grouping, but the worst case 
scenario is that we look at a crash that looks important, and turns out not to 
be, or that we only fix it partially, and then discover the lurkers.  Either 
way, much better scenario than not noticing problems because they’re scattered. 
—
- Milan



_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to