Lightroom Classic 7.3: "Not Responding" Constantly

  • 5
  • Problem
  • Updated 1 month ago
  • (Edited)
I use Lightroom Classic CC on a powerful iMac with 32GB memory and tons of available disk space available.  Ever since about maybe three weeks ago LR started to go into "Not Responding" status after it sits unused for a while.

It's just fine as I am using it.  And it's just fine if I let it sit unused for a couple hours and come back to it.  But if I wait too long between sessions, or if it's open overnight before I use it again the next morning,  it goes into "Not Responding."  If I manage to get into LR after clicking the icon in the dock, I can click something about every 30 seconds, and between clicks I get the color wheel. The only way out of this is exit the app.

I have read elsewhere it could be due to lack of free space. This is not the case here.  Also, I heard that it could help if I uncheck "Use Graphics Processor" in preferences.  This does not help.

It's pretty frustrating. Does anyone have any suggestions?

Here's my system info:

Lightroom Classic version: 7.3 [ 1164630 ]License: Creative Cloud
Language setting: en-US
Operating system: Mac OS 10
Version: 10.13.4 [17E199]
Application architecture: x64
Logical processor count: 8
Processor speed: 4.0 GHz
Built-in memory: 32,768.0 MB
Real memory available to Lightroom: 32,768.0 MB
Real memory used by Lightroom: 2,476.9 MB (7.5%)
Virtual memory used by Lightroom: 6,765.6 MB
Memory cache size: 27.3MB
Internal Camera Raw revision: 933
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 821MB / 16383MB (5%)
Camera Raw real memory: 832MB / 32768MB (2%)
Displays: 1) 5120x2880

Graphics Processor Info: 
Metal: AMD Radeon R9 M395



Application folder: /Applications/Adobe Lightroom Classic CC
Library Path: /Users/mark/Dropbox/Lightroom/Lightroom Catalog-2.lrcat
Settings Folder: /Users/mark/Library/Application Support/Adobe/Lightroom

Installed Plugins: 
1) AdobeStock
2) Aperture/iPhoto Importer Plug-in
3) Canon Tether Plugin
4) Facebook
5) Flickr
6) HDR Efex Pro 2
7) Luminar
8) Luminar 2018
9) Nikon Tether Plugin

Config.lua flags: None

AudioDeviceIOBlockSize: 512
AudioDeviceName: Built-in Output
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: 10.0x7
CoreImage: true
GL_ACCUM_ALPHA_BITS: 0
GL_ACCUM_BLUE_BITS: 0
GL_ACCUM_GREEN_BITS: 0
GL_ACCUM_RED_BITS: 0
GL_ALPHA_BITS: 8
GL_BLUE_BITS: 8
GL_DEPTH_BITS: 24
GL_GREEN_BITS: 8
GL_MAX_3D_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_SIZE: 16384
GL_MAX_TEXTURE_UNITS: 8
GL_MAX_VIEWPORT_DIMS: 16384,16384
GL_RED_BITS: 8
GL_RENDERER: AMD Radeon R9 M395 OpenGL Engine
GL_SHADING_LANGUAGE_VERSION: 1.20
GL_STENCIL_BITS: 8
GL_VENDOR: ATI Technologies Inc.
GL_VERSION: 2.1 ATI-1.66.31
OGLEnabled: true
GL_EXTENSIONS: GL_ARB_color_buffer_float GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_draw_buffers GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging GL_ARB_instanced_arrays GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_provoking_vertex GL_ARB_seamless_cube_map GL_ARB_shader_objects GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shadow GL_ARB_shadow_ambient GL_ARB_sync GL_ARB_texture_border_clamp GL_ARB_texture_compression GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_texture_env_combine GL_ARB_texture_env_crossbar GL_ARB_texture_env_dot3 GL_ARB_texture_float GL_ARB_texture_mirrored_repeat GL_ARB_texture_non_power_of_two GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_transpose_matrix GL_ARB_vertex_array_bgra GL_ARB_vertex_blend GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_window_pos GL_EXT_abgr GL_EXT_bgra GL_EXT_bindable_uniform GL_EXT_blend_color GL_EXT_blend_equation_separate GL_EXT_blend_func_separate GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_clip_volume_hint GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_depth_bounds_test GL_EXT_draw_buffers2 GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXT_framebuffer_object GL_EXT_framebuffer_sRGB GL_EXT_geometry_shader4 GL_EXT_gpu_program_parameters GL_EXT_gpu_shader4 GL_EXT_multi_draw_arrays GL_EXT_packed_depth_stencil GL_EXT_packed_float GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture_array GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_s3tc GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_rectangle GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_timer_query GL_EXT_transform_feedback GL_EXT_vertex_array_bgra GL_APPLE_aux_depth_stencil GL_APPLE_client_storage GL_APPLE_element_array GL_APPLE_fence GL_APPLE_float_pixels GL_APPLE_flush_buffer_range GL_APPLE_flush_render GL_APPLE_object_purgeable GL_APPLE_packed_pixels GL_APPLE_pixel_buffer GL_APPLE_rgb_422 GL_APPLE_row_bytes GL_APPLE_specular_vector GL_APPLE_texture_range GL_APPLE_transform_hint GL_APPLE_vertex_array_object GL_APPLE_vertex_array_range GL_APPLE_vertex_point_size GL_APPLE_vertex_program_evaluators GL_APPLE_ycbcr_422 GL_ATI_blend_equation_separate 
Photo of Mark Fleming

