130
edits
NightlyCrashTriage/2017Q4: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Amccreight (talk | contribs) (11-15 Nightly) |
No edit summary |
||
| Line 1: | Line 1: | ||
== 2007-11-19 - jseward == | |||
Nov 16 Nightly | |||
* Filed {{bug|1418763}} Crash in IOAccelerator@0x28ba | |||
* Filed {{bug|1418766}} Crash in java.lang.OutOfMemoryError: at com.google.android.exoplayer2.upstream.DefaultAllocator.allocate(DefaultAllocator.java) | |||
I looked at various single-instance bugs. I feel that the strategy of | |||
sorting signatures by the number of crashes is increasingly unrepresentative | |||
of what's important, and that it would be better to sort by the number of | |||
different installation times involved. This would move SIBs to the bottom | |||
of the list and make it easier to concentrate on crashes that impact more | |||
than one user. | |||
== 2017-11-17 - mccr8 == | == 2017-11-17 - mccr8 == | ||
11-15 Nightly | 11-15 Nightly | ||