Wrong photo gets "stuck" in Develop Module display pane during editing session

[Marc Merlin]

I've been working on a relatively recent installation of Lightroom (see system info below) and have encountered a problem which I believe began after the latest update. It's difficult to reconstruct the sequence of actions that leads to the problem, but after doing some photo editing and switching back and forth from the Library and the Develop module, an extraneous photo gets "stuck" in the display pane of the Develop Module. Also, mousing over the filmstrip there results in incorrect or incorrectly oriented photos being displayed in the Navigation pane.

The problem is resolved temporarily by restarting Lightroom. It reappears soon after a fair amount of editing. I'm not sure, but deleting photos (using the LR interface, not the file system of course) seems to precede the appearance of the problem. For what it's worth, there are no issues reported about the consistency or integrity of the catalog when backing up.

Is this a known issue with a recent release or might it be something related to my particular installation. Any help would be much appreciated!

Thanks,

Marc

__________

Lightroom version: CC 2015.8 [ 1099473 ]

License: Creative Cloud

Operating system: Windows 10

Version: 10.0

Application architecture: x64

System architecture: x64

Logical processor count: 8

Processor speed: 4.0 GHz

Built-in memory: 32680.5 MB

Real memory available to Lightroom: 32680.5 MB

Real memory used by Lightroom: 1160.9 MB (3.5%)

Virtual memory used by Lightroom: 1165.2 MB

Memory cache size: 405.2 MB

Maximum thread count used by Camera Raw: 8

Camera Raw SIMD optimization: SSE2,AVX,AVX2

System DPI setting: 96 DPI

Desktop composition enabled: Yes

Displays: 1) 1920x1200

Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info:

Intel(R) HD Graphics 530

Check OpenGL support: Passed

Vendor: Intel

Version: 3.3.0 - Build 21.20.16.4534

Renderer: Intel(R) HD Graphics 530

LanguageVersion: 3.30 - Build 21.20.16.4534

Application folder: C:\Program Files\Adobe\Adobe Lightroom

Library Path: C:\Users\Marc Merlin\Pictures\Lightroom\Lightroom Catalog.lrcat

Settings Folder: C:\Users\Marc Merlin\AppData\Roaming\Adobe\Lightroom

Installed Plugins:

1) AdobeStock

2) Canon Tether Plugin

3) Facebook

4) Flickr

5) Leica Tether Plugin

6) Nikon Tether Plugin

Config.lua flags: None

Adapter #1: Vendor : 8086

  Device : 1912

  Subsystem : d0001458

  Revision : 6

  Video Memory : 128

Adapter #2: Vendor : 1414

  Device : 8c

  Subsystem : 0

  Revision : 0

  Video Memory : 0

AudioDeviceIOBlockSize: 1024

AudioDeviceName: Speakers (High Definition Audio Device)

AudioDeviceNumberOfChannels: 2

AudioDeviceSampleRate: 44100

Build: LR5x4

Direct2DEnabled: false

GL_ACCUM_ALPHA_BITS: 16

GL_ACCUM_BLUE_BITS: 16

GL_ACCUM_GREEN_BITS: 16

GL_ACCUM_RED_BITS: 16

GL_ALPHA_BITS: 8

GL_BLUE_BITS: 8

GL_DEPTH_BITS: 24

GL_GREEN_BITS: 8

GL_MAX_3D_TEXTURE_SIZE: 2048

GL_MAX_TEXTURE_SIZE: 16384

GL_MAX_TEXTURE_UNITS: 8

GL_MAX_VIEWPORT_DIMS: 16384,16384

GL_RED_BITS: 8

GL_RENDERER: Intel(R) HD Graphics 530

GL_SHADING_LANGUAGE_VERSION: 4.40 - Build 21.20.16.4534

GL_STENCIL_BITS: 8

GL_VENDOR: Intel

GL_VERSION: 4.4.0 - Build 21.20.16.4534

