Export Crashes when export, just me?

[jemostrom]

Lightroom Version Number

13.5.1

Operating System

1. macOS 15 Sequoia

LR Classic have started to crash when I export photos, it's a bit strange since the LRC UI keep on running but I get a crash dialog and a stack trace. So I guess that the export is not only done in a separate thread from the UI, but on a completely different process. Does this happen for just me or are there others who have the same problem

The top of the crash log reads

Process:               Adobe Lightroom Classic [6364]
Path:                  /Applications/Adobe Lightroom Classic/Adobe Lightroom Classic.app/Contents/MacOS/Adobe Lightroom Classic
Identifier:            com.adobe.LightroomClassicCC7
Version:               13.5.1 (13.5.1)
Code Type:             X86-64 (Native)
Parent Process:        Adobe Lightroom Classic [6299]

[snip]

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000282ab42bb19e
Exception Codes:       0x0000000000000001, 0x0000282ab42bb19e

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [6364]

VM Region Info: 0x282ab42bb19e is not in any region.  Bytes after previous region: 44148713623967  Bytes before following region: 61389239766626
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      mapped file                 387c6f000-387c72000    [   12K] r--/rwx SM=S/A  Object_id=6e1f8fe8
--->  GAP OF 0x5ffc7838e000 BYTES
      MALLOC_NANO              600000000000-600020000000 [512.0M] rw-/rwx SM=COW 

Application Specific Information:
*** multi-threaded process forked ***
crashed on child side of fork pre-exec


Thread 0 Crashed:
0   libobjc.A.dylib                       0x7ff819bcd4ea objc_destructInstance + 37
1   libobjc.A.dylib                       0x7ff819bd941d object_dispose + 19
2   Chromium Embedded Framework              0x128f1caf2 ChromeAppModeStart_v7 + 31083138
3   libxpc.dylib                          0x7ff819c9cad3 -[OS_xpc_object dealloc] + 47

 

[clee01l]

Sequoia is a recent update from Apple. I’m not sure Adobe has announced support for Sequoia. It is possible that this could be your problem. Are you using a Silicon or Intel Mac?

It might help Adobe if you report it as an issue. I am sure there will be bugs in MacOS 15 that will require a decimal update.


Sent from my iPad using Tapatalk

 

[jemostrom]

Intel, a 2018 Mini with a basic config ... so I can't take advantage of all the features in LR

This has happened for a while, I'm not sure if I had problem before I upgraded to Sequoia or not. I'll send some info to Adobe the next time it happens.

 

[Hal P Anderson]

In your Export dialogue, do you have something specified in the Post-Processing section, at the very end? If so, try running without specifying that.

 

[John R Ellis]

I’m not sure Adobe has announced support for Sequoia.

The Adobe Help says LR Classic is compatible with Mac OS 15 (Sequoia):
https://helpx.adobe.com/download-install/kb/macos-sequoia-compatibility-common-issues.html

 

[John R Ellis]

Intel, a 2018 Mini with a basic config ... so I can't take advantage of all the features in LR

Since Mac OS 14.4.1, LR has had issues with Intel Macs with certain GPUs. Next troubleshooting steps:

1. Do the LR menu command Help > System Info and copy/paste the entire contents here so we can see exactly which versions of hardware and software LR thinks you're running and important LR options that are set.

2. Set Preferences > Performance > Use Graphics Processor to Off. Do you still get the error?

 

[clee01l]

The Adobe Help says LR Classic is compatible with Mac OS 15 (Sequoia):
https://helpx.adobe.com/download-install/kb/macos-sequoia-compatibility-common-issues.html

I found that after I posted. It does not give a lot of confidence. Both Apple and Adobe can have as yet unknown bugs that could be at issue here.

I still think it’s a good idea to wait for MacOS 15.1


Sent from my iPhone using Tapatalk

 

[John R Ellis]

I still think it’s a good idea to wait for MacOS 15.1

Agreed. I haven't updated yet. (I use a Parallels virtual machine for testing with Mac OS 15 in the interim.)