P: Plugin Crashes when a Plug-in uses LrTasks.execute

Report · Sep 06, 2024

I am a developer of the Lightroom Classic plug-in Excire Seach (https://www.excire.com). The plug-in uses the function LrTasks.execute to start a background process. The plug-in has been used by many users for some years and this part always worked well.

Since version 13.5 of Lightroom Classic some Intel Mac users with the current macOS Sonoma experience the issue, that a subprocess of Lightroom Classic crashes (with a segmentation fault) when LrTasks.execute is called by the plug-in. It does not always crash but most of the times. LrTasks.execute returns the value 11.

The newest version 13.5.1 does not fix the issue.

I have attached the crash report generated by macOS (as txt because .ips is not supported to be uploaded).

The plug-in starts several LrTasks and interacts with the LrC catalog before it calls LrTasks.execute. I tried to write a very simple plug-in that does nothing but calling LrTasks.execute, but it does not reproduce the issue.

Report · Sep 06, 2024

Can you reproduce the crash? If so, did you submit a crash report and include the email address associated with your Creative Cloud subscription? If you can't reproduce it, then ensure one of your customers submits a crash report and include their Creative Cloud email address in the submission, and then send a private message with that email to Adobe employee @Rikk Flohr: Photography. He will look up the crash report and inject it into the bug workflow.

Report · Sep 15, 2024

Thank you for the tip!
We were able to reproduce the crash on one Intel Macbook. Re-installing Lightroom Classic solved the problem on this machine. Unfortunately, a re-installation does not solve it for all affected users. I am in contact with an employee of Adobe now who has our crash report.

Report · Sep 27, 2024

For the past 3 weeks, I've had an issue where Lightroom Classic will stop in the middle of an export and give me an error. The app doesn't close, but the export stops and the "Problem Report for Lightroom Classic" pops up. This is what the report says:

-------------------------------------

Translated Report (Full Report Below)

-------------------------------------

Process: Adobe Lightroom Classic [61710]

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 [8082]

Responsible: Adobe Lightroom Classic [8082]

User ID: 501

Date/Time: 2024-09-26 10:40:42.3110 -0400

OS Version: macOS 15.0 (24A335)

Report Version: 12

Bridge OS Version: 9.0 (22P353)

Anonymous UUID: ADAFE0CD-A137-8D50-44A4-10637E801432

Time Awake Since Boot: 45000 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00003bfa2616a38e

Exception Codes: 0x0000000000000001, 0x00003bfa2616a38e

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11

Terminating Process: exc handler [61710]

-----

Also posting my LR System info below:

Lightroom Classic version: 13.5.1 [ 202408271704-d15d09cd ]
License: Creative Cloud
Language setting: en-US
Operating system: Mac OS 15
Version: 15.0.0 [24A335]
Application architecture: x64
Logical processor count: 20
Processor speed: 3.6GHz
SqLite Version: 3.36.0
Built-in memory: 65,536.0 MB
Dedicated GPU memory used by Lightroom: 490.3MB / 8,176.0MB (5%)
Real memory available to Lightroom: 65,536.0 MB
Real memory used by Lightroom: 18,224.9 MB (27.8%)
Virtual memory used by Lightroom: 59,506.9 MB
Memory cache size: 4,834.2MB
Internal Camera Raw version: 16.5 [ 1954 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 6403MB / 32767MB (19%)
Camera Raw real memory: 6829MB / 65536MB (10%)

Cache1:
Final1- RAM:352.0MB, VRAM:0.0MB, IMG_0012.CR3
NT- RAM:352.0MB, VRAM:0.0MB, Combined:352.0MB

Cache2:
m:4,834.2MB, n:352.3MB

U-main: 258.0MB

Standard Preview Size: 5120 pixels
Displays: 1) 5120x2880

Graphics Processor Info:
Metal: AMD Radeon Pro 5500 XT
Init State: GPU for Export supported by default
User Preference: Off

Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Users/danacubbage/Desktop/2024-09-07 Abby + Greydon/2024-09-07 Abby + Greydon.lrcat
Settings Folder: /Users/danacubbage/Library/Application Support/Adobe/Lightroom

Installed Plugins:
1) AdobeStock
2) Aperture/iPhoto Importer Plug-in
3) Flickr
4) JPEGmini
5) Nikon Tether Plugin

Config.lua flags:

And a screenshot (below) of my Lightroom Preference settings. I've been on chat with Adobe a ton of times over the past few weeks and we've tried the following: uninstall/reinstalling Lightroom Classic, trying older versions of LrC, changing permissions on Adobe folders, resetting LrC preferences, disabling the GPU on export, disabling the GPU completely, exporting to different hard drives, exporting from a test user on my mac, updating macOS, exporting in safe mode, etc. Nothing seems to help.

The amount of time/images it takes for the error to occur varies. Sometimes I can export 100 images without it stopping. Sometimes it's only 4-5 images, then I get the error.

Adobe mentioned that there could be an issue with Intel i9 and AMD with the new version of LrC. Just trying to see what else I can try - I really don't want to have to buy a new mac since this one is only 3 years old 😞 Thanks in advance for any insight you can provide!!

Report · Sep 27, 2024

Thank you for reaching out and sharing all these details. It really helps us gain a clearer understanding of what might be happening faster.

Which version of Lightroom Classic did not have this issue? ^CM

Report · Sep 27, 2024

I'm not 100% sure if I had updated from 13.4/13.5 to 13.5.1 before this issue started, but we tried installing older versions once this export issue started - and even the older versions were crashing 😞

Report · Sep 27, 2024

Following is not the cause, nor solution to your problem, just an observation of an issue that will cause you some performance issues in the develop module. You have the Adobe default of 5 GB for Camera RAW CACHE limit. Even Adobe in documentation states that is too low and to increase to at least 20GB

Report · Sep 30, 2024

Thank you for the update. Have you seen a way to send a crash report at all? The team is asking if you can submit a crash report and PM the email address you enter.

Report · Sep 30, 2024

Did this issue start in coincidence with your upgrade to Mac OS 15?

What is your drive configuration? Are you exporting to a different drive than before the issue?

Ken Seals - Nikon Z 9, Z 8, 14mm-800mm. Computer Win 11 Pro, I7-14700K, 64GB, RTX3070TI. Travel machine: 2021 MacBook Pro M1 MAX 64GB. All Adobe apps.

Report · Sep 30, 2024

The Problem Report for Adobe Lightroom Classic send directly to Apple, I believe. I copy/pasted the report and am attaching it here

Report · Sep 30, 2024

No, it started while I was still using Sonoma - prior to updating to Mac OS 15 Sequoia. I recently upgraded to Sonoma in hopes that it would resolve the issue... which it didn't.

I've always exported to my Mac desktop and haven't had any issues doing so until early September.

Report · Oct 02, 2024

Thank you for sharing that information. Are you receiving any crash reports for Lightroom Classic? If not, please follow the steps in this article (under the 'Note' section) to enable crash report prompts: https://adobe.ly/3ZNRc5T

^CM

Report · Oct 05, 2024

A customer of my Any Tag has run into the same issue, with LR crashing sometimes (but not always) as it forks a child process to execute the Exiftool program in LrTasks.execute():

Application Specific Information:
crashed on child side of fork pre-exec

Thread 0 Crashed:
0   libobjc.A.dylib              0x7ff814606522 objc_destructInstance + 37
1   libobjc.A.dylib              0x7ff8146121f5 object_dispose + 19
2   Chromium Embedded Framework     0x14ba64af2 ChromeAppModeStart_v7 + 31083138
3   libxpc.dylib                 0x7ff8146da04f -[OS_xpc_object dealloc] + 47
4   libsystem_asl.dylib          0x7ff81a07dbde _asl_mt_shim_fork_child + 33
5   libSystem.B.dylib            0x7ff821c7ac62 libSystem_atfork_child + 53
6   libsystem_c.dylib            0x7ff81489fca4 fork + 84
7   AgSubstrate                     0x105cfb526 AgWorkspace_executeWithoutFileDescriptors_L +

A crash report from the customer is attached.

This is the only report I've received from the thousands who use the plugin. The customer's report:

"I am using the plugin “AnyTag” version 1.16 by John Ellis (https://johnrellis.com/lightroom/anytag.htm). Since about 2 -3 months I have the following issue: When using the option to “Commit Locations” while having selected more than 10-15 photos, I get this error message and the locations identified by geo coordinates are not committed to the meta data. Usually, it works when selecting less than 10 photos at once. About 2-3 months ago, I was also able to commit locations when selecting 100 or more photos. As far as I remember I updated Lightroom Classic to the latest version during this time which may be a reason for the issue. I want that I can bulk commit locations again as described here: https://johnrellis.com/lightroom/anytag.htm#usinglocations"

Report · Oct 05, 2024

@Rikk Flohr: Photography, please move to Bugs. I will send you the customer's email address in a private message, so you can cross-reference the crash reports.

Report · Oct 06, 2024

No crash reports were found under that address under versions 13.3.1, 13.4, 13.5 or 13.5.1

Rikk Flohr: Adobe Photography Org

Report · Oct 07, 2024

I submitted twice the crash report via Lightroom using my email address. In the meantime, I have accepted to submit automatically system information to Adobe. I don't have images with uncomitted locations in my library at the moment to submit another crash report. However, you can find all details in the commit-error.txt file which John has added. Here you can also find my system info:

Lightroom Classic version: 13.5.1 [ 202408271704-d15d09cd ]
License: Creative Cloud
Language setting: en-CH
Operating system: Mac OS 14
Version: 14.6.1 [23G93]
Application architecture: x64
Logical processor count: 16
Processor speed: 2.4GHz
SqLite Version: 3.36.0
Power Source: Plugged In, 78%, Charging
Built-in memory: 65'536.0 MB
Dedicated GPU memory used by Lightroom: 72.7MB / 8'176.0MB (0%)
Real memory available to Lightroom: 65'536.0 MB
Real memory used by Lightroom: 2'897.1 MB (4.4%)
Virtual memory used by Lightroom: 46'384.8 MB
Memory cache size: 1'150.6MB
Internal Camera Raw version: 16.5 [ 1954 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 41MB / 32767MB (0%)
Camera Raw real memory: 43MB / 65536MB (0%)

Cache1:
NT- RAM:0.0MB, VRAM:0.0MB, Combined:0.0MB

Cache2:
m:1'150.6MB, n:0.0MB

U-main: 174.0MB

Standard Preview Size: 3840 pixels
Displays: 1) 3840x1600

Graphics Processor Info:
Metal: AMD Radeon Pro 5500M
Init State: GPU for Export supported by default
User Preference: GPU for Display Enabled
Enable HDR in Library: OFF

