Bug Reports

I've been subscribed for over 2 years now and have never been able to make use of Lightroom Classic. Every time I try to import more than a handful of folders worth of photos it just freezes up. I have tens of thousands of images from over the years but the most I've ever been able to import has been perhaps a thousand before it just freezes, and even then it takes up to an hour just to import a couple hundred. I'm using the add option so I don't know if that makes a difference. I've tried uninstalling and reinstalling - more than once - before anyone asks.   This has happened on 2 different laptops by the way - I expected it with my old one as it didn't have enough RAM, but I kept lightroom in mind while buying my new laptop. Despite that it's still unusable for my needs...or anything to be perfectly honest. It also freezes every time I try to use to stitch panoramas. I'm doing them in photoshop now, but from the few times Lightroom hasn't crashed I know it's better for this than

When using the straighten tool on an image, clicking and dragging does not show the straighten line when in Soft Proofing mode. This is happening in Lightroom 10.3, on macOS Big Sur. 

Hi Adobe I had a long support session with you today. A short command \ (backslash) is not working on Swedish keyboard. The command triggers zoom instead. I could with Alt+Shift change the keyboard setup in Microsoft only to try and the \ worked fine.

Windows 10 Pro, Lightroom 8.3.1I have been tagging faces and noticed after a while that LR has slower and slower redraws and general GUI response. Looking in the task manager, I see 1800 or so GDI handles in use. At start-up it is more like 670 handles.After some playing around while watching the task manager, I blame the Navigator window. If I just mouse-over a dozen or so folder names, the Navigator window shows the first photo in each folder, and the GDI handle count jumps up by dozens. It is the same set of photos each time, so it isn't about caching of bitmaps, I don't think.There may well be other handle leaks, but this is the most obvious one.My system has 128GB of memory. In the Old Days of Windows, leaking a few hundred handles basically killed Windows. More recent versions claim to let you waste handles recklessly, but the truth is that programs get unacceptably slow pretty quickly if they leak. For now the work-around is to close and re-open Lightroom. But you want to m

Dear developers,   PLEASE make a troubleshooting article in the official support articles for Lightroom Classic, for the startup crashing problem appearing constantly.    The Lightroom Classic starts, it shows the pictures from the library, then it pops up the error reporting window - 0xc0000005 error.    I faced this already 4 times during a short time period of 3 months.    Everytime I did more hours of troubleshooting and googling what can cause this problem.  I started with GPU drivers, update, rollback, delete, clean, install. No result. Then I went for Windows updates, installing the latest updates, then uninstall up to the last day, when LR CC worked. No result.  Then I did   sfc /scannow system integrity check, it did not find any problems.    At the end I found out, that:  The ADOBE CREATIVE CLOUD app is the reason. It is constantly getting corrupted. Even it is corrupted, the app runs, does n

I have an issue with LR using almost all GPU memory, impacting Photoshop performance. Once I switch to LR Developer module, VRAM usage goes through the roof and the PS interface becomes sluggish. For instance, opening a new document in PS is slow - and the new empty document will shortly show a part of the photograph I've opened previously. Zooming is slow and opening a filter like NIK becomes extremely slow. During the slow performance PS is even briefly showing status 'Is not responding' in the process list.   LR and PS constantly up to data via Creative Cloud. Windows 10 up to date, use constantly latest NVIDIA Studio drivers and have no errors or messages in event logs. No other issues. Screenshot of VRAM usage:     LR uses 22GB of the GPU memory. This amount seems rather unnecessary: LR performed about the same with my previous 8GB graphics card (of which LR used about 7GB, of course, and impacted PS performance the same way):      By closing LR, af

When attempting to export pictures to an HD slideshow video, I noticed that it completely fails to even begin the export at either 720 or 1080.  I am able to export at the lower quality settings, but the pictures are completely blurry.  I read a post that having portrait oriented pictures in your slideshow is causing the problem.  Sure enough, I create a slideshow 720 or 1080 video with only landscape photos and the export works fine.  I then try to create a slideshow 720 or 1080 video with nothing but portrait, and it hangs.  It did this is the version prior as well, as I was hoping the update would fix this.Here are my System Settings:Lightroom version: CC 2015.6.1 [ 1083169 ]License: Creative CloudOperating system: Mac OS 10Version: 10.11 [6]Application architecture: x64Logical processor count: 4Processor speed: 3.1 GHzBuilt-in memory: 16,384.0 MBReal memory available to Lightroom: 16,384.0 MBReal memory used by Lightroom: 2,202.4 MB (13.4%)Virtual memory us

So I am using the brush tool on some of my photos and after that I decided to use the spot removal tool. Upon doing so it removed more than the spot. It actually ended up removing separate brush strokes I have made. I am not sure how this is possible but please look into this. 

