P: Adding to/Creation of a new Target collection takes minutes unless Sync is paused

[wroublin]

Hello everyone.

I've been using LR for a long time, previously on an intel based Windows 10 laptop. It was a bit slow, but usable.

Now I am using m1 macbookair, both MacOS and LR are up to date and the issue persists.

Since couple versions ago - LR is not usable for me. My collection is huge, has photos on several external hard drives, but i mostly use one, with most current shots. Since 3-6 months my LR is UNUSABLE. I push the B key to add image to target collection - nothing happens. I push it again - nothing happens. After couple minutes - some photos appear in the target collection, others don't, because i pushed the button more than once. It's very annoying. Sync activity goes back to some photos on random external hdd (not currently connected) form way back - i haven't done anything with those photos but there are sync errors for some reason, because why not?

Also - i create a collection - and it doesn't appear immediately.I create another one - after 20 minutes LR wakes up, that the collection I want to create has to have a unique name and boom, the firs one I created magically appears. Seriously - my impression is that this has something to do with syncing - as I sync some collections to cloud to be ableto do some additional culling on my mobile while on the go.

I cannot work like this and instead of having a pleasant experience with culling photos - I am very annoyed and I am unable to work like that. What can i do to make it work smooth again?

[dabour]

I thought about the possibility of downgrading to 13.4 or 13.3 to rectify
temporarily. Anyone do that?

-- Dave

Photography
www.dabourphoto.com

[DdeGannes]

@cobalt35446299 , you indicate Mac OS 13.6.9, is there a particular reason you have not updated to Mac OS version 14 ?

[DaMoroshka!]

so start by updating your Mac. Adobe cannot even make sure their soft runs normally on current versions, and you are using Mac OS from a year or two ago - they don't test for it at all.

[DaMoroshka!]

the bug was introduced in 13.3. You'd need to upgrade to some verions prior to 13.3

[DaMoroshka!]

Arjun from Adobe asked me for all sorts of diagnostic files, got them and then disappeared - see posts on page 1 of this thread

[DaMoroshka!]

yours is a different issue. On my Mac, there is no memory leak, memory usage is normal. The lag is only with some specific operations and only happens when cloud sync is active.

[dabour]

Oh great, that's when they upgraded the catalog so to downgrade, we would
probably have to go back to a backup before 13.3 and then lose all the
edits since then?

I'll probably just silently suffer with no syncing until this is resolved 🙏

-- Dave

Photography
www.dabourphoto.com

[arjunhaarith]

Hi @DaMoroshka! ,

We have received the logs from you and are investigating the issue.

We will get back to you

For now, you can remove the config file that we have shared with you and relaunch Lightroom(this will prevent logs being created on your machine). 

Thanks,

Arjun

[cobalt35446299]

Yes there is a reason, although it is unrelated. Is OS 13 no longer supported by Adobe products?

[cobalt35446299]

I downgraded to 13.2 and my issues were solved.

[OHANA Studios]

Same issue here. Sync issues started with 13.3, then 13.4.1 was a bit better. It was slow, but working. There was some memory leak issues I noticed, and a lot of lag when adjusting settings. 13.5 broke sync 100%, and the memory leaks are causing the Mac to run out of both physical and virtual memory - as high as 250GB of usage. I've opened several cases with Adobe, but the resolution was to delete files locally, remove the sync issues from the cloud, then re-import. This isn't a feasable fix when we're importing thousands of photos every single day, and trying to sync them to editing teams. Support has been unable to give a timeline for a bugfix to be impltemented. This is breaking our business workflow. 

[nicolah31659244]

Mine is doing all of this since updating! beyond annoying 

[DaMoroshka!]

as you may see from this thread no version of Mac OS is supported, for there are critical bugs everywhere. However you are more likely to be in luck with current Mac OS, because Adobe don't test for old versions compatibility

[daleducatte]

I was syncing a relatively small number of images (500, across six collections), and noticed the following behavior change between 13.4 and 13.5:

