Lightroom CC 2015.5: Uses all the RAM on my mahcine (Win 7 Pro, 32 GB)

  • 2
  • Problem
  • Updated 1 year ago
  • (Edited)
LR is now using almost all the RAM on my machine.  Only way to recover the RAM is to kill LR.  How do I revert to prior version of LR?

See the attached jpg that shows the Resource Monitor.  The longer LR is open the more RAM it consumes.  
Photo of John Hixon

John Hixon

  • 16 Posts
  • 2 Reply Likes
  • EXTREMELY frustrated that every update of LR comes with horrible issues.

Posted 3 years ago

  • 2
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1490 Posts
  • 471 Reply Likes
Hi John,

Can you help experiment a little bit more? What are you doing in Lightroom when this happens?

See https://helpx.adobe.com/lightroom/kb/lightroom-downloads.html on how to revert back to the specific version of Lr. Basically you uninstall your current version. Download and install the Lr 6.0, and then download and install the specific patch for the minor version.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1490 Posts
  • 471 Reply Likes
The screen cap is very fuzzy to be readable from here.
Photo of John Hixon

John Hixon

  • 16 Posts
  • 2 Reply Likes
All I am doing is importing raw files into the catalog and then converting to DNG on import.  I just imported a couple dozen files after restarting LR, and already LR has consumed a LOT of memory.  Instead of a screenshot I'll post the info right from LR below.  I will be addin more photos tonight so I'll send more screenshots that show the Memory Usage growing until finally I can't use the computer anymore without shutting down LR.  I was wrong when I said I have 32G of RAM.  I have 24 GB of RAM.  

This memory leak is outrageous.  LR is not usable in this release.  Thanks for the info on how to uninstall this 'upgrade'...


Lightroom version: CC 2015.5 [ 1067055 ]License: Creative Cloud
Operating system: Windows 7 
Version: 6.1
Application architecture: x64
System architecture: x64
Logical processor count: 12
Processor speed: 3.2 GHz
Built-in memory: 24574.3 MB
Real memory available to Lightroom: 24574.3 MB
Real memory used by Lightroom: 6650.3 MB (27.0%)
Virtual memory used by Lightroom: 7931.8 MB
Memory cache size: 884.4 MB
Maximum thread count used by Camera Raw: 12
Camera Raw SIMD optimization: SSE2
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080, 2) 1680x1050
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info: 
GeForce GTX 780/PCIe/SSE2

Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 358.91
Renderer: GeForce GTX 780/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler

Config.lua flags: None

Adapter #1: Vendor : 10de
Device : 1004
Subsystem : 104b196e
Revision : a1
Video Memory : 3013
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: LR5x102
Direct2DEnabled: false
GPUDevice: not available
OGLEnabled: true
Photo of John Hixon

John Hixon

  • 16 Posts
  • 2 Reply Likes
I imported a couple dozen more photos.  The memory usage is climbing like a rocket.  I will take a stroll around the neighborhood and snap a few more test photos then import them.  See memory usage below:

Lightroom version: CC 2015.5 [ 1067055 ]License: Creative Cloud
Operating system: Windows 7 
Version: 6.1
Application architecture: x64
System architecture: x64
Logical processor count: 12
Processor speed: 3.2 GHz
Built-in memory: 24574.3 MB
Real memory available to Lightroom: 24574.3 MB
Real memory used by Lightroom: 12204.6 MB (49.6%)
Virtual memory used by Lightroom: 14736.2 MB
Memory cache size: 4185.2 MB
Maximum thread count used by Camera Raw: 12
Camera Raw SIMD optimization: SSE2
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080, 2) 1680x1050
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info: 
GeForce GTX 780/PCIe/SSE2

Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 358.91
Renderer: GeForce GTX 780/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler


Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: C:\Program Files\Adobe\LR_Catalogs\LR4Main_Catalog\Real_LR4_Main_Catalog\Real_LR4_Main_Catalog-2-2.lrcat
Settings Folder: C:\Users\OWNER\AppData\Roaming\Adobe\Lightroom

Config.lua flags: None

