Lightroom classic becomes unresponsive during sync. Memory leak?

Report · Feb 15, 2019

Context: Earlier this year I managed to migrate my old catalog of 20.000 photos into the adobe cloud. I have been using lightroom classic for a long time, but since I love the way the new lightroom CC is evolving I decided to start using lightroom CC as the prime source of truth, and say goodbye to my old native catalog in lightroom classic. I started with a new and empty catalog that should sync with my cloud environment. New pictures will be imported using the new lightroom CC and should magically appear in lightroom classic thanks to the sync.

Problem: When lightroom classic starts syncing, the counter of "syncing x photo's" in the upper left hand corner goes up to around 12.000. Lightroom will start downloading a couple of photo's until it becomes slower and slower and slower, and after about syncing 10 photo's will become completely unresponsive. The windows task manager shows that lightroom classic is taking around 25% of CPU, and has taken up all of the available memory (>12GB used of the available 16GB). A force stop of lightroom is the only way out. After 2 days I've only managed to sync 260 photo's.

Info:

Lightroom Classic version: 8.2 [ 1204643 ]
License: Creative Cloud
Language setting: en
Operating system: Windows 10 - Business Edition
Version: 10.0.17134
Application architecture: x64
System architecture: x64
Logical processor count: 8
Processor speed: 4.0 GHz
Built-in memory: 16344.3 MB
Real memory available to Lightroom: 16344.3 MB
Real memory used by Lightroom: 1130.4 MB (6.9%)
Virtual memory used by Lightroom: 919.1 MB
GDI objects count: 582
USER objects count: 2036
Process handles count: 1506
Memory cache size: 0.0MB
Internal Camera Raw version: 11.2 [ 134 ]
Maximum thread count used by Camera Raw: 5
Camera Raw SIMD optimization: SSE2,AVX,AVX2
Camera Raw virtual memory: 0MB / 8172MB (0%)
Camera Raw real memory: 0MB / 16344MB (0%)
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 2560x1440
Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No

Graphics Processor Info:
DirectX: NVIDIA GeForce GTX 980 Ti (25.21.14.1616)

Application folder: C:\Program Files\Adobe\Adobe Lightroom Classic CC
Library Path: D:\Foto\catalog\catalog.lrcat
Settings Folder: C:\Users\Papa\AppData\Roaming\Adobe\Lightroom

Installed Plugins:
1) AdobeStock
2) Facebook
3) Flickr
4) Nikon Tether Plugin
5) SmugMug

Config.lua flags: None

Adapter #1: Vendor : 10de
Device : 17c8
Subsystem : 32321462
Revision : a1
Video Memory : 6097
Adapter #2: Vendor : 1414
Device : 8c
Subsystem : 0
Revision : 0
Video Memory : 0

Message was edited by: Mod to removed unneeded text.

Report · Feb 16, 2019

I may have found a possible cause for the memory leak that is worth trying!! I deactivated all the "publishing plugins" in lightroom classic and the problem seems to have disappeared. My sync has been happily humming now for 60 minutes and is only using 1.5G of memory (according to task manager). Before, it would hang after 5 minutes and take up all the memory it could get its hands on (13GB).

* double click on one of the publish services to open the dialogue

* in the dialogue, click on plugin manager...

* deactivate all plugins one by one (I only kept the "disk" publish service active)

* restart lightroom classic

after restart, you should no longer see the publish services in the publish section. In my case, the memory leak issue has disappeared, and lightroom classic works like a charm.

It now needs to sync 20.000 pictures (download from cloud) on a slow connection. It will take a long time but I will update this thread with my findings.

Report · Feb 16, 2019

Unfortunately, after a couple of hours the problem returned in full force.

Observation: when I pause sync and restart lightroom classic, there is no problem with the memory consumption. As soon as I continue the sync, the memory usage spirals out of control. Pausing again does not stop the issue, only after reboot.

Report · Feb 16, 2019

Try disabling your anti virus program. A lot of times these AV/internet security programs scan every file that goes out or comes in from the internet. That might be part of your problem.

I have not used an AV/IS program for over 12 years and have NO problems with LR Classic (the Traditional version) syncing with the web system.

I just created a new Collection, Synced it with the web system, then loaded 433 images into that collection. Brought up Task Manager and memory use started at 5.05 GBs went up to 5.75+ and is now at 5.55 GBs.

