Skip to main content
Participant
September 6, 2024

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

  • September 6, 2024
  • 12 replies
  • 6859 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.

12 replies

johnrellis
Legend
October 5, 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"

johnrellis
Legend
October 5, 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.

Rikk Flohr_Photography
Community Manager
Community Manager
October 6, 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
johnrellis
Legend
September 6, 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.

Participant
September 16, 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.

johnrellis
Legend
October 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?