Adapter #1: Vendor : 10de
Device : 1004
Subsystem : 104b196e
Revision : a1
Video Memory : 3013
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: LR5x102
Direct2DEnabled: false
GPUDevice: not available
OGLEnabled: true
Photo of John Hixon

John Hixon

  • 16 Posts
  • 2 Reply Likes
OK, all I did was import a couple dozen more photos.  No processing in the develop module, just simply importing photos from a memory card.  At this point I must shut down LR or my computer is very unresponsive.  This is juts nuts.  I've rented a camera and lens for this weekend's New England YMCA Swim Championship Meet, and, instead of spending time getting more familiar with the rented camera, instead I'll be uninstalling and reinstalling LR (and hoping my catalogs remain wholly intact).

I wish there was some alternative to LR.  I'm so tired of the performance of LR getting WORSE and WORSE every release.  It may be time to seriously look at alternatives, but, last time I looked there wasn't any real choice.  Too bad.

Here's where the memory usage is at now, and, all I've done is import maybe 100 photos.  

Lightroom version: CC 2015.5 [ 1067055 ]License: Creative Cloud
Operating system: Windows 7 
Version: 6.1
Application architecture: x64
System architecture: x64
Logical processor count: 12
Processor speed: 3.2 GHz
Built-in memory: 24574.3 MB
Real memory available to Lightroom: 24574.3 MB
Real memory used by Lightroom: 16094.2 MB (65.4%)
Virtual memory used by Lightroom: 19489.3 MB
Memory cache size: 4555.9 MB
Maximum thread count used by Camera Raw: 12
Camera Raw SIMD optimization: SSE2
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080, 2) 1680x1050
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info: 
GeForce GTX 780/PCIe/SSE2

Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 358.91
Renderer: GeForce GTX 780/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler


Application folder: C:\Program Files\Adobe\Adobe Lightroom
Library Path: C:\Program Files\Adobe\LR_Catalogs\LR4Main_Catalog\Real_LR4_Main_Catalog\Real_LR4_Main_Catalog-2-2.lrcat
Settings Folder: C:\Users\OWNER\AppData\Roaming\Adobe\Lightroom

Config.lua flags: None

Adapter #1: Vendor : 10de
Device : 1004
Subsystem : 104b196e
Revision : a1
Video Memory : 3013
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Speakers (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: LR5x102
Direct2DEnabled: false
GPUDevice: not available
OGLEnabled: true
Photo of John Hixon

John Hixon

  • 16 Posts
  • 2 Reply Likes
This is nuts.  I've done nothing more in LR, just left it open.  If I keep the System Info Window open I can see the memory usage slowly increasing.  And, this is with me doing nothing at all.  No keystrokes, nothing.  Just watching the LR memory usage increase.

See memory usage below, after doing nothing at all.  It just keeps growing until the computer is unresponsive.  I can't believe this only affects my PC?

Lightroom version: CC 2015.5 [ 1067055 ]License: Creative Cloud
Operating system: Windows 7 
Version: 6.1
Application architecture: x64
System architecture: x64
Logical processor count: 12
Processor speed: 3.2 GHz
Built-in memory: 24574.3 MB
Real memory available to Lightroom: 24574.3 MB
Real memory used by Lightroom: 17712.6 MB (72.0%)
Virtual memory used by Lightroom: 21518.5 MB
Memory cache size: 4629.0 MB
Maximum thread count used by Camera Raw: 12
Camera Raw SIMD optimization: SSE2
System DPI setting: 96 DPI
Desktop composition enabled: Yes
Displays: 1) 1920x1080, 2) 1680x1050
Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No

Graphics Processor Info: 
GeForce GTX 780/PCIe/SSE2

Check OpenGL support: Passed
Vendor: NVIDIA Corporation
Version: 3.3.0 NVIDIA 358.91
Renderer: GeForce GTX 780/PCIe/SSE2
LanguageVersion: 3.30 NVIDIA via Cg compiler
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1490 Posts
  • 471 Reply Likes
It looks like it there might be some memory leak going on.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1490 Posts
  • 471 Reply Likes
