Crash report: https://crash-stats.mozilla.org/report/index/fc047ad7-cb2e-4106-9d1e-f03760210818

Reason: EXCEPTION_ACCESS_VIOLATION_READ

Top 10 frames of crashing thread:

0 xul.dll cairo_pdf_interchange_end_page_content gfx/cairo/cairo/src/cairo-pdf-interchange.c:1485
1 xul.dll _cairo_pdf_surface_show_page gfx/cairo/cairo/src/cairo-pdf-surface.c:5333
2 xul.dll moz_cairo_surface_show_page gfx/cairo/cairo/src/cairo-surface.c:2555
3 xul.dll _cairo_paginated_surface_show_page gfx/cairo/cairo/src/cairo-paginated-surface.c:587
4 xul.dll moz_cairo_surface_show_page gfx/cairo/cairo/src/cairo-surface.c:2555
5 xul.dll mozilla::gfx::PrintTargetPDF::EndPage gfx/thebes/PrintTargetPDF.cpp:63
6 xul.dll nsDeviceContext::EndPage gfx/src/nsDeviceContext.cpp:582
7 xul.dll mozilla::layout::RemotePrintJobParent::PrintPage layout/printing/ipc/RemotePrintJobParent.cpp:171
8 xul.dll mozilla::layout::RemotePrintJobParent::FinishProcessingPage layout/printing/ipc/RemotePrintJobParent.cpp:146
9 xul.dll mozilla::layout::RemotePrintJobParent::RecvProcessPage layout/printing/ipc/RemotePrintJobParent.cpp:121

• I've encountered this crash while trying to print this page on two different tabs on Firefox 92.0b5.

[Platforms Affected]

• Windows 7

[Steps to Reproduce]

1. Launch Firefox
2. Open this page in two tabs
3. Open print preview on both on them and change printing settings to random ones on both
4. After the print preview is loaded, click on print on both tabs

[Notes]

• The crash can be seen in the attachment
• Feel free to change the component to the right one

Jonathan, any idea what might have caused this?

This may be related to bug 1722300 (see also bug 1725798, bug 1725743), though I haven't gotten to the bottom of it yet.

(In reply to Jonathan Kew (:jfkthame) from comment #2)

This may be related to bug 1722300 (see also bug 1725798, bug 1725743), though I haven't gotten to the bottom of it yet.

jfkthame: do you think this was fixed by bug 1722300? (or bug 1725743)? (if so, should we dupe/close?)

I suspect bug 1725743 will have "fixed" this (well, more like wallpapered it by disabling the feature from bug 1722300 for now), but don't know that for certain. The fact that we don't seem to have any crash reports from 92.0b9 is a promising sign, but I'm inclined to give it a few more days before closing as a dupe, given the rate was never more than a handful of crashes.

Given that there are no reports later than 92.0b8, I think we can safely consider this fixed by bug 1725743.