So it is something on your system that is causing this rise in memory use when syncing with the LR web system. IMO the only thing that could do that is some type of AV or internet security program. No other program that I'm aware of would scan every file being uploaded from your computer to the net.

Oh and all the files I selected to upload are Fuji X-T2 RAF files of 48+/-MBs in size.

CPU activity is much larger, spiking @ 90+% and sometimes going to 100%, than memory use.

Report · Feb 16, 2019

Hi JSM,

Thanks for taking the time to respond, much appreciated!!

It's not the AV though, just like you I've disabled that a long time ago. I'm also a long time Lightroom (classic) user, and again in line with your experience I've been able to upload and sync to the cloud in smaller badges (uploading 1000 images no problem. That's how I managed to get my 20.000 photo's up there. I'm not posting to complain about ligthroom CC or classic, I love and need them both, but I'm still struggling with the co-existence of the two flavors on my desktop.

I agree there is "'something" on my system that causes it to behave differently than yours, however, that does not mean lightroom classic is behaving as it should. I'm still convinced the issue is "within" lightroom classic. There is no way that an external program such as an antivirus can cause the memory allocation of the "Lightroom Classic executable" to go up. Memory allocated to a program has been requested by that program, and it is the responsibility of that program to release it (or of the Operating system upon termination of the program)

The problem I'm observing is not related to uploading/sync'ing TO the cloud. It is related to downloading/sync'ing FROM the cloud with Lightroom Classic (the new lightroom CC on my desktop sync's like a charm and downloaded every single photo. Recently I uninstalled lightroom classic, re-installed it from scratch, started a new catalog, and promoted it into the catalog to use with lightroom sync. This is where my challenge started (suddenly lightroom classic needs to sync/download >20000 photo's from the cloud).

I've spent most part of today observing Lightroom Classic and its memory consumption, and this is what I've found:

As the number of "syncing X photo's" in the upper left hand corner (the badge where you start/pause the sync) increases, so does the memory consumption.

When the number increases with 450 pictures, the memory consumption of lightroom classic (not the system memory) increases with 10G. That's where I need to stop lightroom and restart it to prevent my system to start paging/swapping. When I restart lightroom, it will continue where it left of with the sync and with normal memory consumption, until the sync number increases again with 450 pictures (more or less) and is back at >10G memory consumption. I've done this over and over again until the "syncing X photos" got to 13.000 and stopped increasing. I'm not sure if it's related, but 10G divided by 450 is a bit over 20MB wich is around the average size of my raw photo's. It feels as if Lightroom reserves memory for the files it adds to the download list... Of course this is just a guess

As soon as the sync number got stable, the memory explosion issue stopped as well, and lightroom is then able to focus its resources on downloading the files from the cloud

However, it is not downloading every file The syncing counter has gone down by 7000 in the mean time, but only 1800 photo's got downloaded. Is there a good write-up somewhere on the internals of the sync process? How does it decide if a photo needs to be downloaded or not?

Sorry for the long post, hope you made it to the end!

/K

Report · Mar 06, 2019

Hi

Just installed the latest classic version (8.2) and created a new fresh catalog to play around with. Please note I have installed LR on more or less fresh Windows 10 Pro installation. My system has 32 GB of RAM which gets consumed by lightroom only within a few minutes.

So there definitly IS a memory leak, that does seem to be related to the synchronization process. This anoying bug started to occur after I enabled "synchronize with lightroom cc" (don't know the correct english term for it as I am using a german version). As mentioned I have created a fresh cataloq and added around 70 pictures to it. That was it and enough the trigger the memory leaking bug.

Please investigate!!!!!

Lightroom Classic-Version: 8.2 [ 1204643 ]

Lizenz: Creative Cloud

Spracheinstellung: de

Betriebssystem: Windows 10 - Business Edition

Version: 10.0.17763

Anwendungsarchitektur: x64

Systemarchitektur: x64

Anzahl logischer Prozessoren: 8

Prozessorgeschwindigkeit: 3.7 GHz

Integrierter Speicher: 32650.1 MB

Für Lightroom verfügbarer phys. Speicher: 32650.1 MB

Von Lightroom verwendeter phys. Speicher: 513.3 MB (1.5%)

Von Lightroom verwendeter virtueller Speicher: 537.3 MB

Anzahl GDI-Objekte: 603

Anzahl BENUTZER-Objekte: 1934

Anzahl Prozess-Handles: 1377

Cache-Speichergröße: 0.0MB

Interne Camera Raw-Version: 11.2 [ 134 ]

Maximale Anzahl Threads, die Camera Raw verwendet: 5

Camera Raw SIMD-Optimierung: SSE2,AVX

Virtueller Speicher in Camera Raw: 0MB / 16325MB (0%)

Physischer Speicher in Camera Raw: 0MB / 32650MB (0%)

DPI-Einstellung des Systems: 96 DPI

Desktop-Komposition aktiviert: Ja

Monitore/Anzeigegeräte: 1) 1920x1200, 2) 1200x1920

Eingabetypen: Multitouch: Nein, integrierte Toucheingabe: Nein, integrierter Stift: Nein, externe Toucheingabe: Nein, externer Stift: Nein, Tastatur: Nein

Informationen zum Grafikprozessor:

DirectX: NVIDIA Quadro K600 (24.21.14.1216)

Anwendungsordner: C:\Program Files\Adobe\Adobe Lightroom Classic CC

Bibliothekspfad: C:\Temp\Temp2Catalog\Temp2Catalog.lrcat

Einstellungen-Ordner: C:\Users\sp4rc\AppData\Roaming\Adobe\Lightroom

Installierte Zusatzmodule:

1) Show Focus Points

Config.lua-Flags: None

Adapter Nr. 1: Anbieter : 10de

Gerät : ffa

Subsystem : 94b10de

Version : a1

Grafikspeicher : 985

Adapter Nr. 2: Anbieter : 1414

Gerät : 8c

Subsystem : 0

Version : 0

Grafikspeicher : 0

AudioDeviceIOBlockSize: 1024

AudioDeviceName: Speakers (High Definition Audio Device)

AudioDeviceNumberOfChannels: 2

AudioDeviceSampleRate: 48000

Build: 12.1x4

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: 0

GL_BLUE_BITS: 8

GL_DEPTH_BITS: 24

GL_GREEN_BITS: 8

GL_MAX_3D_TEXTURE_SIZE: 4096

GL_MAX_TEXTURE_SIZE: 16384

GL_MAX_TEXTURE_UNITS: 4

GL_MAX_VIEWPORT_DIMS: 16384,16384

GL_RED_BITS: 8

GL_RENDERER: Quadro K600/PCIe/SSE2

GL_SHADING_LANGUAGE_VERSION: 4.60 NVIDIA

GL_STENCIL_BITS: 8

GL_VENDOR: NVIDIA Corporation

GL_VERSION: 4.6.0 NVIDIA 412.16

GPUDeviceEnabled: false

OGLEnabled: true

GL_EXTENSIONS: GL_AMD_multi_draw_indirect GL_AMD_seamless_cubemap_per_texture GL_ARB_arrays_of_arrays GL_ARB_base_instance GL_ARB_bindless_texture 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_conservative_depth GL_ARB_compute_shader GL_ARB_compute_variable_group_size GL_ARB_conditional_render_inverted GL_ARB_copy_buffer GL_ARB_copy_image GL_ARB_cull_distance GL_ARB_debug_output GL_ARB_depth_buffer_float GL_ARB_depth_clamp GL_ARB_depth_texture GL_ARB_derivative_control GL_ARB_direct_state_access GL_ARB_draw_buffers GL_ARB_draw_buffers_blend GL_ARB_draw_indirect GL_ARB_draw_elements_base_vertex GL_ARB_draw_instanced GL_ARB_enhanced_layouts GL_ARB_ES2_compatibility GL_ARB_ES3_compatibility GL_ARB_ES3_1_compatibility GL_ARB_ES3_2_compatibility 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_framebuffer_no_attachments GL_ARB_framebuffer_object GL_ARB_framebuffer_sRGB GL_ARB_geometry_shader4 GL_ARB_get_program_binary GL_ARB_get_texture_sub_image GL_ARB_gl_spirv GL_ARB_gpu_shader5 GL_ARB_gpu_shader_fp64 GL_ARB_gpu_shader_int64 GL_ARB_half_float_pixel GL_ARB_half_float_vertex GL_ARB_imaging 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_parallel_shader_compile GL_ARB_pipeline_statistics_query GL_ARB_pixel_buffer_object GL_ARB_point_parameters GL_ARB_point_sprite GL_ARB_polygon_offset_clamp 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_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_counter_ops GL_ARB_shader_atomic_counters GL_ARB_shader_ballot GL_ARB_shader_bit_encoding GL_ARB_shader_clock GL_ARB_shader_draw_parameters GL_ARB_shader_group_vote GL_ARB_shader_image_load_store GL_ARB_shader_image_size GL_ARB_shader_objects GL_ARB_shader_precision GL_ARB_shader_storage_buffer_object GL_ARB_shader_subroutine GL_ARB_shader_texture_image_samples GL_ARB_shader_texture_lod GL_ARB_shading_language_100 GL_ARB_shading_language_420pack GL_ARB_shading_language_include GL_ARB_shading_language_packing GL_ARB_shadow GL_ARB_sparse_buffer GL_ARB_sparse_texture GL_ARB_spirv_extensions 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 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_filter_anisotropic 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_transform_feedback_overflow_query 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_draw_buffers GL_ATI_texture_float GL_ATI_texture_mirror_once GL_S3_s3tc GL_EXT_texture_env_add 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_compiled_vertex_array GL_EXT_Cg_shader GL_EXT_depth_bounds_test GL_EXT_direct_state_access GL_EXT_draw_buffers2 GL_EXT_draw_instanced GL_EXT_draw_range_elements GL_EXT_fog_coord GL_EXT_framebuffer_blit GL_EXT_framebuffer_multisample GL_EXTX_framebuffer_mixed_formats GL_EXT_framebuffer_multisample_blit_scaled 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_packed_pixels GL_EXT_pixel_buffer_object GL_EXT_point_parameters GL_EXT_polygon_offset_clamp GL_EXT_provoking_vertex GL_EXT_rescale_normal GL_EXT_secondary_color GL_EXT_separate_shader_objects GL_EXT_separate_specular_color GL_EXT_shader_image_load_store 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_buffer_object GL_EXT_texture_compression_dxt1 GL_EXT_texture_compression_latc GL_EXT_texture_compression_rgtc GL_EXT_texture_compression_s3tc GL_EXT_texture_cube_map GL_EXT_texture_edge_clamp GL_EXT_texture_env_combine GL_EXT_texture_env_dot3 GL_EXT_texture_filter_anisotropic GL_EXT_texture_integer GL_EXT_texture_lod GL_EXT_texture_lod_bias GL_EXT_texture_mirror_clamp GL_EXT_texture_object GL_EXT_texture_shared_exponent GL_EXT_texture_sRGB GL_EXT_texture_sRGB_decode GL_EXT_texture_storage GL_EXT_texture_swizzle GL_EXT_timer_query GL_EXT_transform_feedback2 GL_EXT_vertex_array GL_EXT_vertex_array_bgra GL_EXT_vertex_attrib_64bit GL_EXT_window_rectangles GL_EXT_import_sync_object GL_IBM_rasterpos_clip GL_IBM_texture_mirrored_repeat GL_KHR_context_flush_control GL_KHR_debug GL_EXT_memory_object GL_EXT_memory_object_win32 GL_EXT_win32_keyed_mutex GL_KHR_parallel_shader_compile GL_KHR_no_error GL_KHR_robust_buffer_access_behavior GL_KHR_robustness GL_EXT_semaphore GL_EXT_semaphore_win32 GL_KTX_buffer_region GL_NV_alpha_to_coverage_dither_control GL_NV_bindless_multi_draw_indirect GL_NV_bindless_multi_draw_indirect_count GL_NV_bindless_texture GL_NV_blend_equation_advanced GL_NV_blend_square GL_NV_command_list GL_NV_compute_program5 GL_NV_conditional_render GL_NV_copy_depth_to_color GL_NV_copy_image GL_NV_deep_texture3D GL_NV_depth_buffer_float GL_NV_depth_clamp GL_NV_draw_texture GL_NV_draw_vulkan_image GL_NV_ES1_1_compatibility GL_NV_ES3_1_compatibility GL_NV_explicit_multisample GL_NV_feature_query GL_NV_fence GL_NV_float_buffer GL_NV_fog_distance GL_NV_fragment_program GL_NV_fragment_program_option GL_NV_fragment_program2 GL_NV_framebuffer_multisample_coverage GL_NV_geometry_shader4 GL_NV_gpu_program4 GL_NV_internalformat_sample_query GL_NV_gpu_program4_1 GL_NV_gpu_program5 GL_NV_gpu_program5_mem_extended GL_NV_gpu_program_fp64 GL_NV_gpu_shader5 GL_NV_half_float GL_NV_light_max_exponent GL_NV_multisample_coverage GL_NV_multisample_filter_hint GL_NV_occlusion_query GL_NV_packed_depth_stencil GL_NV_parameter_buffer_object GL_NV_parameter_buffer_object2 GL_NV_path_rendering GL_NV_pixel_data_range GL_NV_point_sprite GL_NV_primitive_restart GL_NV_query_resource GL_NV_query_resource_tag GL_NV_register_combiners GL_NV_register_combiners2 GL_NV_shader_atomic_counters GL_NV_shader_atomic_float GL_NV_shader_buffer_load GL_NV_shader_storage_buffer_object GL_NV_texgen_reflection GL_NV_texture_barrier GL_NV_texture_compression_vtc GL_NV_texture_env_combine4 GL_NV_texture_multisample GL_NV_texture_rectangle GL_NV_texture_rectangle_compressed GL_NV_texture_shader GL_NV_texture_shader2 GL_NV_texture_shader3 GL_NV_transform_feedback GL_NV_transform_feedback2 GL_NV_uniform_buffer_unified_memory GL_NV_vertex_array_range GL_NV_vertex_array_range2 GL_NV_vertex_attrib_integer_64bit GL_NV_vertex_buffer_unified_memory GL_NV_vertex_program GL_NV_vertex_program1_1 GL_NV_vertex_program2 GL_NV_vertex_program2_option GL_NV_vertex_program3 GL_NV_video_capture GL_NVX_conditional_render GL_NVX_gpu_memory_info GL_NVX_multigpu_info GL_NVX_nvenc_interop GL_NV_shader_thread_group GL_NV_shader_thread_shuffle GL_KHR_blend_equation_advanced GL_OVR_multiview GL_OVR_multiview2 GL_SGIS_generate_mipmap GL_SGIS_texture_lod GL_SGIX_depth_texture GL_SGIX_shadow GL_SUN_slice_accum GL_WIN_swap_hint WGL_EXT_swap_control

