New Participant

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

Forum|Forum|1 year ago
September 6, 2024
12 replies
6792 views

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.

crash-report.txt

Rikk Flohr_Photography

Community Manager

Greetings all,

A new update for the Adobe Photography products has been released. The August update contains an update regarding this issue.

If you do not see the update in your Creative Cloud Application, you can refresh it by pressing [Ctrl/Cmd]+[Alt/Opt]+[ R ].

Note: It may take up to 24 hours for your update to be available in your Creative Cloud app.

Thank you for being so patient.

Rikk Flohr: Adobe Photography Org

R

renzoelv.

New Participant

ME TOO

Hello,

I’m writing because I’m experiencing some troubles with Any Tag plug-in for light-room. I use it with Lightroom 14.2 Camera Raw 17.2 in order to commit locations.

I tried the plug-in before to buy it and it worked fine. After a while without using it, I decided to use it again and decided to buy the licence.

I don’t understand why if I select more then 10 photos to commit their locations I have the following message: Commit Locations Couldn’t run ExifTool. When I tried the plugin, I never experienced such a problem. Maybe I was using one of the previous versions of LightRoom? I don’t know.

Many thanks for your kind help.

Best regards,

Renzo

johnrellis

Braniac

@SunilBhaskaran: "Will executing in smaller batches help in this case?"

It's not clear. I don't have an Intel Mac and can't reproduce the issues directly. But the plugins that are failing are all apply operations to batches of photos, and it appears fairly random when the problem strikes, and if it is random, then smaller batches may not help (but just a guess).

S

SunilBhaskaran

Adobe Employee

Thanks, John.
We can repro the crash.
Will executing in smaller batches help in this case?

Thanks,
Sunil

johnrellis

Braniac

Note the telltale in @Ken5E27's crash report:

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

that indicates this is the same bug with LrTasks.execute().

K

Ken5E27

New Participant

I am using John Ellis' Any File plugin on two Intel iMacs running the latest version of Lightroom Classic. One of the iMacs is running Sonoma and the other Sequoia.

On both iMacs I am experiencing intermittent failures during the importing of eighteen MP3 files. The problem occurs more frequently on my Intel iMac that is running Sequoia. During the import the software will typically successfully import and create several thumbnails, but then at some random point during the import the software will stop the import and display a pop-up window that says Can't create proxy / Volumes/.....". When I hit the continue button in the pop-up window another pop-up window appears that says Can't import true into the catalog" -> LrCatalogaddPhoto: path parameter is missing or is not a string.

These failures are not consistent --- sometime the import works and other times it fails at some random point during the importing of the 18 files. The types of pop-up windows I get during a failure are consistent ("Can't import proxy.." and "Can't import true")

As a sanity check I have been running the same plugin on my Macbook Air M1 (2020) with the latest version of LrC and Sonoma. On this system I have not had any import failures when importing these same 18 MP3 files as well as many other types of files .

Below are the first two pages of a crash report that I was able to obtain during one of the import crashes on my Intel iMac running Sonoma:

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

Translated Report (Full Report Below)

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

Process: Adobe Lightroom Classic [1488]

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

Identifier: com.adobe.LightroomClassicCC7

Version: 14.2 (14.2)

Code Type: X86-64 (Native)

Parent Process: Adobe Lightroom Classic [1424]

Responsible: Adobe Lightroom Classic [1424]

User ID: 501

Date/Time: 2025-03-19 22:50:13.7885 -0500

OS Version: macOS 14.7.2 (23H311)

Report Version: 12

Bridge OS Version: 9.2 (22P2093)

Anonymous UUID: A1A97D21-E10F-1001-9391-376F9F0E534F

Time Awake Since Boot: 5900 seconds

System Integrity Protection: enabled

Crashed Thread: 0

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x000069d3c809434e

Exception Codes: 0x0000000000000001, 0x000069d3c809434e

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

Terminating Process: exc handler [1488]

VM Region Info: 0x69d3c809434e is not in any region. Bytes after previous region: 10804125057871 Bytes before following region:

6786992204978

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

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

---> GAP OF 0xfffc04bb000 BYTES

Stack Guard 7000004bb000-7000004bc000 [ 4K] ---/rwx SM=NUL

Application Specific Information:

