Lightroom ecosystem (Cloud-based)

I have an update. I don’t know if the behavior I initially described is a bug or not, but it happened again.  it seems like if you long press on a mask while the mask is selected (has blue frame around it) then the menu comes up. But if you long press when the mask is not selected, then the on/off (expected) behavior returns.I’m uploading a screen recording. I’m using a 12.9 inch iPad Pro 5th gen. I’m using iPadOS 27.0.1. 

Description of Issue- While culling, Lightroom reads its preferences through NSUserDefaults ~750 times per second (peaks above 1,800/s), 99% of them on the main thread. Idle, it reads none.- One key dominates: Organize_viewMode is read ~440 times per second (62% of all reads). The 10 most-read names make up 94.5%.- Lua code also assigns preferences ~7 times per second while culling (Organize_lastLocalAssetSelection and Organize_lastLocalActiveAssetSelection on every selection change, AgDevelop_denoiseAmount, lastOzUserId), but almost all assignments store the value already there: only 24 actual writes reached CFPreferences in 207 s. Each assignment still reads the current value first.- 93% of the reads come from two Lua bindings in AgSubstrate that read a preference with no cache: each takes the key from the Lua stack, calls [[NSUserDefaults standardUserDefaults] objectForKey:], converts the value and pushes it back to Lua (AgSubstrate+0x1ab48 and +0x1ade0, arm64). So every preference

Description of Issue- While culling in Detail view with the arrow keys, every photo step starts a Camera Raw task named "find transparent" on 6 worker threads. In three Time Profiler recordings it used 39%, 46% and 54% of all of Lightroom's CPU: more than decoding, demosaicing and rendering the photos put together.- It happens with the Crop tool closed and no editing. In two of the recordings only D and the Left/Right arrow keys were pressed.- It's specific to Detail view: moving through the same photos in Grid view with the same keys runs no check at all, and Lightroom uses 0.18 cores instead of 5.2- It runs for every photo, whatever the camera, lens, file type or crop, and it found nothing: all 79 checks over 55 photos from a Sony A7R III, a Panasonic GH5 and four iPhones (ARW, RW2, HEIC and JPEG; three cropped, one of them also straightened 4.9°) left hasVisibleTransparentAreas false. Each check cost about the same, 1.5–2.2 CPU-seconds, for 12 MP and 42 MP photos alike.- Its result

Description of Issue- Lightroom's live AgTimerMac objects (AgSubstrate) keep accumulating: 226 just after launch, 224,705 after 34 minutes of culling, 950,048 after 8 more days idle in the background. Some are released (44,000 within 2 minutes of leaving Detail view), but far fewer than are created.- Memory grows with them. Left open in the background with no interaction, the same process grew steadily by ~0.25 GB per hour (~6 GB per day) whenever the Mac was awake: 6 GB → 29 GB over 8 days, during 3½ of which the Mac was asleep.- Most of the growth is small allocations made through the Lua VM. The churn also leaves the small-allocation zone heavily fragmented: 20.9 GB dirty against 8.1 GB of live allocations.- For long stretches, the main thread runs a timer loop: an NSTimer fires, calls into Lua (AgSubstrate → lua_pcall), and the callback invalidates and re-creates a run-loop timer (CFRunLoopTimerInvalidate → __CFArmNextTimerInMode), ~6,400 times per second at a flat rate, independen

Description of Issue- At every launch, the Objective-C runtime warns that several classes are implemented in two of Lightroom's bundled frameworks. Apple documents this as able to "cause spurious casting failures and mysterious crashes".- The app bundle also contains a second, complete copy of WichitaFoundation (19 MB) inside AgUI.framework that is never loaded, and a category (NSException(ToString)) defined in both AgKernel and AgSubstrate, where which implementation wins is undefined and the runtime doesn't warn. Step-by-step Reproduction Instructions1. Launch Lightroom.2. Open the first lines of:   ~/Library/Containers/com.adobe.mas.lightroomCC/Data/Library/Application Support/Adobe/Lightroom CC/lrcc_console.log3. Optional, without launching Lightroom (Xcode command line tools): list the Objective-C classes each framework defines and compare, e.g.   cd "/Applications/Adobe Lightroom.app/Contents/Frameworks"   xcrun dyld_info -arch arm64 -objc WichitaFoundation.agtoolkit/Versions/A/W

Description of Issue- The bundled analytics SDKs (dunamis, GrowthSDK) write constant trace-level chatter to disk, never clean up their logs, and repeat the same identity error indefinitely- Even with "Share usage information" turned off, they keep uploading events that carry the device ID and the user ID Step-by-step Reproduction Instructions1. In Lightroom, make sure Preferences → General → Privacy → "Share usage information" is off. Check it:   defaults read ~/Library/Containers/com.adobe.mas.lightroomCC/Data/Library/Preferences/com.adobe.mas.lightroomCC MetricsParticipationChoice   (prints opt-out)2. Quit and relaunch Lightroom, then leave it idle for 10 minutes3. In Terminal, look at the newest dunamis log (one file per launch):   cd ~/Library/Containers/com.adobe.mas.lightroomCC/Data/Library/Logs/Adobe/com.adobe.dunamis   F=$(ls -t dunamis-*.log | head -1)   wc -l "$F"; sleep 60; wc -l "$F"                                    # lines per minute   grep -c "AEPErrorCode" "$F"        

I'm experiencing unacceptable performance with Lightroom (cloud version) on my MacBook Pro M4 Max with 36 GB RAM.Lightroom consumes around 20 GB of RAM while editing just 8 photos, causing severe lag. My Mac handles demanding 8K video editing in Premiere Pro and After Effects, yet Lightroom struggles with basic photo editing.This suggests serious memory management or optimisation issues. There is also no straightforward way to clear unused RAM without restarting the application.I pay approximately AUD $130/month for Adobe software and expect professional performance.I want this issue investigated and escalated to the technical team, with a proper solution rather than generic troubleshooting advice.

I am attempting to log in to my Adobe Lightroom account using the Lightroom Mobile application on an iPhone with iOS 27.0.1.I launch the app, I see the 4 login choices and choose the Continue with email option.I am given a page (auth.services.adobe.com) which prompts me to log in with my email address.  I enter my Adobe account email address and the page fails at this point.  I am unable to select the Continue button nor am I able to edit the email address.  I can refresh the page but cannot progress through the continue button.I know my account is active as I can log in to lightroom.adobe.com on my laptop’s browser and I can log in using my Lightroom Classic application on my Mac.Edit to add:I have reinstalled the application, refreshed network settings, force closed the app, and none of these steps have remediated the issue.