Copy link to clipboard
Printing crashes LR when parameters are set wrong
Steps to reproduce:
Expected result: Either an error message, or the print module should reset the printer panel if there are fewer images in the panel than are referred to in the panel.Actual result: LR crashes.
Updates to the Adobe Photography Products were released today and contain a fix for this issue. Please install the update via your Creative Cloud Desktop App or your respective App Store.
You may need to refresh the Creative Cloud App for desktop software to show an update available. ([Ctrl/Cmd]+[Alt/Opt]+ [ R ])
For Mobile downloads, it may take several days for the update to appear in your respective App Stores.
Thank you for your patience.
First thing to try when LR crashes is resetting your Lightroom preferences:https://helpx.adobe.com/lightroom-classic/help/setting-preferences-lightroom.html
Quit Lightroom Classic.MacOS: Press and hold the Shift + Option keys.Windows: Press and hold the Shift + Alt keys.While holding down the keys, launch Lightroom Classic. When asked, select "Yes".
Thanks, dd. I eventually fixed it by simply correcting the page count (set it to "all" instead of selected pages), though that was after crashing it a few times until I noticed the discrepancy. Clearly, it's operator error and easy to correct once noticed. I filed the bug report just as a courtesy, because it shouldn't have crashed, but rather thrown an error message. A very low priority bug, but I'd consider it a bug nonetheless.
BTW, the page range spec in the printer panel was wrong because it had persisted from the last time that I'd used the Print module. So, it's an easy mistake to make, and it took a while to notice, at least for me, because one doesn't usually look at the page range spec when printing a single image. I guess if I'd used the "print" button instead of "printer", I wouldn't have even seen the panel with the fatal page range spec.
I can duplicate this BUG. Lightroom crashed. Crash report sent to Adobe.
I haven't been able to locate any crash reports under either of your email addresses. Did you use an email other than that you've used in this forum?
@Rikk Flohr: Photography
I reproduced this again and resent the Crash Report. I probably didn't send my email the first time. I also saved it as a text file in case you need me to send it to you directly.
I noticed an oddity. I tried this using a JPG this morning and it didn't crash but I tried it on the RAW I used last time and it produced the crash.
Than you for this, I was going nuts with it crashing and didn't realize that I had that exact issue in step 3 above. No more crashes for me.
We’ve reviewed the email address you use (Bob & loonsailer) with this forum and find no crash reports in our system.
Did you see a crash dialog?
Do you use a different email address when filling out the crash report?
Was the crash dialog Adobe’s? Microsoft’s? Apple’s?
I definately sent it to Adobe the second time I tried. I saved it as a text file so here it is.
-------------------------------------Translated Report (Full Report Below)-------------------------------------
Process: Adobe Lightroom Classic Path: /Applications/Adobe Lightroom Classic/Adobe Lightroom Classic.app/Contents/MacOS/Adobe Lightroom ClassicIdentifier: com.adobe.LightroomClassicCC7Version: 11.2 (11.2)Code Type: X86-64 (Native)Parent Process: launchd User ID: 501
Date/Time: 2022-02-08 08:41:21.3816 -0700OS Version: macOS 12.2 (21D49)Report Version: 12Anonymous UUID: 988B2EA6-F37E-AEAD-4CF4-0FF2B2E50791
Sleep/Wake UUID: 6F4B787E-1926-4078-9D3F-800341E80D48
Time Awake Since Boot: 13000 secondsTime Since Wake: 253 seconds
System Integrity Protection: enabled
Crashed Thread: 64
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)Exception Codes: 0x0000000000000001, 0x0000000000000000Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: Namespace SIGNAL, Code 4 Illegal instruction: 4Terminating Process: exc handler 
Application Specific Backtrace 0:0 CoreFoundation 0x00007ff804758f0b __exceptionPreprocess + 2421 libobjc.A.dylib 0x00007ff8044b9b9d objc_exception_throw + 482 CoreFoundation 0x00007ff804758d6f +[NSException raise:format:] + 1893 AppKit 0x00007ff80798f78b _NSRunModal + 2384 AppKit 0x00007ff8074cc2db NSRunAlertPanel + 4675 AppKit 0x00007ff807a51708 -[NSView(NSPrintingInternal) _printForCurrentOperation] + 1736 AppKit 0x00007ff8077bc679 -[NSConcretePrintOperation _renderView] + 1947 AppKit 0x00007ff8077bc85b -[NSConcretePrintOperation _continueModalOperationToTheEnd:] + 958 Foundation 0x00007ff80553b2d9 __NSThread__start__ + 10259 libsystem_pthread.dylib 0x00007ff8046164f4 _pthread_start + 12510 libsystem_pthread.dylib 0x00007ff80461200f thread_start + 15
Thread 64 Crashed:0 AppKit 0x7ff8074890de -[NSApplication _crashOnException:] + 3131 AppKit 0x7ff807488e0f -[NSApplication reportException:] + 7312 AppKit 0x7ff8077bc713 -[NSConcretePrintOperation _renderView] + 3483 AppKit 0x7ff8077bc85b -[NSConcretePrintOperation _continueModalOperationToTheEnd:] + 954 Foundation 0x7ff80553b2d9 __NSThread__start__ + 10255 libsystem_pthread.dylib 0x7ff8046164f4 _pthread_start + 1256 libsystem_pthread.dylib 0x7ff80461200f thread_start + 15Thread 64 crashed with X86 Thread State (64-bit):rax: 0x00007faa1d4d9000 rbx: 0x00007ff8044aa040 rcx: 0xc998a3f5892e0027 rdx: 0x0000000000000201rdi: 0x00007000049a36e0 rsi: 0x00000000000003f9 rbp: 0x00007000049a3b70 rsp: 0x00007000049a3b40r8: 0x00000000000001f9 r9: 0x00007000049a3120 r10: 0x00000000000001f9 r11: 0x00007faa1d4d93f9r12: 0x00007faa17113cc0 r13: 0x00007ff8044aa040 r14: 0x000060000fed0960 r15: 0x00007ff81edb7370rip: 0x00007ff8074890de rfl: 0x0000000000010206 cr2: 0x00007ff845e4c130
If you want me to send the Text file to someone at ADOBE please PM me where you want it sent with their address.
The recipe to produce this crash is fairly easy. Recreating the FULL scenario the OP posted is not necessary.
1 Select ONE RAW file
2 In the print module select PRINTER button
3 On Mac, change Pages in the dialog from ALL to FROM 3 to 4
4 Click Print in the DIALOG
I was able to reproduce with Bob's instructions and crash report. I have logged it with the team. Thanks for the help.
Bob is correct, it crashes when I try what he explains (change Pages in the dialog from ALL to FROM 3 to 4). I have a crash log now, but anyone at Adobe or elsewhere should be able to produce this crash.