Application folder: /Applications/Adobe Lightroom Classic
Library Path: /Users/flip/Documents/Space/06 Media/Catalogs/Lightroom/*/*-v13-3.lrcat
Settings Folder: /Users/flip/Library/Application Support/Adobe/Lightroom

Installed Plugins:
1) AI Keywording
2) Any Filter
3) Any Tag
4) Any Vision
5) Backup Cleaner
6) Find Duplicates 2
7) Flickr
8) jb: Search + Replace
9) jf Data Explorer
10) jf Geocoding Support
11) jf Megapixel Sort
12) jf Metadata Viewer
13) jf Metadata Wrangler
14) Show Focus Points
15) Teekesselchen

Config.lua flags:

Report · Oct 07, 2024

Eventually, the crash report is sent to Apple and not Adobe? Here you can find a screen recording: https://www.dropbox.com/scl/fi/5vex0a7ecpxgl1bht7wnz/Screen-Recording-2024-10-07-at-11.50.41.mov?rlk...

Attached you can find the latest crash report.

Report · Oct 31, 2024

@Rikk Flohr: Photography Do you have any update on my issue? I just upgraded to LR Classic 14.x and hoped that the issue is solved but I still can only commit locations to a couple of images. I have now 400 images and need to commit location data to images in batches of 10 images which means doing the steps manually 40 times which is sooo time consuming.

Report · Oct 31, 2024

@fischerluebeck: "Unfortunately, a re-installation does not solve it for all affected users. I am in contact with an employee of Adobe now who has our crash report."

Was there any further progress on this? Did you learn anything about what might trigger these crashes and how to possibly work around them?

Report · Nov 18, 2024

Sorry for the delay.

The adobe employee that contacted me was unable to reproduce the crashes.

Unfortunately, after the reinstallation of Lightroom Classic on the only one of our own Macs that reproduced the issue, we are also unable to reproduce it.

I can confirm that the issue is still not fixed. We still get error reports from customers with the latest version of Lightroom Classic.

We know that the issue does occur only on Macs with intel CPU (not Apple Silicon architecture). And we know that it does not occur on each start of Lightroom Classic and the Excire Search plugin, but like every second or third start.

We tell our customers to try a restart of Lightroom Classic. This fixes the issue for a very few of them. If the crash occurs a user can restart Lightroom Classic in order to be able to use Excire Search, because the crash does not occur on every start.

Report · Nov 18, 2024

Sigh, thanks very much for that helpful (but disappointing) information. I suspect this is one of those bugs that will never get fixed.

Report · Dec 03, 2024

@Rikk Flohr: Photography, the user "camner" in the Lightroom Queen forum experiences these crashes regularly, under at least two scenarios:

- Using the plugin jf Metadata Wrangler as an export post-process action (the plugin invokes Exiftool).

- Using the jb Capture Time To Exif plugin (which also invokes Exiftool).

(Note that the original bug report involves an Excire program, not Exiftool).

One of his crash reports is attached. I'm asking him to private-message you with his Adobe Id email address. The crash report shows the same proximate cause as the other two reports here:

"Application Specific Information:
crashed on child side of fork pre-exec"

That's Mac/Unix-speak for the low-level mechanism a process uses for creating a child process to run a program. It "forks" itself, and the newly created child process loads ("execs") the desired program. Apparently the child process is crashing after the fork but before the exec.

Also, all the reports are for LR on Intel Macs.

Report · Dec 04, 2024

@Rikk Flohr: Photography, "camner" in the Lightroom Queen forum observes that the Adobe crash dialog never appears, just the one for reporting the crash to Apple. This is most likely because, as I described above, the crash is happening in the child process after the main LR process forks but before it execs the child program, and the Adobe crash helper process monitors the main process only.

So is the text crash report (two of which are attached above) adequate to inject this into Bugs? Is it possible for the team to get the Apple crash report?

Report · Dec 04, 2024

At this point, sharing the crash report would be premature. I have injected your comments from 13 hours ago into the previous conversation I had with the team. Let's see what they come back with.

Rikk Flohr: Adobe Photography Org

Report · Dec 04, 2024

Using a 2018 15" Macbook Pro, Intel. Sequoia 15.1.1 and LR Classic 14.0.1

Just upgraded from a 2015 Macbook Pro - this would happen with the 2015 model, too, but not as much. Now it is every time we try to export.

When exporting large collections of images (such as 800 wedding photographs) - it crashes every time. Smaller collections around 100, sometimes it will get through it.

We've disabled GPU, changed export settings, up'd CACHE setting to 20GB, cleared cache- done so many things.

Driving us nuts.

Any idea of what we can do? Crash report attached:

Basic details of report here:

Process: Adobe Lightroom Classic [16814]

Path: /Applications/Adobe Lightroom Classic/Adobe Lightroom Classic.app/Contents/MacOS/Adobe Lightroom Classic

Identifier: com.adobe.LightroomClassicCC7

Version: 14.0.1 (14.0.1)

Code Type: X86-64 (Native)

Parent Process: Adobe Lightroom Classic [16452]

Responsible: Adobe Lightroom Classic [16452]

User ID: 503

Date/Time: 2024-12-04 15:20:21.5667 -0600

OS Version: macOS 15.1.1 (24B91)

Report Version: 12

Bridge OS Version: 9.1 (22P1072)

Anonymous UUID: 6F7261CE-C0B0-D798-324D-788057BC74E2

Sleep/Wake UUID: E88CAB6E-7DF8-4EB3-8066-9A273868DFE1

Time Awake Since Boot: 62000 seconds

Time Since Wake: 8362 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x0000107f6cb49b4e

Exception Codes: 0x0000000000000001, 0x0000107f6cb49b4e

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11

Terminating Process: exc handler [16814]

VM Region Info: 0x107f6cb49b4e is not in any region. Bytes after previous region: 18132404415311 Bytes before following region: 87413645599922

REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL

mapped file 1a52e5000-1a52e7000 [ 8K] r--/rwx SM=S/A Object_id=e5fdfc98

---> GAP OF 0x5ffe5ad19000 BYTES

MALLOC_NANO 600000000000-600020000000 [512.0M] rw-/rwx SM=COW

Application Specific Information:

crashed on child side of fork pre-exec

Report · Dec 04, 2024

"Application Specific Information:

crashed on child side of fork pre-exec"

You probably have a plugin that's running an Export post-processing action that runs an external program, such as Metadata Wrangler or JPEG Mini. Disable that and the exports should complete without crashing.

So far, there isn't any known workaround for this bug other than disabling the post-processing action.