P: Unresponsive after Eject SD Card/USB Drive

[drtonyb]

This is a reproducible crash that I have found in Lightroom Classic 7.3 running on a Windows 7 Pro 64bit OS Toshiba laptop fitted with a built-in SD card reader.

Follow these steps to reproduce:

1. Launch Lightroom Classic 7.3 and ensure that Auto Import is disabled and the Preference 'Show import dialog when a memory card is detected' is unchecked.

2. Insert an SD memory card. Close the Auto Play dialog if it is displayed.

3. Use the Safely Remove Hardware icon in the system tray to Eject SD Card. An error dialog is displayed stating that 'This device is currently in use...' Click OK to close the dialog.

4. Open Windows File Explorer, click on Computer to show Devices with removable Storage. Right-click on the SD card icon and select Eject from the pop-up context menu. An error dialog is displayed stating that the drive 'is in use' and to 'Save any open files on this disc...' In this dialog you have three choices: Cancel, Try Again or Continue. The dialog states 'If you choose to continue, the files will be closed, which might cause data to be lost.' Click the Continue button and the SD card is ejected.

5. Lightroom has how crashed with the busy cursor whirling away and (Not Responding) displayed in the title bar. Lightroom must now be forced to close.

Following these steps while Lightroom CC version 6 is running does not crash LR6.

So, why is LR7 opening files on an inserted SD card? There is no reason for LR7 to be accessing the SD card at all at this stage and it certainly shouldn't crash when the SD card is ejected.

Would other LR Classic 7.3 users try this too and report the result?

I would like a proper response from the Adobe team on this and by this, I mean someone who actually has the authority to do something about it. If I don't, I will assume that the development or management team are not interested in fixing the problems that infest this version of Lightroom.

[Sunil_Bhaskaran]

Thanks for letting us know.
We are aware of this issue and a fix is underway.

Thanks,
Sunil

[FeedbackCommunityMember]

All of a sudden, Lightroom 4.4 is not ejecting cards after import. I used three different card readers, and the problem persists. Also, my cards are not showing up under the "Devices" tab in the import dialog; they show up at the bottom of the "Files" tab, which has never happened before.

[Rikk Flohr: Photography]

Lightroom 7.3.1 was released earlier today. After installing it, please let us know if you continue to see the crash on ejecting the card. 

[drtonyb]

Thanks Sunil for the Official Response, I won't be holding my breath for a fix.

Rikk, I have just updated to 7.3.1, restarted my computer and tested the SD Eject problem that I reported. As expected, no change. Still crashes same as 7.3. Since it is not listed as a fix in the release notes, I didn't expect that the bug would magically disappear.

It is just beyond my comprehension why Adobe is taking so very long to find and fix bugs that are being reported to them. As a web developer myself, I write a lot of code in javascript and php. I too make mistakes and sometimes introduce bugs in my code. When I discover a bug in my testing or a client reports a problem, I find it very quickly and resolve the issue immediately. I don't ignore it for days, weeks or years and I don't have a team of developers - it's just me.

Adobe needs to stop and devote all its development resources to fixing the serious problems with Lightroom Classic now, not later.

I love using Lightroom and have done so since Version 1. Like other LR customers, I just want it to work properly, fast, efficient and without crashing. I also want Adobe to really listen to its customers and take on board some of the excellent ideas that are posted on this forum. Unfortunately, Adobe doesn't have a very good track record of listening to its customers - Lightroom isn't the only Adobe product where customer concerns are largely ignored. I once use Business Catalyst for web development and after reporting some bugs, I discovered these same bugs had been reported before and fixes for them had been outstanding for years. I don't use or want to use Business Catalyst any more.

[Nature Light]

Due to number of photos I have to use 2 external and 1 internal hard drive.  While working in LR latest version 7.3, if I turn off one of the externals LR immediately freezes displaying the revolving blue circle.  I can move this cursor around and the computer otherwise is not frozen but LR is dead.  The only way to resume work is to use task manager to end task for LR and then restart LR.  It then works fine.  If I then turn the external on, all is well but once again, turning it off causes a freeze.  It is not a hard drive problem because the same thing happens with either of the two drives.  It seems worse recently so I tried roll back to version 7.2 and the same thing happens.  Can anybody offer any insight as to whether a Windows 10 issue, a computer hardware or software issue, or while unlikely, a hard drive issue?

[Nature Light]

Will update 7.3.1 address this hard drive issue as well?

[Rikk Flohr: Photography]

John, 

This issue is still open and in-process. See Sunil's comments at the top. 

