Bugzilla

Note: in comment 6, I was looking back 3 months.  If I look back a bit further (6 months of history, 28 total crashes), I found some additional crashes which don't involve that `br` DLL and which weren't from that old 10.0.14393 windows-version:

bp-80ace716-594b-49af-84be-38d630210714 (Windows 10.0.18363 ; note, the backtrace doesn't quite make sense)
bp-aea556fe-e98b-4c03-8a3a-472690210615 (Windows 10.0.18363; note, the backtrace doesn't show any Mozilla code and is mostly in an HP print driver I think)
bp-415c3e8c-2c4e-446b-bf9f-9896b0210624 (Windows 10.0.19043, nothing stands out as too notable in this one except that it's in Thunderbird ESR 78.11.0 and our crash-backtrace click-to-view-source links unfortunately don't seem to work)

I think all the other ones that I clicked through from digging back that far were still from that one particular old Windows version, 10.0.14393.

So, this is seeming like it's a combination of the following:
(1) an old Windows bug that's been fixed in newer versions.
(2) crashes from drivers and/or malware DLLs.
(3) possibly some other extremely-rare Windows crash (e.g. that single [last crash report](https://crash-stats.mozilla.org/report/index/415c3e8c-2c4e-446b-bf9f-9896b0210624) that I linked above), which also seems like it could easily be a Windows bug, or somehow-a-mozilla-bug that's nonetheless been fixed since 78.)

So, I don't think it's worth tracking this as a Mozilla bug at this point.  Calling it INVALID since it's nearly-or-entirely explained by bugs in other software (mostly that one specific old windows version)

Note: in comment 6, I was looking back 3 months.  If I look back a bit further (6 months of history, 28 total crashes), I found some additional crashes which don't involve that `br` DLL and which weren't from that old 10.0.14393 windows-version:

bp-80ace716-594b-49af-84be-38d630210714 (Windows 10.0.18363 ; note, the backtrace doesn't quite make sense)
bp-aea556fe-e98b-4c03-8a3a-472690210615 (Windows 10.0.18363; note, the backtrace doesn't show any Mozilla code and is mostly in an HP print driver I think)
bp-415c3e8c-2c4e-446b-bf9f-9896b0210624 (Windows 10.0.19043, nothing stands out as too notable in this one except that it's in Thunderbird ESR 78.11.0 and our crash-backtrace click-to-view-source links unfortunately don't seem to work)

I think all the other ones that I clicked through from digging back that far were still from that one particular old Windows version, 10.0.14393.   So, this still seems to be largely-explained by a bug in that version.

Bottom line: this is seeming like it's a combination of the following:
(1) an old Windows bug that's been fixed in newer versions.
(2) crashes from drivers and/or malware DLLs.
(3) possibly some other extremely-rare Windows crash (e.g. that single [last crash report](https://crash-stats.mozilla.org/report/index/415c3e8c-2c4e-446b-bf9f-9896b0210624) that I linked above), which also seems like it could easily be a Windows bug, or somehow-a-mozilla-bug that's nonetheless been fixed since 78.)

So, I don't think it's worth tracking this as a Mozilla bug at this point.  Calling it INVALID since it's nearly-or-entirely explained by bugs in other software (mostly that one specific old windows version)

Note: in comment 6, I was looking back 3 months.  If I look back a bit further (6 months of history, 28 total crashes), I found some additional crashes which don't involve that `br` DLL and which weren't from that old 10.0.14393 windows-version:

bp-80ace716-594b-49af-84be-38d630210714 (Windows 10.0.18363 ; note, the backtrace doesn't quite make sense)
bp-aea556fe-e98b-4c03-8a3a-472690210615 (Windows 10.0.18363; note, the backtrace doesn't show any Mozilla code and is mostly in an HP print driver I think)
bp-415c3e8c-2c4e-446b-bf9f-9896b0210624 (Windows 10.0.19043, nothing stands out as too notable in this one except that it's in Thunderbird ESR 78.11.0 and our crash-backtrace click-to-view-source links unfortunately don't seem to work)

I think all the other ones that I clicked through from digging back that far were still from that one particular old Windows version, 10.0.14393.   So, this still seems to be largely-explained by a bug in that version.

Bottom line: this bug report is seeming like it's a combination of the following:
(1) an old Windows bug that's been fixed in newer versions.
(2) crashes from drivers and/or malware DLLs.
(3) possibly some other extremely-rare Windows crash (e.g. that single [last crash report](https://crash-stats.mozilla.org/report/index/415c3e8c-2c4e-446b-bf9f-9896b0210624) that I linked above), which also seems like it could easily be a Windows bug, or somehow-a-mozilla-bug that's nonetheless been fixed since 78.)

So, I don't think it's worth tracking this as a Mozilla bug at this point.  Calling it INVALID since it's nearly-or-entirely explained by bugs in other software (mostly that one specific old windows version)

Note: in comment 6, I was looking back 3 months.  If I look back a bit further (6 months of history, 28 total crashes), I found some additional crashes which don't involve that `br` DLL and which weren't from that old 10.0.14393 windows-version:

bp-80ace716-594b-49af-84be-38d630210714 (Windows 10.0.18363 ; note, the backtrace doesn't quite make sense)
bp-aea556fe-e98b-4c03-8a3a-472690210615 (Windows 10.0.18363; note, the backtrace doesn't show any Mozilla code and is mostly in an HP print driver I think)
bp-415c3e8c-2c4e-446b-bf9f-9896b0210624 (Windows 10.0.19043, nothing stands out as too notable in this one except that it's in Thunderbird ESR 78.11.0 and our crash-backtrace click-to-view-source links unfortunately don't seem to work)

I think all the other ones that I clicked through from digging back that far were still from that one particular old Windows version, 10.0.14393.   So, this still seems to be largely-explained by a bug in that version.

Bottom line: this bug report is seeming like it's a combination of the following:
(1) an old Windows OS bug that's been fixed in newer versions.
(2) crashes from drivers and/or malware DLLs.
(3) possibly some other extremely-rare Windows crash (e.g. that single [last crash report](https://crash-stats.mozilla.org/report/index/415c3e8c-2c4e-446b-bf9f-9896b0210624) that I linked above), which also seems like it could easily be a Windows bug, or somehow-a-mozilla-bug that's nonetheless been fixed since 78.)

So, I don't think it's worth tracking this as a Mozilla bug at this point.  Calling it INVALID since it's nearly-or-entirely explained by bugs in other software (mostly that one specific old windows version)

Note: in comment 6, I was looking back 3 months.  If I look back a bit further (6 months of history, 28 total crashes), I found some additional crashes which don't involve that `br` DLL and which weren't from that old 10.0.14393 windows-version:

bp-80ace716-594b-49af-84be-38d630210714 (Windows 10.0.18363 ; note, the backtrace doesn't quite make sense)
bp-aea556fe-e98b-4c03-8a3a-472690210615 (Windows 10.0.18363; note, the backtrace doesn't show any Mozilla code and is mostly in an HP print driver I think)
bp-415c3e8c-2c4e-446b-bf9f-9896b0210624 (Windows 10.0.19043, nothing stands out as too notable in this one except that it's in Thunderbird ESR 78.11.0 and our crash-backtrace click-to-view-source links unfortunately don't seem to work)

I think all the other ones that I clicked through from digging back that far were still from that one particular old Windows version, 10.0.14393.   So, this still seems to be largely-explained by a bug in that version.

Bottom line: this bug report is seeming like it's a combination of the following:
(1) an old Windows OS bug that's been fixed in newer versions.
(2) crashes from drivers and/or malware DLLs (with `brpri19d.dll`/`breni19d.dll` or `brpri19c.dll`/`breni19c.dll` in the backtrace)
(3) possibly some other extremely-rare Windows crash (e.g. that single [last crash report](https://crash-stats.mozilla.org/report/index/415c3e8c-2c4e-446b-bf9f-9896b0210624) that I linked above), which also seems like it could easily be a Windows bug, or somehow-a-mozilla-bug that's nonetheless been fixed since 78.)

So, I don't think it's worth tracking this as a Mozilla bug at this point.  Calling it INVALID since it's nearly-or-entirely explained by bugs in other software (mostly that one specific old windows version)