Thanks John. Will do some investigation on our side. In general, Lr could use up to 50% of the total available RAM (i.e. the real memory usage). Since you have 24GB, it might just want to use that. As long as there is no memory leak. That should be fine.
(Edited)
Photo of John Hixon

John Hixon

  • 16 Posts
  • 2 Reply Likes
How can this be fine?  Eventually there is zero memory left, and the computer will not respond to keystroke commands.  The only way to get the computer to respond is to SHUT DOWN LR.  How can this be OK?

Then, once you shut down LR and restart it, the whole process of all the system memory being consumed begins again.  This is a new behavior and is totally UNACCEPTABLE.  
(Edited)
Photo of John Hixon

John Hixon

  • 16 Posts
  • 2 Reply Likes
Is this site part of Adobe?  If not, how do I open a bug report for this memory leak?  I've used LR for years and never run into anything quite this bad?
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1490 Posts
  • 471 Reply Likes
Thanks for the other data point after letting it run overnight. It looks like the RAM usage has stabilized and did not ever growing on itself to claim all the memories.

Our QE are investigating this and try to reproduce, they may come back with questions.
Photo of John Hixon

John Hixon

  • 16 Posts
  • 2 Reply Likes
OM, thanks for the update.  I've taken a vacation day today to get familiar with the cameras we rented for the Swim Meet.  I imported ~ 400 photos and LR was able to handle it, although slowly.  Of course, now I have to SHUT DOWN LR since the memory usage on the computer is at 95%.  Almost all of that is due to good old LR.  This only started happening yesterday after updating LR.



LR also seems to continuously use CPU resources even when it has no work to do.  See bitmap below:



Often I can see no evidence of what the LR PID doing, but, it is often wirting to the LR journal file, or, writing/reading from some DLLs that have nothing to do with my system.  See the bitmap below.  I do NOT have a Wacom Tablet.  I do NOT have the "Ink" tool from Adobe, so, I'm not sure why LR needs to be concerned with those DLLs on my system?



Good luck trying to fix this.  As it is now, I have to continually shut down LR to regain system memory.  This is not tenable long term.  
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 818 Reply Likes
Ink is Microsoft's tablet API, and for some reason the OS thinks you do have some tablet device attached (a touch laptop, maybe?).
Photo of John Hixon

John Hixon

  • 16 Posts
  • 2 Reply Likes
I hope that someone can figure out what is going on, because, this is wholly unacceptable. It sounds like maybe you think things are OK because LR does not consume 100% of the system memory, but, you need to understand that LR consumes memory continually.  Eventually it reaches the point where it consumes FAR TOO MUCH memory, so that LR must be shut down in order to use other applications on the computer.  Below is another bitmap that shows the memory usage at 94%, almost all due to LR.

It does not matter if you are using LR or not, it just keeps eating memory.  I used to keep LR open for weeks at a time, now:  if it is open for more than a few hours, I have to shut it down because it is using all the memory on my computer!

   

So, I trust that you don't consider this to be "Normal".  I've been using LR for many years, and, this is absolutely not normal.
(Edited)
Photo of Geoffrey Phillips

Geoffrey Phillips

  • 15 Posts
  • 0 Reply Likes

Related observations on previous release. Am holding off current as appears too buggy.

Using Win7 64bit 24GB ram.

A) LR tries to create a preview for each photo selected for grid view.  So if I have 'All photographs' set that's 50000+ and will take for ever and a day.  You can see in Task manager that this is happening, ram usage is going up and constant 5% CPU usage.  If select a small or empty folder for grid view the activity stops when all previews are done.

B) With PC NOT connected to the internet and LR otherwise idle and not making previews the Thread count keeps going up about 1 every 10 seconds + ram usage. Have not left this for long but after 20 mins was up to 240.  If connect to the internet this stops and the thread count stabilises.

Have all cloud syncing etc turned off and have Creative Cloud disabled to stop it littering by PC with useless tasks that persist after stop using LR. Most recent file have GPS locations.

Looks to me as if Adobe never test with large catalogs or no internet connection.


Photo of avinash r

avinash r, Employee

  • 24 Posts
  • 5 Reply Likes
Hi John,

Could you please provide an email-id so that we could communicate with you and debug your issue?

Regards,
Avinash
Photo of David Lee

David Lee

  • 5 Posts
  • 0 Reply Likes
I have a similar issue with Lightroom 6.5. Every time I leave it for hours it leaks memory and handles. After 24 hours it was using 680,261 handles and lots of RAM. It's still adding to those numbers. Windows offered to kill the app.

Lightroom version: 6.5 [ 1067055 ]
LanguageVersion: 3.30 NVIDIA via Cg compilerRenderer: GeForce GT 640/PCIe/SSE2Version: 3.3.0 NVIDIA 353.82Vendor: NVIDIA CorporationCheck OpenGL support: PassedGeForce GT 640/PCIe/SSE2Graphics Processor Info: Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: NoDisplays: 1) 2560x1440, 2) 2560x1440Desktop composition enabled: YesSystem DPI setting: 96 DPICamera Raw SIMD optimization: SSE2,AVX,AVX2Maximum thread count used by Camera Raw: 8Memory cache size: 0.0 MBVirtual memory used by Lightroom: 7885.9 MBReal memory used by Lightroom: 2574.6 MB (7.8%)Real memory available to Lightroom: 32706.7 MBBuilt-in memory: 32706.7 MBProcessor speed: 3.4 GHzLogical processor count: 8System architecture: x64Application architecture: x64Version: 10.0Operating system: Windows 10License: Perpetual
Photo of David Lee

David Lee

  • 5 Posts
  • 0 Reply Likes
Almost all of the 680k handles are semaphores and events, if that helps.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1440 Posts
  • 444 Reply Likes
Do you have a network connection when this happens? We did find an issue under this condition (Lr are holding on to threads threads).
(Edited)
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1440 Posts
  • 444 Reply Likes
Also you have use any 3rd party plug-ins? Try disable them to see if it helps. Our automation QE could not reproduce the issue internally.
Photo of David Lee

David Lee

  • 5 Posts
  • 0 Reply Likes
I do have an active network connection when this reproes, and it reproes every time. I am using a few third-party plugins -- Nik primarily. I'll try to see how to disable them without uninstalling them. Several of my co-workers are seeing the same leak -- it's happening for many people on the latest build.
Photo of David Lee

David Lee

  • 5 Posts
  • 0 Reply Likes
See my reply to the response below for a stack that helps explain the leak.
Photo of Steve Sprengel

Steve Sprengel, Champion

  • 2656 Posts
  • 341 Reply Likes

Make sure Face Detection is paused, Address Lookup is paused, and LR Mobile Sync is paused if applicable.  Just to make sure these aren't affecting the memory usage. 

Face Detection uses 10s of MBs per image with my mostly non-people images so maybe if there are people it's finding those could pile up in memory, not sure.  In any case, allocating and freeing the memory per picture may fragment memory. 

I have 80,000 images in my catalog, opened it 10 minutes ago and it's risen from 700MB to 750MB but seems to have settled down, both the handles and the memory, so I don't know as it's going to use up everything if it sits overnight.  I have all the above background processes paused. 

I can imagine a scenario where something in the preview cache is corrupted and LR is seeing an error while trying to compute a preview and tries to regenerate the same preview over and over and not cleaning up since the process is aborting prematurely.  A way to test for this would be to create an entirely new catalog and just let that sit, then import a few photos, and let it sit some more and see if the behavior changes. 

I can also imagine some problem if there is a video in one of the folders that is causing an error somehow and LR retrying to scan it or do whatever it does with videos over and over and losing memory each time due to aborting the process due to an error.

One more thing to check, disable any Auto Import that is configured, in case LR is actually checking for imports every few seconds and that process is eating memory.

It would be interesting to hear from Simon on what happened with the original poster's situation when instrumentation was attached to the LR process and things debugged.

(Edited)
Photo of David Lee

David Lee

  • 5 Posts
  • 0 Reply Likes
I believe it is related to trying to create a preview for a video. A thread is continually in a loop like this:
0:017> k
Child-SP          RetAddr           Call Site
00000000`20f8f188 00007ffa`7e7e6e33 msxml3!Document::loadXML
00000000`20f8f190 00007ffa`9f19148c msxml3!DOMDocumentWrapper::loadXML+0x93
00000000`20f8f200 00007ffa`9f192d08 xml_toolkit!StTempLuaState::`default constructor closure'+0x33c
00000000`20f8f2b0 00007ffa`87982a66 xml_toolkit!private_load_AgXML+0x158
00000000`20f8f300 00007ffa`879a1988 AgKernel!lua_getinfo+0x926
00000000`20f8f340 00007ffa`879838d1 AgKernel!luaopen_table+0x3628
00000000`20f8f4c0 00007ffa`879b52e2 AgKernel!lua_yield+0x201
00000000`20f8f4f0 00007ffa`8798378e AgKernel!AgThrowProgramError+0x42
00000000`20f8f540 00007ffa`87977873 AgKernel!lua_yield+0xbe
00000000`20f8f590 00007ffa`87982a66 AgKernel!luaopen_base+0x1343
00000000`20f8f5e0 00007ffa`879a1988 AgKernel!lua_getinfo+0x926
00000000`20f8f620 00007ffa`879838d1 AgKernel!luaopen_table+0x3628
00000000`20f8f7a0 00007ffa`879b52e2 AgKernel!lua_yield+0x201
00000000`20f8f7d0 00007ffa`8798378e AgKernel!AgThrowProgramError+0x42
00000000`20f8f820 00007ffa`87977873 AgKernel!lua_yield+0xbe
00000000`20f8f870 00007ffa`87982a66 AgKernel!luaopen_base+0x1343
00000000`20f8f8c0 00007ffa`879a1988 AgKernel!lua_getinfo+0x926
00000000`20f8f900 00007ffa`879838d1 AgKernel!luaopen_table+0x3628
00000000`20f8fa80 00007ffa`879b52e2 AgKernel!lua_yield+0x201
00000000`20f8fab0 00007ffa`8798378e AgKernel!AgThrowProgramError+0x42
00000000`20f8fb00 00007ffa`87977873 AgKernel!lua_yield+0xbe
00000000`20f8fb50 00007ffa`87982a66 AgKernel!luaopen_base+0x1343
00000000`20f8fba0 00007ffa`879838c2 AgKernel!lua_getinfo+0x926
00000000`20f8fbe0 00007ffa`879bf2a7 AgKernel!lua_yield+0x1f2
00000000`20f8fc10 00007ffa`87982a66 AgKernel!AgLua_callWithAutoReleasePool+0x37
00000000`20f8fc40 00007ffa`879a1988 AgKernel!lua_getinfo+0x926
00000000`20f8fc80 00007ffa`879838d1 AgKernel!luaopen_table+0x3628
00000000`20f8fe00 00007ffa`879b52e2 AgKernel!lua_yield+0x201
00000000`20f8fe30 00007ffa`8798378e AgKernel!AgThrowProgramError+0x42
00000000`20f8fe80 00007ffa`87973060 AgKernel!lua_yield+0xbe
00000000`20f8fed0 00007ffa`8819a1c2 AgKernel!lua_pcall+0x60
00000000`20f8ff20 00007ffa`a9218102 substrate!AgMainThreadAction_trigger+0x552
00000000`20f8ff60 00007ffa`abcfc5b4 KERNEL32!BaseThreadInitThunk+0x22
00000000`20f8ff90 00000000`00000000 ntdll!RtlUserThreadStart+0x34

The XML it's passing refers to a cache for one of my video files:

0:017> du @rdx
00000000`73075ec8  "<?xml version="1.0" encoding="UT"
00000000`73075f08  "F-8"?>.<PremiereData Version="3""
00000000`73075f48  ">.  <MediaAcceleratorDatabaseEntr"
00000000`73075f88  "y ObjectRef="1"/>.  <MediaAcceler"
00000000`73075fc8  "atorDatabaseEntry ObjectID="1" C"
00000000`73076008  "lassID="e727e14d-731c-47f8-9d24-"
00000000`73076048  "2cb69e8c5323" Version="3">.         <It"
00000000`73076088  "em.CanBeCopied1>false</Item.CanB"
00000000`730760c8  "eCopied1>.          <Stream.ID1>0</Strea"
00000000`73076108  "m.ID1>.             <Item.Count1>1</Item.Co"
00000000`73076148  "unt1>.              <Item.Path1>C:\Users\Dav"
00000000`73076188  "id\AppData\Local\Adobe\Lightroom"
0:017> du
00000000`730761c8  "\Caches\Video\Media Cache Files\"
00000000`73076208  "Videomp24x3NTSC720x480-09895c9f-"
00000000`73076248  "2559-d8ae-4739-1aec000001e9.ims<"
00000000`73076288  "/Item.Path1>.               <Item.Key1>ims</I"
00000000`730762c8  "tem.Key1>.          <Item.ModDate1 Encod"
00000000`73076308  "ing="base64" Checksum="101047810"
00000000`73076348  "7">xAxKyo/OzwE=</Item.ModDate1>."
00000000`73076388  "            <Item.ContentState>375fa587-b6"
00000000`730763c8  "fc-ecfb-43fe-a0ef000000fe</Item."
00000000`73076408  "ContentState>.              <Stream.Count>1<"
00000000`73076448  "/Stream.Count>.             <OriginalPath>\"
00000000`73076488  "\?\C:\Users\David\Documents\My D"
0:017> du
00000000`730764c8  "VDs\buffy minus one\Sources\Vide"
00000000`73076508  "omp24x3NTSC720x480.mpg</Original"
00000000`73076548  "Path>.      </MediaAcceleratorDatabas"
00000000`73076588  "eEntry>.</PremiereData>."

the .dvd files in this diretory look like 44k metadata files for DVDs I've made in the past.

That loop creats events and from what I can tell leaks them.
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1483 Posts
  • 467 Reply Likes
Hi David,

What happens if you rename "C:\Users\David\AppData\Local\Adobe\Lightroom\Caches\Video\" to "C:\Users\David\AppData\Local\Adobe\Lightroom\Caches\Video.old\" and see what happens?
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1483 Posts
  • 467 Reply Likes
Also, before you rename the video cache folder and when you are still able to reproduce the issue, could you follow https://support.microsoft.com/en-us/kb/931673 to create a dump file for us to inspect?

Also could you also collect the Lightroom traceback log by following https://forums.adobe.com/thread/925598. We should be able to figure out the what's happening based on that.

Please share the dump file and the traceback logs online via dropbox or something else. Thanks.
(Edited)
Photo of Jan Prawdzik

Jan Prawdzik

  • 1 Post
  • 0 Reply Likes
Guys, I have the exact same problem. It just eats up all my RAM. This is a pretty recent issue, as I also have been using LR forever and this is the first time this happens. I have the latest CC version. 
Photo of Karl

Karl

  • 18 Posts
  • 2 Reply Likes
Hi

I am presuming that you have a custom build PC, not an OEM in my next points. I have a similar system in spec, just a different gfx card &.it used to struggle at LR4, that machine sits in the corner not used these days.

FYI LR catalog uses RAM, as you have loads, I can presume everything else uses either CPU or GPU Horsepower, as we are talking massive numbers of computations just for one image. A memory leakage would effect more than a program, as you are referring to a coding term, I feel that windows security centre or system log would throw something up & Also it would crash.

I would check your bios & drivers, then windows updates, then presuming you are HDD not SSD, perform a hard drive check, read & write speeds, if you are having large data stuck in RAM, this is hardware & driver related, especially if you move large of files round, also switch off any windows related search functions. Also do not use windows tools for hardware, they lie, have done since windows 95.

Please post the size of LR Catalog and other associated folders in thread & also number of images currently in LR Catalog and I will confirm if Catalog is corrupt.
Photo of Isabella Harrex

Isabella Harrex

  • 1 Post
  • 0 Reply Likes
I have the exact same issue. LR is chewing up 16GB of ram on import dialogue and my iMac grinds to a halt. Again, never used to have this issue, it's seriously making me insane and I'm looking at buying Capture One instead!!