1. Editing an image 2. Create a virtual copy 3. Crop the copy 4. Adding a spot removal to the original 5. Synching spot removal from original to copy 6. Interrogate spot removal   Expected - spot removal over the same part of the image and sampling from the same part Actual - spot removal does not always sample exactly from the same place This is an example in which the shift is very slight, sometimes the sampling area completety change!   Bokeh ball removed by sampling just from next to it...   Image 1 (original)     Image2 (virtual copy of the original on which I use the spot removal)     Image3 (a cropped virtual copy of image1 to which I synch the spot removal tool from image2 - see the shift on the right)    

Today I found a new problem.After connecting my new iPhone 11 Pro with the iMac (Catalina) in order to import photos using LR Classic the application closed suddenly.After reopen LR I tried again and the message was "no photos found" !Using a SD card nothing happens but with the Iphone (iOS 13.2) LR close suddenly !Note: This conversation was created from a reply on: Lightroom Classic: Fails to import photos and stalls out on macOS 10.15 Catalina.

The Collections I'm syncing from Lightroom on the desktop are all sorted via User Order. When a Collection is synced to my phone the order is all over the place. Custom on the phone is apparently not the same as User Order. How do I get the custom order I've made on the desktop to sync and be the same on the mobile app?

Only half the width of the keywordlist is used to display the keyword. I use a hierarchical keyword list and at lower level keywordnames are cut off. Instead of for example "Flower" it is displaying "Flo...". I understand that if there is no room left, it has to cut of the name, but in my case still al lot of space is available. If i look at images of keyword lists others post, it seems that a lot more space is used to display the names. If i resize the width of the panel, i can see more of the keyword. At the smallest width only half the width is used for the keyword name and the other half is used for the count, which need in my case much less room than the name

LrC 10.2, macOS Big Sur 11.2.3 on iMac Pro w/ 64 GB memory and Radeon Pro Vega 64 16 GB.   After Import, and only after Import, access to the Map module, either via the pin on an image or directly to the tab, results in LrC instantly blowing out and presenting Adobe and Apple crash report dialogs. After recommendation of another Adobe forum's administrator to reset preferences and reboot, problem still exists.   Many crash reports submitted and should be available for analysis.

In a recent update, Adobe seemed to change the fonts in Lightroom Classic CC.  Now the font's when viewed (here in the keyword screen) don't appear to be aligned.  In this case, all of the fruits are listed under the keyword 'fruit', but they don't appear to be aligned or nested properly due to the font.  Same with food types, Chinese Food and Chestnuts aren't and shouldn't appear nested under Candy, but that's how they appear with the new font changes.       Here's another example: Photos to import is not under Pets, but appears to be due to the new font alignment or misalignment...    

LrC 10.2 is consuming memory at an alarming rate when Tethered Live Shooting is activated for Nikon cameras on Windows 10. It looks very much like a memory leak of huge proportions.   This problem is considerably worse for some Nikon DSLR camera models than others. Initially @Steve Martin reported this problem with his newly purchased Nikon D7500.   I tested with my Nikon D750, and although there was evidence of a slow memory leak, I couldn't reproduce the severe memory leak Steve was seeing on his computer.   After trying everything from resetting preferences to reinstalling LrC and trying on a different computer, Steve tried a Nikon D90 and found it was worse than the D7500.   I have a Nikon D90 which I could use to do testing and can confirm his problem on my own Windows 10 PC computer. Starting LrC 10.2 in Library Grid view with an empty folder selected, LrC soon settled into an idle state using the small amount of memory shown in the screen shot below taken aft

When converting a raw DNG file to a lossy DNG file from within Lightroom Classic, the setting "File Extension" is ignored. This setting determines whether the resulting file extension will be DNG (upper case) or lower case (dng).     With other types of raw files, it works ok. But with raw DNGs, the resulting lossy DNG file keeps the same case from the original file.   The only way to make it honor the File Extension setting is to uncheck the box "Delete originals after successful conversion". In this case, the correct case is applied, albeit the resulting file is altered ("-2" is added), and of course, one has to go and manually delete the originals if they are no longer needed. So it's just a workaround for a feature which I think is not working as designed in this specific situation.   In this video the problem is demonstrated (you have to pay attention to the "Filename" field in the Metadata panel after each conversion:   https://youtu.be/gM6LgxUJ4uM &nbsp

When choosing Crop tool there is a padlock symbol that shows whether aspect ratio is locked or not. When making the first attempt to crop any particular image the padlock symbol incorrectly shows as unlocked when the tool is behaving as locked.   This only seems to happen on the first attempt to crop a new image.  Whilst the symbol incorrectly shows as unlocked (even though aspect ratio is locked), just passing the mouse pointer over the padlock (no click required)  changes the padlock to correctly show as locked. Whilst incorrectly showing as unlocked (even though aspect ratio is locked), pressing the shortcut key A has no effect on the padlock symbol but does change the aspect lock to unlocked (so now the symbol and the behaviour matches). Subsequent use of the shortcut A makes padlock symbol behave correctly for that image. Once the initial incorrect view has been corrected (by one of the above methods), all subsequent behaviour on the same image seems correct. Open a