Mark Fleming

  • 14 Posts
  • 5 Reply Likes

Posted 3 months ago

  • 5
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3439 Posts
  • 618 Reply Likes
Greetings Mark,

7.3.1 was released earlier today and had some bug fixes for crashing behavior included that might be affecting you as well. I would recommend you install the 7.3.1 update and monitor your system to see if it becomes unresponsive as you've seen in the past. If it does misbehave again, grab a screenshot of your Activity Monitor so we can take a look at the running processes on your Mac. 
Photo of Mark Fleming

Mark Fleming

  • 14 Posts
  • 5 Reply Likes
Unfortunately, it did not fix the issue.  Went non-responsive after a few hours of not using it.  

I brought up Activity Monitor to take a screenshot for you but see that it would take 3 or 4 screenshots to capture it all.  Is that what you want still?

Interestingly, when looking at the Activity Monitor I saw LR's CPU percentage jump up to over 100% a few times, alternating between that and low single digit percentages. It's settled down now.

However, I see Russ Quinlan's comment below, where he went back to 7.2 and his similar issue has stopped.  I have a feeling that's it's not my other applications (which haven't changed since this issue started a few weeks ago), but the LR release.
Photo of Frank Fischbach

Frank Fischbach

  • 4 Posts
  • 0 Reply Likes
I have exactly the same issue while I am running Windows 10. The issue is still persisting with 7.3.1.. In fact, my LR gets unresponsive already after some minutes of inactivity. 

I was in contact (via chat) with Adobe support, but that did not help at all. I already performed all the standard troubleshooting steps including resetting everything, reinstalling the app, trying different (new) catalogs, updating all driver. Support did some obviously needless things like give all users on my computer full rights to all Adobe folder (did not change anything since the logged in user already had that permissions).

I am pretty sure it is a software issue of LR, maybe a deadlock of some background processes which start after some idle time of LR.

No clue why not all users are impacted and Adobe cannot reproduce it in there (automated) tests.

I do not see any specific configuration with my machine, especially since Mac users are affected too. I am using and Nvidia card, but looking at the post, it also happens for AMD cards.

For me it is fully reproducible with a brand new catalog and only few images in it.
Photo of Russ Quinlan

Russ Quinlan

  • 3 Posts
  • 2 Reply Likes
Frank Fischbach, 7.2 is still working fine, but I should add that it was on my work computer, where the same issue doens't happen on my home computer with 7.3.1.  Now if I could only figure out why.
Photo of Craig Pruden

Craig Pruden

  • 2 Posts
  • 1 Reply Like
I have 7.3.1 and have the same problem as everyone else. When left idle for some period of time, LR goes unresponsive and I have to close it. Adobe has a problem and they don't know what it is.
Photo of Mark Fleming

Mark Fleming

  • 14 Posts
  • 5 Reply Likes
Thanks, I'm going to update and give it a shot!
Photo of Russ Quinlan

Russ Quinlan

  • 3 Posts
  • 2 Reply Likes
I have the same problem and 7.3.1 did not fix it.  Giving up and going back to 7.2.  Disgusted with Adobe right now.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 3384 Posts
  • 599 Reply Likes
How did it go, Mark?
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 14004 Posts
  • 1722 Reply Likes
Russ, do you have a USB drive that is going offline? Issue described here: https://feedback.photoshop.com/photoshop_family/topics/lightroom-classic-7-3-crash-on-eject-sd-card
Photo of Russ Quinlan

Russ Quinlan

  • 3 Posts
  • 2 Reply Likes
Thanks Jeffrey, but shoot, I already went back to 7.2 and it's working great.   I'll keep this if they come up with a new update and it still crashes.
Photo of Mark Fleming

