• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Crashes when a Plug-in uses LrTasks.execute

New Here ,
Sep 06, 2024 Sep 06, 2024

Copy link to clipboard

Copied

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.

TOPICS
macOS , SDK

Views

240

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Sep 06, 2024 Sep 06, 2024

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 15, 2024 Sep 15, 2024

Copy link to clipboard

Copied

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Oct 05, 2024 Oct 05, 2024

Copy link to clipboard

Copied

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"

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Oct 05, 2024 Oct 05, 2024

Copy link to clipboard

Copied

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

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Oct 06, 2024 Oct 06, 2024

Copy link to clipboard

Copied

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

Rikk Flohr - Customer Advocacy: Adobe Photography Products

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 07, 2024 Oct 07, 2024

Copy link to clipboard

Copied

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:

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 07, 2024 Oct 07, 2024

Copy link to clipboard

Copied

LATEST

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.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines