Two minutes for item to appear in Collection list

[DaMoroshka!]

Thas all started when they changed the sync mechanism (13.3 I think) , and has been living hell since then. I try to create new collection - have to wait 2 minutes for it to appear in the list. I hit B to add a picture to current target collection - have to wait 2 minutes for it to register in the collection. Apply Portrait effect (auto masking) - have to wait 2 minutes for it to appear. The bug is intermittent - sometimes all works fine (rare occasions) - and the AI masks themselve take only 1-2 sec to calculate on my M2 MaX Macbook Pro.  But when it lags, oh boy!  the lags and freezes are unbearable, they happen with many library operations, especially related to collections creations, adding pics to collections and enabling/disabling cloud sync for a given collection - that all makes Lightroom barely usable. 
the lags are all tied to the cloud sync operation - when there are images in the sync queue many operations lag unbearably, including quitting the app. 

P.S. whats with the "topics" that this forum suggest to select "to help users find my post" and selection is FROM THREE topics - macOS, Windows and SDK! WHere are other topics???

[_oh_yeah]

Same for me, since 13.5, uses all the available memory (64 Go !) and the the computer is unusable. Same issue on 2 computers. Have you tried to come back to an older version ?

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

[DaMoroshka!]

Bugs from 13.3.1 persist - enormous lag creating new albums and collections and populating them, e.g. you press B to add to collection and wait several minutes before the image actually registers there.

New bugs added - now with many iphone apple raw .dng pics I open the pic after import in Loupe view mode - it shows built-in preview (LR previews not generated) - I switch to Develop - full size preview generated and shown as usual - I switch back to Loupe - and IT ONLY SHOWS built-in preview! 

It gets worse - previews get stuck and even if I choose generate full size preview - nothing changes, and after a couple of minutes I get message that Preview has been generated!

Adobe - start testing your software on large libraries - mine contains 200,000+ images and releases before 13.3 worked fine - after 13.3 I am having nothing but issues!

[JohanElzenga]

Always give your hardware specs and your MacOS version, otherwise Adobe engineers can't do nothing with your report. I have a 200,000 images catalog too on my MacBook Pro 16" M1 Max 32GB running MacOS 14.5 and I do not see any of the issues you have. When I press B, the image is reported to have been added to the quick collection in about one second, for example.

[DaMoroshka!]

M2Max Macbook Pro 16", latest Mac OS all updated. For me the trouble started with 13.3 upgrade. That's when they changed the sync engine and thats also when I had multiple issues with lag in various library related operations, like new album creation, adding pics to collection, etc. I have a thread here about it with some guys reporting the same kind of buggy behavior. 

[DdeGannes]

@DaMoroshka! , unfortunately the update to LrC 13.4 did not address any of the " Sync to Adobe Creative Cloud " issues which the updates of LrC 13.3 / 13.3.1 created.
Those issues are still being addressed by Adobe, hopefully these issues will get rectified soon.

[Danilo3125234585jb]

Also here lag in the develop module only go through the photos: it's not usable at all. I'm on Windows 11 Pro 23H2 22631.3810, AMD Ryzen 7 3700X 8-Core Processor, 32,0 GB RAM, NVIDIA GeForce GTX 1650 (Driver already updated). 

[Bergischer Löwe]

Unfortunately, I have to completely agree with "DaMoroshka!" For me too, LRC13.4 is a disaster !

I use a catalog with 170,000 photos (approx. 60% RAW (Nikon/Fuji and 40% JPEG or PSD files) distributed across 3 main directories or 3 hard drives

Base is a PC with Windows 11 Pro (Version 23H2, Build 22631.3737)
- with Mainboard Typ Gigabyte Z790 Gaming X AX
- Intel Core i9-13900K
- 32 GB RAM
- graphic card NVIDEA GeForce RTX 4060 with NVIDIA Studio-Driver 555.99

Only if I deactivate Address Lookup, Face Detection and Saving XMP as well as turn off "Replace embedded previews with standard previews during idle time" and I also deactivate the graphics card can I minimize the number of crashes.

I don't think anyone at Adobe has ever tested LRC 13.4 with a really large number of photo files.

[JohanElzenga]

A catalog with 170,000 images is not that big. I am sure several beta testers will have such a catalog or a much bigger one. A really big catalog is one million images or more. I know this won't be any consolation, but the problem with beta testing is that you cannot possibly test all the possible hardware configurations that are used in the world, especially on Windows. There will always be configurations out there that don't run well with the latest Lightroom version. That is inevitable and obviously Adobe should (and will) look into it. Also remember that people who do not have any problems with this version of Lightroom Classic will not come to this forum to report that. This version does have its problems for some people, and does not have any problems for other people, like all other versions did. I do not have the impression that this version is worse that any previous versions in that respect. I hope Adobe can solve this soon.

[Ganji12]

Same problem with small catalogue... It's a core problem they need to fix it, as a professional i cant work like that anymore

[DdeGannes]

@Ganji12 , @Bergischer Löwe , @Danilo3125234585jb ,

I posted a reply to the original author of the thread who raised issues with LrC 13.4 which relates mainly with Sync Issues that originated with LrC  13.3 and 13.3.1.
These issues have not been addressed in the LrC 13.4 upgrade if you look at the thread at the top of the forum anouncing the release of this update the info and details there do not indicate there are fixes for the issues you continue to raise.

Adobe is aware of the issues and hopefully a fix will be forthcomming in the near future.

[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 

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