Mark Fleming

  • 14 Posts
  • 5 Reply Likes
This is so frustrating. Constantly having to Force Quit LR and restarting.  I hope a fix is coming very soon.
Photo of Frank Fischbach

Frank Fischbach

  • 4 Posts
  • 0 Reply Likes
Mark, do you have an external USB card reader connected to your Mac? I just removed disconnected my card reader (there was no card inserted) and it did not crash since then. I need to do some more tests tomorrow...
Photo of Mark Fleming

Mark Fleming

  • 13 Posts
  • 5 Reply Likes
Frank,  I do have an external drive, but like so many others, it's the working drive I keep my LR photo library on. So I cannot disconnect it.
Photo of Frank Fischbach

Frank Fischbach

  • 4 Posts
  • 0 Reply Likes
I did some more testing and did not have the problem after removing my external USB card reader - so I am pretty sure that the issues is related to some external USB devices. Maybe some issue when the devices goes into power save mode - you might try to disable the power save for the external drive (if that is possible).
Photo of Mark Fleming

Mark Fleming

  • 30 Posts
  • 12 Reply Likes
I’ll check to see if I can keep that drive from sleeping. But since it never had done this until, roughly, a month or more ago, I hope Adobe is taking note of your comment since it has to be something with their recent LR updates.
Photo of Mark Fleming

Mark Fleming

  • 13 Posts
  • 5 Reply Likes
Three days ago I unchecked on my Mac in Energy Saving "Put Hard Disk to sleep when possible."  My external drive is a G-Drive and I read that it respects Mac's preferences.  
Unfortunately, it has not helped. LR still goes to unresponsive mode.
Photo of David Brown

David Brown

  • 8 Posts
  • 8 Reply Likes
Still becomes unresponsive apparently after computer goes into screen saver but definitely every time I leave it alone for a few hours.  Have tried every possible thing mentioned in the various threads.  Never had any issues to speak of before with LR or PS hanging like this.  
Photo of Frank Fischbach

Frank Fischbach

  • 4 Posts
  • 0 Reply Likes
Did you disconnect all external USB devices (as possible)? I disconnected my (unused) USB card reader and the issue was gone. Maybe also deactivating power save modes might help...
(Edited)
Photo of Gillian Moore

Gillian Moore

  • 1 Post
  • 0 Reply Likes
Has anyone found a fix for this? I'm having the same issue with my imac since upgrading. After about an hour of inactivity, my external drives go to sleep. I have to completely restart my computer each time to fix it. I have tried 'turning off power saving mode'. I also chatted with the tech, who wasn't able to help. I even reverted back to 7.2 and that hasn't helped either.  Below is a screen shot of the error in lightroom, and a shot of all my missing folders on my drive. 

 
(Edited)
Photo of Alan Hunt

Alan Hunt

  • 7 Posts
  • 3 Reply Likes
I am seeing the same behavior with the current version of Lightroom Classic on my Windows 10 PC. This started occurring with LR 7.3. I have Graphics processor off and have just disconnected my external USB card reader. I'll respond here if unplugging the USB card reader seems to change things.
Photo of Alan Hunt

Alan Hunt

  • 7 Posts
  • 3 Reply Likes
I left Lightroom up all day yesterday with USB card reader unplugged and had no LR hangs. 
Photo of Jeff Miller

Jeff Miller

  • 1 Post
  • 1 Reply Like
Lightroom has been a nightmare for a few months now, getting worse and worse.  I cannot have an experience with it where I don't spend a significant amount of time "not responding".   It is becoming unusable.
Photo of Alan Hunt

Alan Hunt

  • 4 Posts
  • 2 Reply Likes
I was having a similar experience. I unplugged a USB card reader that I had previously kept plugged in all the time, and the problem went away.
Photo of Mark Fleming

Mark Fleming

  • 14 Posts
  • 5 Reply Likes
This is getting ridiculous.  I'm starting to use Skylum Luminar app more often now. They are adding a library management function this year and then it can be a complete replacement for Lightroom.  The Skylum team is much more responsive than the Lightroom team.
Photo of Colink Technology

Colink Technology

  • 36 Posts
  • 8 Reply Likes
Windows 10 and LR Classic 7.3.1 hangs after it has lost focus for a while. This has been happening for some time, including at least the previous release.

I have one USB external drive connected but can't work without that (for auto, periodic backups) so do not wish to disconnect just to test buggy LR software.

It is very frustrating as unable to rely on LR when I move to another application. Wouldn't be so bad if we were not paying monthly for this app, bugs should be addressed much more quickly.