GPUDeviceEnabled: false

OGLEnabled: true

GL_EXTENSIONS: GL_3DFX_texture_compression_FXT1 GL_AMD_depth_clamp_separate GL_AMD_vertex_shader_layer GL_AMD_vertex_shader_viewport_index GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_blend_func_extended GL_ARB_buffer_storage GL_ARB_cl_event GL_ARB_clear_buffer_object GL_ARB_clear_texture GL_ARB_clip_control GL_ARB_color_buffer_float GL_ARB_compatibility GL_ARB_compressed_texture_pixel_storage GL_ARB_compute_shader GL_ARB_conservative_depth GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_elements_base_vertex GL_ARB_draw_indirect GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_explicit_attrib_location GL_ARB_explicit_uniform_location GL_ARB_fragment_coord_conventions GL_ARB_fragment_layer_viewport GL_ARB_fragment_program GL_ARB_fragment_program_shadow GL_ARB_fragment_shader GL_ARB_fragment_shader_interlock GL_ARB_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_indirect_parameters GL_ARB_instanced_arrays GL_ARB_internalformat_query GL_ARB_internalformat_query2 GL_ARB_invalidate_subdata GL_ARB_map_buffer_alignment GL_ARB_map_buffer_range GL_ARB_multi_bind GL_ARB_multi_draw_indirect GL_ARB_multisample GL_ARB_multitexture GL_ARB_occlusion_query GL_ARB_occlusion_query2 GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_post_depth_coverage GL_ARB_program_interface_query GL_ARB_provoking_vertex GL_ARB_query_buffer_object GL_ARB_robust_buffer_access_behavior GL_ARB_robustness GL_ARB_robustness_isolation GL_ARB_sample_shading GL_ARB_sampler_objects GL_ARB_seamless_cube_map GL_ARB_seamless_cubemap_per_texture GL_ARB_separate_shader_objects GL_ARB_shader_atomic_counters GL_ARB_shader_bit_encoding GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_stencil_export GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_stencil_texturing GL_ARB_sync GL_ARB_tessellation_shader GL_ARB_texture_barrier GL_ARB_texture_border_clamp GL_ARB_texture_buffer_object_rgb32 GL_ARB_texture_buffer_range GL_ARB_texture_compression GL_ARB_texture_compression_bptc GL_ARB_texture_compression_rgtc GL_ARB_texture_cube_map GL_ARB_texture_cube_map_array 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_gather GL_ARB_texture_mirror_clamp_to_edge GL_ARB_texture_mirrored_repeat GL_ARB_texture_multisample GL_ARB_texture_non_power_of_two GL_ARB_texture_query_levels GL_ARB_texture_query_lod GL_ARB_texture_rectangle GL_ARB_texture_rg GL_ARB_texture_rgb10_a2ui GL_ARB_texture_stencil8 GL_ARB_texture_storage GL_ARB_texture_storage_multisample GL_ARB_texture_swizzle GL_ARB_texture_view GL_ARB_timer_query GL_ARB_transform_feedback2 GL_ARB_transform_feedback3 GL_ARB_transform_feedback_instanced GL_ARB_transpose_matrix GL_ARB_uniform_buffer_object GL_ARB_vertex_array_bgra GL_ARB_vertex_array_object GL_ARB_vertex_attrib_64bit GL_ARB_vertex_attrib_binding GL_ARB_vertex_buffer_object GL_ARB_vertex_program GL_ARB_vertex_shader GL_ARB_vertex_type_10f_11f_11f_rev GL_ARB_vertex_type_2_10_10_10_rev GL_ARB_viewport_array GL_ARB_window_pos GL_ATI_separate_stencil GL_EXT_abgr GL_EXT_bgra 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_compiled_vertex_array GL_EXT_direct_state_access 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_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_packed_pixels GL_EXT_polygon_offset_clamp GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_specular_color GL_EXT_shader_framebuffer_fetch GL_EXT_shader_integer_mix GL_EXT_shadow_funcs GL_EXT_stencil_two_side GL_EXT_stencil_wrap GL_EXT_texture3D GL_EXT_texture_array GL_EXT_texture_compression_s3tc GL_EXT_texture_edge_clamp GL_EXT_texture_env_add GL_EXT_texture_env_combine GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod_bias GL_EXT_texture_rectangle GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_shared_exponent GL_EXT_texture_snorm GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback GL_IBM_texture_mirrored_repeat GL_INTEL_conservative_rasterization GL_INTEL_fragment_shader_ordering GL_INTEL_framebuffer_CMAA GL_INTEL_map_texture GL_INTEL_multi_rate_fragment_shader GL_INTEL_performance_query GL_KHR_blend_equation_advanced GL_KHR_blend_equation_advanced_coherent GL_KHR_debug GL_KHR_texture_compression_astc_hdr GL_KHR_texture_compression_astc_ldr GL_NV_blend_square GL_NV_conditional_render GL_NV_primitive_restart GL_NV_texgen_reflection GL_SGIS_generate_mipmap GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_SUN_multi_draw_arrays GL_WIN_swap_hint

[Just Shoot Me · Accepted solution]

This has been reported in other threads. Mostly with Windows 10 but one person is reporting something similar on OS X Sierra.

Deleting photos in Lightroom 2015.8 on Windows 10 issue

Post over at the bug forum in this thread.

Lightroom: No Image displays in Develop Module after Deletion of Other Images | Photoshop Family Cus...

[Marc Merlin]

Thanks!

[TJW250]

Happening to me as well and it is the reason I signed up on the forums. The sequence of events that make it happen for me are: Hitting "X" to reject photos, Hitting Command Delete to delete them, then, whatever was the last photo to have been displayed in the develop module (even if it was just deleted), it gets stuck on the screen until I restart Lightroom. I'm running the latest version of CC on an iMac with El Capitan.

[Bob Somrak]

Supposedly switching to Library before doing the DELETE avoids the problem.  Adobe is aware of the problem so maybe there will be a fix.

[TJW250]

Yes, just read that in another place. Thanks for the tip Bob! Will try that while awaiting a fix

[skirmisser]

I have exactly the same issue with Lightroom 6.8:

Re: Lightroom 6.8 Mac file delete issue

[googull]

Ditto for me on macOS 10.12.2 using LR 2015.8

[hofendisasd]

I am having the identical problem, which is why I too signed onto this forum. Windows 10, all updates installed for Win and LR. I tried to replicate tjw250's suggestion that this was related to deleting images via X and Command-Delete, but it didn't happen for me. Next time I get a frozen image, I will try Bob's suggestion of switching to Library mode before the delete to see if that works.

This is a VERY irritating problem, as the only fix up to now has been to close and reopen LR. I've processed over 10,000 images in the past two months, so opening/closing LR each time this happens is not a viable option to stick with LR. 😞

[hofendisasd]

I just posted the following another forum. Is THIS is trigger for anyone else having this problem? -SJ

I rejected several images in Develop mode with an X and ended on an image I was NOT going to delete. Did a Ctrl-Backspace to delete and everything was fine.

THEN, rejected several more images, but this time ended on an image that was part of the rejected group. Did a Ctrl-Backspace to delete and now the previewed image froze - the image frozen is the rejected image that had been showing when I did the Ctrl-Backspace.

If I go into any other module, I can select any image and view it. But going back into Develop ONLY displays that now-rejected frozen image.

[Just Shoot Me]

I suggest you start using LR as it was intended to be used. Use the Library module to cull images and the Develop module for developing and adjusting images. If you do that this minor bug won't pop up.

[hofendisasd]

Seriously, "as it was intended to be used???" Please show me where in the documentation it states that images must be deleted only from the Library module.

For some of us, this isn't a minor bug. I processed 12,000 new images in the past 10 weeks and while I cull most of my deleted's from the Library module, there are scores that I decide in Develop won't make the cut and get a later X. So royal waste of time to then click back to Library and back to Develop to delete the ones I've X'd...or to singly delete them in process.

Maybe since I understand Adobe engineers are now aware of the issue, they can just fix the bug.

[Just Shoot Me]

There is no documentation that states that. But that is what the Library module is for. To first go through your images, apply keywords or put them into collections, Review good from bad and get ride of the bad. You can also move images around into different folder if you like. That is why the Library module is the first in the line of modules at the top of the LR program screen.

Then the simple thing for you to do is X them then when you want to actually delete them just press the "g" key to take you back to the Library module before you do the actual deleting. Once that is done hit the "d" key to take you back to the develop module.

This should be fixed in the next release.

[Heinzkoch119]

Minor bug or not, that isn't the issue here. It simply shouldn't happen.

Your answer: "I suggest you start using LR as it was intended to be used...", is a little cynical, as it is no where written that it should be used in that manner.

[googull]

This discussion is certainly drifting but I'd like to follow this a bit because it's been a unspoken rub for me for a long while.   What I am talking about is the rigid structure and imposing flow of LR being contrary to how I naturally work and want to work.   I find for example, that I spend the vast majority of my time in the development module - it is where I choose to "live".   The only reason I switch to the Library is to apply Keywords and gain access to the Grid View.  Early on, the imposition of switching modes constantly was fine because switching times were swift.   But now, especially in this latest CC, the switching time has become variable and an agitating waste of time.  Perhaps it is because my images are larger these days (36MP) or that the screen res had expanded (5K) but the computer performance is top notch so switching time IMO really should be cached and instantaneous.   Most of what's in the Library Module is useless to me and for my needs I feel like the two modules could easily be squeezed into one with a switch for beginner/expert use. 

Similar feeling with the order of controls, panning back and forth between those that I am using repeatedly or playing solo mode with  each image is tiresome.  Why no custom workspaces like in Photoshop?  I found myself trialing Luminar this holiday and have been delighted with the workflow opportunities it enables with named workspaces. 

Anyway, Adobe clearly has a model for how they think one should work in LR with limited flexibility to accomplish the same tasks in more than one module (mode) though that is no excuse for a show stopping bug.

Way off topic I realize and I should probably go find or start a thread re: Named Workspaces and consolidating Modules ^g  😉

[hofendisasd]

Custom workspaces would be a VERY helpful addition to LR, but let me address one assumption you may have read into what's been written in this thread: "Just Shoot Me's" assertion that Adobe requires images to be deleted from the Library module as the "the way it (LR) was intended to be used." That's just false. If Adobe had intended that workflow, it would not have allowed Ctr-Backspace to be used in Develop, period. It's only this update of LR that has introduced the bug that causes this problem. So I reject the "intended to be used" assumption - I think Adobe is smarter than that. Its engineers just need to fix the bug.

In terms of workaround, I've found that the only time the bug appears seems to be when I leave the preview image on one of the images I intend to delete. If I move to another image that does not have an X, LR continues to work fine and the preview doesn't freeze. I suspect LR gets confused when its current preview image no longer exists after the Ctr-Backspace and crashes the preview.

[lindavs0362]

I use LRoom CC and am also having the same issue - after x'ing several images to delete in the develop mode, and pressing Command/Delete, LRoom freezes.  This issue began as soon as I upgraded to LR 2015.8 Release.  At the time I upgraded LRoom, my operating system was ElCapitan OX 10.11.  In attempting to correct this problem I reset the Preferences by holding Shift-Option-Delete.  This did not correct the problem.  Then I changed LRoom's permissions which also did not help.  Finally I deleted LRoom CC 2015.8, updated my Mac OX to Sierra, re-installed LRoom CC 2015.8 and the problem continues.  I will try deleting images while in Library instead of in Develop and hopefully this will work and hopefully Adobe will correct this problem soon !!