crashed on child side of fork pre-exec

Thread 0 Crashed:

0 libobjc.A.dylib 0x7ff804887522 objc_destructInstance + 37

1 libobjc.A.dylib 0x7ff8048931f5 object_dispose + 19

2 Chromium Embedded Framework 0x11c74caf2 ChromeAppModeStart_v7 + 31083138

3 libxpc.dylib 0x7ff80495b04f -[OS_xpc_object dealloc] + 47

4 libsystem_asl.dylib 0x7ff80a2ffbde _asl_mt_shim_fork_child + 33

5 libSystem.B.dylib 0x7ff811efcc62 libSystem_atfork_child + 53

6 libsystem_c.dylib 0x7ff804b20ca4 fork + 84

7 AgSubstrate 0x109866876 AgWorkspace_executeWithoutFileDescriptors_L + 176

8 AgKernel 0x10970b8ed 0x109701000 + 43245

9 AgKernel 0x109719cc3 0x109701000 + 101571

10 AgKernel 0x10970bd4c 0x109701000 + 44364

11 AgKernel 0x10970b411 0x109701000 + 42001

12 AgKernel 0x10970bfad 0x109701000 + 44973

13 AgKernel 0x109703b42 lua_pcall + 98

14 AgKernel 0x10970593b 0x109701000 + 18747

15 AgKernel 0x10970b8ed 0x109701000 + 43245

16 AgKernel 0x109719f8d 0x109701000 + 102285

17 AgKernel

Rikk Flohr_Photography

Community Manager

Engineering has reviewed it and is asking if we can get the plugin/process that is crashing for us to review. Can anyone provide an example for examination?

Rikk Flohr: Adobe Photography Org

johnrellis

Braniac

One of the victims above uses the Commit Locations command (free) of my Any Tag plugin on an Intel Mac, LR 13.5 , Mac OS 14.6.1. Commit Locations runs the Exiftool program.

To hopefully provoke the problem:

1. Enable Address Lookup.

2. In the Map module, select 100 or more photos.

3. Drag them to a new location on the amp.

4. With all the photos selected, do File > Plug-in Extras > Any Tag > Commit Locations.

johnrellis

Braniac

Another report above encounters the problem with the Metadata Wrangler plugin (Friedl) and the Capture Time To Exif plugin (@john beardsworth), both of which also invoke Exiftool.

Since the problem occurs at the very beginning of forking the child process, it probably doesn't depend on the exact parameters for invoking the plugins. It smells like a race condition that's triggered infrequently (e.g. over tens or hundreds of invocations of the plugins, such as export 100 photos or changing the capture time of 100 photos).

A

Addison33594689kznf

New Participant

Thanks - do you have a way to "reset" LR back to default without ANY plugins installed. Or a way to remove every single thing that could be tied back to LrTasks.execute?

I am going to "remove" all of my plugins in the plugin manager and start fresh. But is there anywhere else in the LR settings where I could make a change?

Any other part of the EXPORT process that I can disable to stop this Value 11 crash?

johnrellis

Braniac

[This post contains formatting and embedded images that don't appear in email. View the post in your Web browser.]

@Addison33594689kznf, you described the crashes as occurring during exports, and the crash report shows the crash occurring while LR is trying to execute a child program. So check the settings in the Export window for the presence of a post-processing plugin such as Metadata Wrangler or a post-processing After Export program. In this screenshot, there are two export plugins enabled, LR/Transporter Keyword Export and Metadata Wrangler:

If you see such a plugin, remove it by clicking the "x". Ensure Post-Processing > After Export is set to Do Nothing.

A

Addison33594689kznf

New Participant

Thank you - I'll give this a try. We had already played around with export settings and really thinned it down. I'll see if there is more we can remove. One thing we didn't rry is AFTER EXPORT setting to DO NOTHING. But that would be weird if that solved the problem because the crashing occurs randomly during the export, not at the end....but we'll see!

johnrellis

Braniac

Another example of the same crash during export on an Intel Mac:

https://www.lightroomqueen.com/community/threads/crashes-when-export-just-me.51208/

johnrellis

Braniac

@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.

Crash_report_from_Lightroom.txt

system-info.txt

daners1212

Participating Frequently

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!!

CMass

Community Manager

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

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded