Crash report: https://crash-stats.mozilla.org/report/index/422ee101-1114-4141-9eb0-a98730200828

Top 10 frames of crashing thread:

0 libobjc.A.dylib initializeAndMaybeRelock 
1 libobjc.A.dylib lookUpImpOrForward 
2 libobjc.A.dylib _objc_msgSend_uncached 
3 Foundation -[NSPlaceholderString initWithString:] 
4 Foundation +[NSString stringWithString:] 
5 KfSummary KfSummary@0xd303 
6 KfSummary KfSummary@0xcb25 
7 PrintCocoaUI PrintCocoaUI@0x26f2 
8 PrintCocoaUI PrintCocoaUI@0x8be7 
9 PrintCocoaUI CreateDefaultFileName 

Encountered this crash using 81.0b3 (with old print UI) on macOS 10.14 while printing an RTL pdf document while the "Work Offline" option was set.

Will get back with a full description shortly.

Once bug 1653340 lands, this codepath (PrintingParent::ShowPrintDialog) will no longer be exercised.

Emil: Now that bug 1653340 has landed, can you try to reproduce this in the old UI?

(In reply to Jonathan Watt [:jwatt] from comment #1)

Once bug 1653340 lands, this codepath (PrintingParent::ShowPrintDialog) will no longer be exercised.

I missed that this bug was about the old UI specifically. This codepath is still exercised by the old UI.

With regards to priority, there don't appear to be new crash reports against Beta yet since the single crash on the 28 August (the day this bug was reported). It's a bit early to say since the pref only just turned off in 81b7, but it seems unlikely this is a big issue.

I'll keep this on the v82 list for now, but drop to P3 given no further crashes have been reported.

I have not encountered this crash during this week's test run.

I missed that this bug was about the old UI specifically. This codepath is still exercised by the old UI.

Given ^ and the fact that this crash was encountered quite randomly (without any reliable STR) I'm going to remove the ni for now but I'll keep an eye on this signature for our next test runs.

In reply to comment #0:

5 KfSummary KfSummary@0xd303
6 KfSummary KfSummary@0xcb25

KfSummary seems to be part of a third party Kyocera printer driver:

https://gist.github.com/jirutka/55f0c1f3357be666b7f7ca466a7a80e8

So this is likely a bug in third party software.

Closing because no crashes reported for 12 weeks.