I'd go into one of the synced collections in LrC, where I'd finished editing about half of the 40 images in the collection. The sync icon would be green and I knew edits for those images were uploaded because they were visible on my iPad. I'd begin editing another image, and the sync would start re-syncing 5 to 10 of the images that were previously synced, even though I hadn't made any changes to them.

After this happened a few times, I brought up the Sync Preferences panel and watched Sync Activity -- and every few minutes, sync randomly picked 5 to 10 images from the collection and synced them again. This would happen even if I just stared at the screen and didn't do any editing. When I switched to a different collection, the same thing happened for images in that collection: sync kept picking up images I hadn't edited and synced them repeatedly. 

Every time it did this, Lightroom's memory usage would climb (and keep climbing) and its performance would get worse. I tried turning off sync for all my collections, removing the photos from All Synced Photographs, confirming the images were gone from the cloud and started over again. It took about three hours (which seemed like a long time for 500 images with a fiber internet connection) to sync them anew, so I wonder if it was looping on some of them like I described above. But it didn't help anyway: the same random resyncing of multiple unedited images continued to happen.

These are the same images that I was syncing when I was at 13.4 -- where sync behaved as expected: it would sync a single image when I made edits and finish up with no further syncing until I made additional edits. I have since turned off sync entirely, since whatever it's now doing with 13.5 is so detrimental to LrC's performance. 

[DaMoroshka!]

Thank you for your input, but your case is not exactly same as mine, you'd better start a new thread. All the problems I am reporting here started with 13.3 version - when they made major changes to sync engine. There was no appreciable change in behaviour between 13.4 and 13.5. So your issue that only appeared in 13.5 is something different, even though maybe related. We should not be silent about these issues, otherwise Adobe falls asleep on piles of our subscription money!

[DaMoroshka!]

Lightroom 13.5.1 on Mac OS (all updated) still shows lags and delays with some vital basic operations like applying "auto" tone adjustment, creating albums, exporting pics, etc. WHEN CLOUD SYNC IS WORKING. I started a whole thread on this here https://community.adobe.com/t5/lightroom-classic-discussions/two-minutes-for-item-to-appear-in-colle...

which was "locked" by moderators for some reason (?!?!?), please read it, it describes the issue in detail, and the issue is still there, but mitigated. When before you could wait whole MINUTES before Lightroom performed the requested task, now the delay is down to a few seconds, but still very annoying. Please keep working on it, Adobe guys, and don't shift the bug topics to "discussions" thread - this is lame!

[DaMoroshka!]

I've recently started a new topic discussing issues in the latest bug-fix release 13.5.1 - saying that the bugs were mitigated but not completelly addressed, and my NEW topics was MERGED with OLD LOCKED one discussing same issues in the previuos release 13.5! So now nobody can post (including myself). What is this? Some kind of elaborate torture or trying to cancel users actually ACTIVELY FINDING AND REPORTING BUGS???

This is the merged topic please UNLOCK IT, https://community.adobe.com/t5/lightroom-classic-discussions/two-minutes-for-item-to-appear-in-colle...

[JohanElzenga]

Looks like it already is unlocked, so maybe it got locked by mistake.

[DaMoroshka!]

Tell them to also stop changing the name of the topic "by mistake". It is not "Collections take 2 minutes to appear" - the bug is much more widespread, its a showstopper -  with cloud sync working MANY operations lag, like creating new albums, applying presets, applying auto tone corrections, exporting etc.

[Rikk Flohr: Photography]

@DaMoroshka! 

Please do not tamper with Moderator-entered Text.  We've asked this several times of you. 

The subject line has been changed back to "Two minutes for the item to appear in the Collection list," which is the original complaint in your first post.  Please, do not change it back.  Doing so will risk relocking this thread. You are working with a member of the Lightroom Classic team @arjunhaarith and have provided a diagnostic log. I will follow up with them to see if any additional information is needed of you. Until then, I appreciate your patience. 

[DaMoroshka!]

thank you for chiming in, Rikk, and admitting that the lock was intentional silencing and not by accident.  Here's my side of the argument:

1/ The original title of my thread WAS NOT "Two minutes to appear" but "Lightroom has serious bug and is almost unusable now"  - the "two minutes" text was concocted by moderators who wished to downplay the severity of the bug, which is truly huge and is a showstopper. So it was THEM TAMPERING with my title, not me tampering with their text. I have proven with ample evidence that the current build of Lightroom is affected by a serious showstopper bug and moderators tried to silence and downplay me. This kind of "activity" by Adobe stuff is outrageous and should be stopped and prosecuted.

2/ I am not "working" with Adobe team member @arjunhaarith - the only work I did was provide him with diagnostic logs (doing in fact the job of Adobe QA team while providing for their salary with my subscription money!). After that he stopped responding and never updated me on the progress of fixing the bug. I can see that in the latest bug-fix release they have improved on the lags somewhat but ALL THE LAGs ARE STILL THERE! Only now instead of full MINUTES the lags are measured in several seconds, up to 20-30 seconds, which is still huge and unacceptable. 

3/ If you really want to live up to your name "Rikk Flohr: Photography" you should side with us photographers paying subscription money and not with Adobe staff who is releasing buggy software and silences users who actually work as beta testers to find the bugs! I will be definitely escalating this issue to higher Adobe management and also bring to their attention that instead of fixing the bugs Adobe employees are wasting their time and effort silencing users who are actually reporting on those bugs!

[DaMoroshka!]

I apologize for the harsh tones, but I've been unable to use Lightroom for the last THREE MONTHS at least, due to this bug introduced in 13.3 (it was fine before),  spent countless hours troubleshooting, both on my own and online with Adobe tech support, just to have my topic locked because moderators did not like the truthful title!

[Rikk Flohr: Photography]

I would encourage you to read: https://community.adobe.com/t5/lightroom-classic-discussions/p-fine-tune-the-subject-line-of-your-ad... 

Moderators change subject lines for a reason—to improve your visibility and engage with more Community Professionals. Ultimately, this is to better serve those who may come along and have the same issue as you.  When a subject line is ambiguous, non-specific, emotional, or otherwise detrimental to its being seen by others, a moderator will change it. This is done many times daily with the goal of accuracy, not diminishment. 

Moderator text should never be modified by anyone other than a moderator.  

I've changed the subject line to your original post's first complaint. 

No one is downplaying the severity of your issue, but no bug has yet been confirmed.  I run Lightroom on various Macs with none of these issues you describe. That said, I am assisting in investigating your report and working with the Classic team to collect more information regarding your specific issues. I encourage you to respond to the Classic team's emails and requests for information. 

[DaMoroshka!]

I fail to understand how "2 minutes for item to appear in collection list" can improve visibility and engagement - for starters it is plainly misleading and not relevant to the topic! The bug is not about "vague items not appearing in collection list" - it was NEVER MY ORIGINAL TITLE, the bug is about "MANY mission critical features lag to a degree rendering the app unusable".  So please stop falsely claiming that you "reverted the title to my original complaint" This was just one particular example of the lags, not the crux of the complaint! I cannot regard your insisting on applying misleading irrelevant title to my thread as anything but trying to DECREASE its reach and visibility - nobody having this issue will recognize it and chime in if he sees "items take 2 minutes to appear in collections"! 

If you test for a catalogue with 200+K images you'll get the issue 100% reproducible.

Several users confirmed in this thread they are suffering the same problems even with smaller catalogues.

Also the recent bug-fix release actually IMPROVED on the lags, but did not get rid of them completely. So they WERE doing something about it. 

Finally I fail to see how "moderator text should never be modified" applies to my thread - it was MY TITLE that was modified by moderators and changed into an errelevant BS, not ME modifying moderators' text! 

[Rikk Flohr: Photography]

"If you test for a catalogue with 200+K images you'll get the issue 100% reproducible."

-My catalog is 420K, and I cannot reproduce it. 

You may have several different and highly-likely unrelated issues - which should never be bundled into a single bug report.  I recommend creating a distinct Discussion post for each issue - rather than submitting a laundry list like you've done here. 

It might be helpful to read: https://community.adobe.com/t5/lightroom-ecosystem-cloud-based-discussions/p-do-i-post-in-discussion...

Ultimately, if you use the Community Forums as intended, you will get far better results and timely action.