Linda V.

[Uksnapper]

Using iMac OS 10.10.5 - Same issue.....try to delete in Develop (as I was able to do perfectly well with LR 5.7) and LR CC (downloaded 2 days ago from new) freezes. If I delete whilst in Library it seems ok.

Just tried hofendisasd solution and that too seems to work - switch to a non-marked for deletion image and then delete command.

[Andy Vitus]

I have this exact problem on Windows 10. And I also x and then Ctrl-Del in the Develop module.

[RLaw59]

I'm having this issue in Mac OS Sierra 10.12.3 (current as of post). A rejected photo stays locked into the develop module and no way to remove or bring up the photo selected in the Library or thumbnail views. I would classify this as a frequent occurrence, but intermittent in nature. Very frustrating as the only way to "solve" is to shut down program and restart. On one occasion had to resort to a reboot of the Mac.

[Uksnapper]

I was in online chat with Adobe this morning about this issue - it is a known problem and apparently the tech team are working on it.

I've found that if a photo is marked for rejection/deletion within the develop module, and you return to the Library module and Cmd/Del from within there, all seems to work fine....no need to restart LR etc.

I am using MAC OS 10.10.5

Hope this 'helps'

[Copernicus987]

I have the same problem since updating to latest LR on CC on 16 Feb 2017. I'm using Mac El Capitan 10.11.6. Extremely inconvenient and frustrating.

[belindaj_LR]

It is not just an "after delete" issue. While I realize this may or may not be related - in the effort to assist with the troubleshooting I will try to explain another scenario. As someone who shoots and edits 10-14,000 images every weekend from January through April - this is a HUGE bug for me at the moment. I've been a LR user since the original BETA. I am currently using CC 2015.8 Release, Camera Raw 9.8 - and Windows 10. This is a CLEAN install directly from Creative Cloud and a new catalog - all in the past 2 weeks on a brand new Dell I5, 24 GB of Ram.

My images don't get stuck after deleting - in fact I've never had that issue. (And I DO delete in the Develop module - it's a streamlined workflow for processing thousands of action photos which is in large art exactly what Lightroom was built for). I publish out through the SmugMug built-in plugin and that is where the "stickyness" is occurring.

Example: 10,000 images from an 8 hour event.
In Library, Import, categorize into named school folders, apply keywords.
In Develop, Cull (by marking rejects) AND process the keepers in a single continuous workflow
Still in Develop, Delete rejects completely (not just out of LR, completely off disk - yes, I am aware they are gone forever - with the volume of images I go through if I somehow lose a few great ones I am not concerned)
Switch to Library, Drag the edited keepers to the appropriate Smugmug folder for publishing, hit publish.

It's at this point that I NORMALLY would go back to my list of folders in Library and move to the next school to begin its processing back in Develop. My desktop has enough guts in it that I don't usually have to wait for the publish to complete before starting on the next set of edits - but almost always now - I can see the correct images in Library for the next school (but once I click to Develop - the previous ones are still showing and no matter what I do - grid or single image view - I can't "make" them show up in Develop until I restart Lightroom. (Which means I DO have to wait for the publish to finish before restarting - so I'm wasting time in my normal workflow)

This is a really big deal for me and in all the years I've been working in this manner (since the very beginning of Lightroom 7-8 years ago) this has never happened in any version or update.

Completely willing to work with an Adobe engineer if they need more information.

[belindaj_LR]

ok, I tried adjusting my workflow to not actually delete the rejects in my usual order - just left them to delete later - and sure enough - I've now changed folders and modules 3 times without having to restart - so I guess perhaps it IS tied to the delete process. Glad I googled the problem and managed to find this thread. Would love to see it resolved though.

[Nero69-gq8aq8]

Same problem here and I am using the imac version.  Only time it seems to be a problem is if I delete in Develop mode.  Never had this problem before.  Hopefully this can be rectified in an update.  Seems like a simple fix