Assuming `HeaderMismatch` in the signature is always an indicator of the issue, it looks like it only affects Fenix crash reports: ``` $ supersearchfacet --start-date='2022-02-23' --end-date='2022-03-02' --period=daily --_facets=product --signature='HeaderMismatch' --format=markdown ``` date | -- | Fenix | Firefox | Focus ---- | -- | ----- | ------- | ----- 2022-02-23 00:00:00 | 0 | 0 | 0 | 0 2022-02-24 00:00:00 | 0 | 3 | 0 | 0 2022-02-25 00:00:00 | 0 | 1 | 0 | 0 2022-02-26 00:00:00 | 0 | 1 | 0 | 0 2022-02-27 00:00:00 | 0 | 1 | 0 | 0 2022-02-28 00:00:00 | 0 | 9 | 1 | 0 2022-03-01 00:00:00 | 0 | 5 | 0 | 1 2022-03-02 00:00:00 | 0 | 1800 | 0 | 57 If we look at product that have `EMPTY` in the signature (denoting some problem with the minidump), we see this: ``` $ supersearchfacet --start-date='2022-02-23' --end-date='2022-03-02' --period=daily --_facets=product --signature='EMPTY' --format=markdown ``` date | -- | Fenix | Firefox | Focus | ReferenceBrowser ---- | -- | ----- | ------- | ----- | ---------------- 2022-02-23 00:00:00 | 0 | 7241 | 772 | 395 | 0 2022-02-24 00:00:00 | 0 | 6323 | 832 | 307 | 0 2022-02-25 00:00:00 | 0 | 5804 | 661 | 299 | 2 2022-02-26 00:00:00 | 0 | 6648 | 748 | 342 | 0 2022-02-27 00:00:00 | 0 | 6349 | 487 | 342 | 0 2022-02-28 00:00:00 | 0 | 6101 | 870 | 225 | 0 2022-03-01 00:00:00 | 0 | 6344 | 838 | 237 | 0 2022-03-02 00:00:00 | 0 | 5700 | 1019 | 245 | 0 If we look at EMPTY signatures for Fenix over the last 7 days, we see this: ``` supersearchfacet --start-date='2022-02-23' --end-date='2022-03-02' --_facets=signature --signature='EMPTY' --product=Fenix --period=daily ``` date | -- | EMPTY: no crashing thread identified | EMPTY: no crashing thread identified; EmptyMinidump | EMPTY: no crashing thread identified; HeaderMismatch | EMPTY: no crashing thread identified; MissingSystemInfo | EMPTY: no crashing thread identified; MissingThreadList | EMPTY: no crashing thread identified; unknown error | OOM large EMPTY: no crashing thread identified; EmptyMinidump ---- | -- | ------------------------------------ | --------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------- | ------------------------------------------------------- | --------------------------------------------------- | ----------------------------------------------------------------- 2022-02-23 00:00:00 | 0 | 1184 | 5989 | 0 | 3 | 27 | 38 | 0 2022-02-24 00:00:00 | 0 | 965 | 5259 | 3 | 10 | 26 | 60 | 0 2022-02-25 00:00:00 | 0 | 943 | 4781 | 1 | 4 | 36 | 38 | 1 2022-02-26 00:00:00 | 0 | 841 | 5719 | 1 | 1 | 41 | 45 | 0 2022-02-27 00:00:00 | 0 | 832 | 5429 | 1 | 3 | 38 | 46 | 0 2022-02-28 00:00:00 | 0 | 816 | 5190 | 9 | 5 | 47 | 34 | 0 2022-03-01 00:00:00 | 0 | 955 | 5308 | 5 | 9 | 31 | 35 | 1 2022-03-02 00:00:00 | 0 | 785 | 3060 | 1800 | 2 | 24 | 29 | 0 Ergo, while I think there is a bug in the extract_payload code or the Fenix crash reports in question are malformed, I think the crash reports it affects have junk minidumps and rust-minidump would have kicked up a "EmptyMinidump" before and now kicks up a "HeaderMismatch".
Bug 1757854 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Assuming `HeaderMismatch` in the signature is always an indicator of the issue, it looks like it only affects Fenix crash reports: ``` $ supersearchfacet --start-date='2022-02-23' --end-date='2022-03-02' --period=daily --_facets=product --signature='HeaderMismatch' --format=markdown ``` date | -- | Fenix | Firefox | Focus ---- | -- | ----- | ------- | ----- 2022-02-23 00:00:00 | 0 | 0 | 0 | 0 2022-02-24 00:00:00 | 0 | 3 | 0 | 0 2022-02-25 00:00:00 | 0 | 1 | 0 | 0 2022-02-26 00:00:00 | 0 | 1 | 0 | 0 2022-02-27 00:00:00 | 0 | 1 | 0 | 0 2022-02-28 00:00:00 | 0 | 9 | 1 | 0 2022-03-01 00:00:00 | 0 | 5 | 0 | 1 2022-03-02 00:00:00 | 0 | 1800 | 0 | 57 If we look at product that have `EMPTY` in the signature (denoting some problem with the minidump), we see this: ``` $ supersearchfacet --start-date='2022-02-23' --end-date='2022-03-02' --period=daily --_facets=product --signature='EMPTY' --format=markdown ``` date | -- | Fenix | Firefox | Focus | ReferenceBrowser ---- | -- | ----- | ------- | ----- | ---------------- 2022-02-23 00:00:00 | 0 | 7241 | 772 | 395 | 0 2022-02-24 00:00:00 | 0 | 6323 | 832 | 307 | 0 2022-02-25 00:00:00 | 0 | 5804 | 661 | 299 | 2 2022-02-26 00:00:00 | 0 | 6648 | 748 | 342 | 0 2022-02-27 00:00:00 | 0 | 6349 | 487 | 342 | 0 2022-02-28 00:00:00 | 0 | 6101 | 870 | 225 | 0 2022-03-01 00:00:00 | 0 | 6344 | 838 | 237 | 0 2022-03-02 00:00:00 | 0 | 5700 | 1019 | 245 | 0 If we look at EMPTY signatures for Fenix over the last 7 days, we see this: ``` $ supersearchfacet --start-date='2022-02-23' --end-date='2022-03-02' --_facets=signature --signature='EMPTY' --product=Fenix --period=daily ``` date | -- | EMPTY: no crashing thread identified | EMPTY: no crashing thread identified; EmptyMinidump | EMPTY: no crashing thread identified; HeaderMismatch | EMPTY: no crashing thread identified; MissingSystemInfo | EMPTY: no crashing thread identified; MissingThreadList | EMPTY: no crashing thread identified; unknown error | OOM large EMPTY: no crashing thread identified; EmptyMinidump ---- | -- | ------------------------------------ | --------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------- | ------------------------------------------------------- | --------------------------------------------------- | ----------------------------------------------------------------- 2022-02-23 00:00:00 | 0 | 1184 | 5989 | 0 | 3 | 27 | 38 | 0 2022-02-24 00:00:00 | 0 | 965 | 5259 | 3 | 10 | 26 | 60 | 0 2022-02-25 00:00:00 | 0 | 943 | 4781 | 1 | 4 | 36 | 38 | 1 2022-02-26 00:00:00 | 0 | 841 | 5719 | 1 | 1 | 41 | 45 | 0 2022-02-27 00:00:00 | 0 | 832 | 5429 | 1 | 3 | 38 | 46 | 0 2022-02-28 00:00:00 | 0 | 816 | 5190 | 9 | 5 | 47 | 34 | 0 2022-03-01 00:00:00 | 0 | 955 | 5308 | 5 | 9 | 31 | 35 | 1 2022-03-02 00:00:00 | 0 | 785 | 3060 | 1800 | 2 | 24 | 29 | 0 Ergo, while I think there is a bug in the extract_payload code or the Fenix crash reports in question are malformed, I think the crash reports it affects have junk minidumps and rust-minidump would have kicked up a "EmptyMinidump" before and now kicks up a "HeaderMismatch".
Assuming `HeaderMismatch` in the signature is always an indicator of the issue, it looks like it only affects Fenix crash reports:
```
$ supersearchfacet --start-date='2022-02-23' --end-date='2022-03-02' --period=daily \
--_facets=product --signature='HeaderMismatch' --format=markdown
```
date | -- | Fenix | Firefox | Focus
---- | -- | ----- | ------- | -----
2022-02-23 00:00:00 | 0 | 0 | 0 | 0
2022-02-24 00:00:00 | 0 | 3 | 0 | 0
2022-02-25 00:00:00 | 0 | 1 | 0 | 0
2022-02-26 00:00:00 | 0 | 1 | 0 | 0
2022-02-27 00:00:00 | 0 | 1 | 0 | 0
2022-02-28 00:00:00 | 0 | 9 | 1 | 0
2022-03-01 00:00:00 | 0 | 5 | 0 | 1
2022-03-02 00:00:00 | 0 | 1800 | 0 | 57
If we look at product that have `EMPTY` in the signature (denoting some problem with the minidump), we see this:
```
$ supersearchfacet --start-date='2022-02-23' --end-date='2022-03-02' --period=daily \
--_facets=product --signature='EMPTY' --format=markdown
```
date | -- | Fenix | Firefox | Focus | ReferenceBrowser
---- | -- | ----- | ------- | ----- | ----------------
2022-02-23 00:00:00 | 0 | 7241 | 772 | 395 | 0
2022-02-24 00:00:00 | 0 | 6323 | 832 | 307 | 0
2022-02-25 00:00:00 | 0 | 5804 | 661 | 299 | 2
2022-02-26 00:00:00 | 0 | 6648 | 748 | 342 | 0
2022-02-27 00:00:00 | 0 | 6349 | 487 | 342 | 0
2022-02-28 00:00:00 | 0 | 6101 | 870 | 225 | 0
2022-03-01 00:00:00 | 0 | 6344 | 838 | 237 | 0
2022-03-02 00:00:00 | 0 | 5700 | 1019 | 245 | 0
If we look at EMPTY signatures for Fenix over the last 7 days, we see this:
```
$ supersearchfacet --start-date='2022-02-23' --end-date='2022-03-02' --_facets=signature \
--signature='EMPTY' --product=Fenix --period=daily
```
date | -- | EMPTY: no crashing thread identified | EMPTY: no crashing thread identified; EmptyMinidump | EMPTY: no crashing thread identified; HeaderMismatch | EMPTY: no crashing thread identified; MissingSystemInfo | EMPTY: no crashing thread identified; MissingThreadList | EMPTY: no crashing thread identified; unknown error | OOM large EMPTY: no crashing thread identified; EmptyMinidump
---- | -- | ------------------------------------ | --------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------- | ------------------------------------------------------- | --------------------------------------------------- | -----------------------------------------------------------------
2022-02-23 00:00:00 | 0 | 1184 | 5989 | 0 | 3 | 27 | 38 | 0
2022-02-24 00:00:00 | 0 | 965 | 5259 | 3 | 10 | 26 | 60 | 0
2022-02-25 00:00:00 | 0 | 943 | 4781 | 1 | 4 | 36 | 38 | 1
2022-02-26 00:00:00 | 0 | 841 | 5719 | 1 | 1 | 41 | 45 | 0
2022-02-27 00:00:00 | 0 | 832 | 5429 | 1 | 3 | 38 | 46 | 0
2022-02-28 00:00:00 | 0 | 816 | 5190 | 9 | 5 | 47 | 34 | 0
2022-03-01 00:00:00 | 0 | 955 | 5308 | 5 | 9 | 31 | 35 | 1
2022-03-02 00:00:00 | 0 | 785 | 3060 | 1800 | 2 | 24 | 29 | 0
Ergo, while I think there is a bug in the extract_payload code or the Fenix crash reports in question are malformed, I think the crash reports it affects have junk minidumps and rust-minidump would have kicked up a "EmptyMinidump" before and now kicks up a "HeaderMismatch".
Assuming `HeaderMismatch` in the signature is always an indicator of the issue, it looks like it only affects Fenix crash reports:
```
$ supersearchfacet --start-date='2022-02-23' --end-date='2022-03-02' --period=daily \
--_facets=product --signature='HeaderMismatch' --format=markdown
```
date | -- | Fenix | Firefox | Focus
---- | -- | ----- | ------- | -----
2022-02-23 00:00:00 | 0 | 0 | 0 | 0
2022-02-24 00:00:00 | 0 | 3 | 0 | 0
2022-02-25 00:00:00 | 0 | 1 | 0 | 0
2022-02-26 00:00:00 | 0 | 1 | 0 | 0
2022-02-27 00:00:00 | 0 | 1 | 0 | 0
2022-02-28 00:00:00 | 0 | 9 | 1 | 0
2022-03-01 00:00:00 | 0 | 5 | 0 | 1
2022-03-02 00:00:00 | 0 | 1800 | 0 | 57
If we look at signatures that have `EMPTY` in them (denoting some problem with the minidump), we see this:
```
$ supersearchfacet --start-date='2022-02-23' --end-date='2022-03-02' --period=daily \
--_facets=product --signature='EMPTY' --format=markdown
```
date | -- | Fenix | Firefox | Focus | ReferenceBrowser
---- | -- | ----- | ------- | ----- | ----------------
2022-02-23 00:00:00 | 0 | 7241 | 772 | 395 | 0
2022-02-24 00:00:00 | 0 | 6323 | 832 | 307 | 0
2022-02-25 00:00:00 | 0 | 5804 | 661 | 299 | 2
2022-02-26 00:00:00 | 0 | 6648 | 748 | 342 | 0
2022-02-27 00:00:00 | 0 | 6349 | 487 | 342 | 0
2022-02-28 00:00:00 | 0 | 6101 | 870 | 225 | 0
2022-03-01 00:00:00 | 0 | 6344 | 838 | 237 | 0
2022-03-02 00:00:00 | 0 | 5700 | 1019 | 245 | 0
If we look at EMPTY signatures for Fenix over the last 7 days, we see this:
```
$ supersearchfacet --start-date='2022-02-23' --end-date='2022-03-02' --_facets=signature \
--signature='EMPTY' --product=Fenix --period=daily
```
date | -- | EMPTY: no crashing thread identified | EMPTY: no crashing thread identified; EmptyMinidump | EMPTY: no crashing thread identified; HeaderMismatch | EMPTY: no crashing thread identified; MissingSystemInfo | EMPTY: no crashing thread identified; MissingThreadList | EMPTY: no crashing thread identified; unknown error | OOM large EMPTY: no crashing thread identified; EmptyMinidump
---- | -- | ------------------------------------ | --------------------------------------------------- | ---------------------------------------------------- | ------------------------------------------------------- | ------------------------------------------------------- | --------------------------------------------------- | -----------------------------------------------------------------
2022-02-23 00:00:00 | 0 | 1184 | 5989 | 0 | 3 | 27 | 38 | 0
2022-02-24 00:00:00 | 0 | 965 | 5259 | 3 | 10 | 26 | 60 | 0
2022-02-25 00:00:00 | 0 | 943 | 4781 | 1 | 4 | 36 | 38 | 1
2022-02-26 00:00:00 | 0 | 841 | 5719 | 1 | 1 | 41 | 45 | 0
2022-02-27 00:00:00 | 0 | 832 | 5429 | 1 | 3 | 38 | 46 | 0
2022-02-28 00:00:00 | 0 | 816 | 5190 | 9 | 5 | 47 | 34 | 0
2022-03-01 00:00:00 | 0 | 955 | 5308 | 5 | 9 | 31 | 35 | 1
2022-03-02 00:00:00 | 0 | 785 | 3060 | 1800 | 2 | 24 | 29 | 0
Ergo, while I think there is a bug in the extract_payload code or the Fenix crash reports in question are malformed, I think the crash reports it affects have junk minidumps and rust-minidump would have kicked up a "EmptyMinidump" before and now kicks up a "HeaderMismatch".