Me: Any clue why my newly built Lightroom preset - that has color grading selected when created - doesn’t actually apply color grading to images when selected? My color grading only presets work just fine, but not ISO adaptive ones. Adobe, fix this please.    From AdobeCare: Hi Dave, thanks for the heads up. Has this preset ever worked since you created it? Would you mind reviewing the process of creating an ISO adaptive preset in Lightroom Classic and see if that helps? See: helpx.adobe.com/lightroom-clas… Thanks, ^AK   Me: Thanks - this is a new one, so never worked. I have several other ISO adaptive presets (made before Color Grading) and they all still work fine (but with no color grading). I was finally getting around to making one with Color Grading included. I do have Color Grading only presets that work (not adaptive). Reviewing now   Me: Reviewed, that’s exactly what I did. Images from ISO 320/800/1600/3200/6400, checked that the only differe

Hi everyone,   I've just noticed odd behaviour after recent LR update on my Win10 64bit - I'm processing photos from 1 photoshoot, using nikon d700 and 50mm lens for all of them.   As conditions are the same, my workflow is to apply settings to first photo and then sync across rest of them so if I'm selecting multiple images and then sync settings either from Library or Develop module - that's great, working fine and as expected.   However, sometimes I'm doing manual tweaks and then I want to apply those settings to the next photo so what I'm doing is: in Develop mode, go to the next image and hit "Previous" button next to "Reset" - when this is used the image is getting marginally cropped (probably by 1pixel) even when previous image wasn't cropped at all.   This change is only marginal but alters the aspect ratio without user's knowledge and only indication is a small crop icon in the filmstrip thumbnail.   Thank youMarcin

Long term Lr6/LrC user. First time creating a slide show.   Added photos, mix of portrait and and landscape, into a custom template that shows the Title and Caption. Previewing works fine.   I added a music clip; LrC 9.4 froze  then the crash screen came up.   I've Googled this issue and it seems to be old. Any idea when it will be fixed?   Thanks

Hi, after updating to Lr classic 10.2 metadata like capture time, exposure, filename etc is not updating nor showing after I make a change from the list with right click just above or under the thumbnails in the grid view. Win 10, AMD Ryzen 9 3900X 12-Core, 64GB, x570 MB.

When I right click on the righthand third of an image, the background colour contextual menu comes up instead of the more general purpose Lightroom one that includes settings, export and edit in and such like. The mapping of where the image is on the screen seems out. If I right click to the left of the image on the background area it still behaves as if I've clicked on the image, i.e. I don't get the background contextual menu   Ive got right click on the rocker of the wacom pen, if I am viewing the image zoomed in the problem stops. Didn't notice this issue in previous Lightroom version.   Wacom driver 6.3.42-2, (screen area full, tablet are full, no to force proportions in wacom driver)  Windows Ink is turned on.   Lightroom Classic version: 10.1.1 [ 202101041610-8c69aa4e ]License: Creative CloudLanguage setting: enOperating system: Windows 10 - Business EditionVersion: 10.0.19042Application architecture: x64System architecture: x64Logical processor count: 32Proc

lightroom classic cc 8.2 (build 1204643) on windows 101) enable color label toolbar both in grid and loupe view.2) choose a folder with multiple photos3) from grid view add a color label to a photo4) press enter (or E or double click) on the labelled filein loupe view the previously labelled file has no label selected5) still in loupe view, press arrow right to select the next file and then the arrow left to return to the previous filethe labelled file now is shown labelled in luope view too6) press G to return to grid view7) remove the color label😎 press enter (or E or double click) on this filein loupe view the file is still shown as labelled9) press arrow right/left (one or more times)all the pictures are shown as labelled (even if they are not)

Win 10 1803, LR  8.0, I7 8700k, 64GB ram Control keys inop. Most functions in Edit, Image, Layer, Select anf Filter grayed out. Images opened directly into PS all ok. Reset prefs no help.

The problem is created when syncing the pictures from Lr Classig to Lr Mobile. During that process they will get an "upload time / create time", but as Lr mobile sort them according to the capture date you will not see this problem until you create a web gallery. There they are presented in the same order as they were uploaded to Lr Mobile!   The work around is to update the sort order in the web gallery to capture date.    As soon as the support representative and I understood the reason for the problem she said that this will be corrected soon!.   This item is reported as Adobe Case ADB-19651987-L9V5