[Nature Light]

I assumed since your comment was after his that the fix was done with 7.3.1 and not still underway.  So I'll just wait for a further update I guess.  Thanks for the super fast response!!

[halimab9816848]

My system has been running beautifully until I updated My Lightroom Classic CC 7.3 via Adobe Creative Cloud and now my Lightroom crashes constantly. The screen greys out and "Not Responding" displays in the title bar. I have to Ctrl+Alt+Del to exit

[Laura Shoe]

I have a similar issue - if I try to eject my external drive that LR references, I get a message that it can't be ejected because an app is using it. I have to close LR first. 

[Nature Light]

Bug fix 7.3.1 is not the answer.  Working in LR this morning.  Had to plug in a thumb drive to copy some Powerpoint files to laptop for teaching a class tomorrow.  Used Windows Explorer to copy 3 files to the thumbdrive.  After removing the thumb drive and loading files onto laptop, returned to LR to resume work and it is once again frozen.  No message other than at the top "not responding",  a totally grayed out screen.  Back to the drawing board Adobe.  I'll try to attach screenshot.

[rpengale]

I also have this problem and feel my privacy has been violated. Plugged in a USB thumbdrive while Lightroom happened to be running. When I attempted to disconnect the device Windows told me the device is currently in use. Closing Lightroom allowed me to properly detach the drive.

WHY IS LIGHTROOM SEARCHING THROUGH MY PRIVATE FILES? Isn't this a criminal offense? Adobe is apparently attacking my system and is clearly interfering with my use of it.

This is not a trivial mistake. Lightroom is not assigned to automatically detect mounted media, and it is not assigned or permitted to browse my system looking for files it deems interesting.

I like you, Adobe, and I have been trying to forgive your many recent blunders, but I do not enjoy being hacked.

[PhotoDB]

Experiencing the same problem on my desktop.  Having to crash Lightroom with the Red X after each session is getting to be annoying. Godspeed on the solution/fix.

[jmr_photo]

I'm a paid LR/PS subscriber and updated the software yesterday after it kept on crashing after every import and during the import process itself. I've restarted the PC several times, it opens up and then it freezes again.  Crashing continues and Adobe says I'm using LR and PS in trial mode. Very dissapointed!

[FeedbackCommunityMember]

I am having the problem as well, evidently after updating to Classic CC 7.3 and then 7.3.1.  I shoot with both SD and CF cards, and the problem exists with both, using a Delkin Devices card reader.  If I leave the card in the reader, there is no problem, but if I remove it (after "card ejected after import" is displayed), LR freezes with a spinning blue circle and I have to X-out of it and restart.  The import is intact, and I can proceed, but it is annoying.  I tried to manually eject the card but Windows told me it was in use, but I could click "continue" to force it.  So I clicked "continue," and LR froze right after the first mouse click.  I think what is happening is that LR thinks it has ejected the card, but it has not.  The light on the Delkin reader stays on, suggesting the application is still using it.  

[uk_malcolm]

Mine is just the same, it was fine until the update prior to 7.3.1 but it is becoming a pain in the proverbial to have to keep forcing Lightroom to close after each card's import, I have a compact flash card in one camera and an SD card in the other, it happens with both cards.

[FeedbackCommunityMember]

PC users, do not despair. Macs have exactly the same problem.

[uk_malcolm]

Then Adobe should get their backsides into gear and SORT IT 🙂

[FeedbackCommunityMember]

I connect my camera to the computer via USB cable, import my pictures through LR & add them to the computer hard drive. After the import, LR "ejects" the card. If, after that (files are already copied to hard drive) I turn off my camera, LR hangs.

I just had an online session with your support and they re-installed the software, but it had the same result.

[JLCKJC2015]

I am having the same identical problem described by Anthony Blackett who initiated this thread with LR CC 7.3.1 running on the Win 7 Professional, 64 bit OS. It happens with CF and SD cards,  and USB sticks. Just replicated the problem a few minutes ago. I hope these instabilities are resolved soon as my confidence LR won't lose my work has been shaken.

[uk_malcolm]

ADMIN/MODERATORS, are we any closer to a fix for this please? 3 weeks ago you said you were aware of this and a fix was on the way.
Can we have a progress report please?

[Prabal Ghosh]

Hi,

This should get fixed in upcoming release.

[FeedbackCommunityMember]

The question is: when?

[FeedbackCommunityMember]

when memory card is removed or files on card deleted. win 10

[uk_malcolm]

One week on, are we any nearer to seeing a fix for this please Admin/Moderators?