Lightroom ecosystem (Cloud-based)

A couple years ago August 2024 the AI removal tool could remove people from the background and replace with what was around them. Today I am trying the tool and it won’t remove the person. It makes a new face or head. And then it won’t use the background of the surrounding area it takes from other parts of the photo that don’t make sense so it looks worse (like instead of the nearby wall it used my outfit and put that Where a wall should be, above me in the pic) 

Description of Issue- When culling in Detail view, moving to the next photo makes Lightroom download that photo's full original raw (~59 MB for a Canon R5 II CR3) from the cloud, even though a local smart preview (2560 px proxy) exists for every photo (all proxies are stored locally) and Detail view is at fit-to-screen.- Culling a large shoot therefore downloads hundreds of GB. macOS flagged Lightroom for writing 137 GB in 13 minutes (173 MB/s) during one culling session.- The writer is the libcurl write callback inside WichitaFoundation: the heaviest stack in the macOS disk-write reports ends in WichitaFoundation → fwrite. That function multiplies size × nmemb and only writes when the HTTP status is below 400, and WichitaFoundation contains a statically linked libcurl (CURLOPT_* and Content-Range strings). Step-by-step Reproduction Instructions1. Use a cloud library where originals are not all stored locally (Preferences → Local Storage: "Store a copy of all originals" off) but all sm

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.

Lightroom Classic wont open. Says application not responding. I uninstalled and reinstalled. Still doesn't open.

Classic will not open