kgeusens

Report · Mar 13, 2019

I have exactly the same problem. My memory usage goes over 10-13 GB and lightroom classic cc becomes unresponsive when syncing more than 40.000 pictures (10MB on average) from scratch in a new lightroom classic cc catalog.

Report · Mar 14, 2019

"Memory allocated to a program has been requested by that program, and it is the responsibility of that program to release it (or of the Operating system upon termination of the program)"

.....................................................

That is not the way memory management works in Windows; not sure about Mac. The memory is kept by the Operating system after the program has released it, in case you want that stuff again. Only when another program wants memory does the OS release the stored memory.

Bob Frost

Report · Mar 24, 2019

Hi

I have the same problem. I have come to the conclusion that you should NOT migrate any classic catalogs to the CC unless you are not going to use Classic anymore.

I managed to fix my classic though after I migrated a catalog of about 11k photos, and ended up with the same problem that you mentioned above.

Fix:

1. In LR CC: Delete all files, albums and folders added from the migrated catalog. Verify that the files are also deleted from the cloud storage in LR on the web.

2. Open Classic. I was supprized to se that classic was still trying to sync the deleted cloud files. And I could see classic tried to add these files to a CC device called "Macbook Pro".

3. I paused the sync process before Classic got time to become unresponsive.

4. Deleted all the imported files from the just mentioned CC device. (All files and adjustments was still intact in the original classic catalog I initially tried to migrate to CC. So I didn't worry about loosing any work.)

Then after starting the sync process again, I could see after a few minutes the amount of files classic tried to sync was dropping and in about 10-15 minutes was 0.

Note to myself. DON'T MIGRATE CLASSIC TO CC. Just synk between the two versions of LR...

Report · Jul 19, 2019

I’ve been on customer support for this many times. Each time the person controls my system, changes this permission or that, looks around, and nothing changes. When syncing, the memory use explodes until the app and the system hang.

This last session with customer support, the person told me to create a new user on the Mac, start LR and point to the same catalog, and then sync. No memory leak at all. Sync is slow as molasses, but it is syncing both ways.

So this leads to a conflict. Some process is conflicting with LR. The customer support person has no idea what that might be.

Report · Jul 19, 2019

Spoke too soon. After about 2 hrs, the solution started failing as memory usage rapidly climbed. Quitting and restarting LR and it climbed pretty fast. Another theory bites the dust