Lightroom Classic: Mac crashes while exporting images

  • 1
  • Problem
  • Updated 3 months ago
  • Not a Problem
  • (Edited)
MacBook Pro (15-inch, 2016) macOS Mojave 10.14.5.
2,6GHz i7, 16GB RAM, Intel HD Graphics 530 1536MB.

I've been using LR since beta without problems. This week LR Classic started to crash every time I try to export images, sometimes it also crashes while editing pictures.

Somtetimes only the app crashes, most of the time the whole computer restarts. 

I have tried to turn off GPU in preferences. I have tried to uninstall the app and re-install.

This is service affecting and needs to be fixed immediately. 
Photo of Per Arne Kvamsø

Per Arne Kvamsø

  • 5 Posts
  • 3 Reply Likes
  • frustrated, stressed

Posted 1 year ago

  • 1
Photo of SatishT

SatishT, Employee

  • 108 Posts
  • 44 Reply Likes
Hi,
We could not find any crashes reports tagged with your emailaddress registered on this forum. If Lr crashes next time, add your emailaddress in the crash report so that we can identify your crash report and debugthe issue.

You can reference https://helpx.adobe.com/photoshop/kb/submit-crash-reports.html for more details.

-Satish
Photo of Per Arne Kvamsø

Per Arne Kvamsø

  • 5 Posts
  • 3 Reply Likes
I created a fresh catalog and imported some pictures. LR crashed while I was sorting through the pictures. Crash-report is tagged with my email. I hope you can figure out what is wrong. Thank you. 
Photo of Carlos Cardona

Carlos Cardona

  • 792 Posts
  • 151 Reply Likes
Did you do the “once over”?
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1743 Posts
  • 603 Reply Likes
Yes please submit your Lr crash report with your email address.

It could be a hardware issue (bad RAM memory/disk).
Photo of Carlos Cardona

Carlos Cardona

  • 793 Posts
  • 152 Reply Likes
Since this doesn't happen to everyone, it's probably not a bug, but an OS issue on your Mac. I was a Mac IT pro for 25 years. It may be a corrupt cache or application state, or directory damage. Please give your Mac the "once over"! Run the free Onyx (https://www.titanium-software.fr/en/o...), reboot. (In Onyx just run almost everything in the Maintenance tab, deselecting things you may not want deleted, like Launch Services . Hit the "Options" button and deselect more stuff like Cookies & Other Site Data, Browser History, Form Values, etc.), then hit Run Tasks. After it's done it will ask for a reboot. 

If that doesn’t fix it run Disk Warrior if you can ($120), (https://www.alsoft.com), reboot. If you can’t do Disk Warrior, at least run First Aid from Disk Utility. Also just doing a "Safe Boot" can clear out caches (restart, hold down shift until you see "Safe Boot" on the screen, then reboot normally. 

If that doesn’t work try launching Lightroom from your other (admin or test) account, with a new catalog, as a test. Does it run OK? If it does it may be a corrupted preference in your Username/Library folder. Check The Lightroom Queen site for instructions on how to reset your preferences (https://www.lightroomqueen.com).

Let me know.

Photo of Per Arne Kvamsø

Per Arne Kvamsø

  • 5 Posts
  • 3 Reply Likes
Thank you, I will try to do your recommendations and let you know how it goes. 
Photo of Simon Chen

Simon Chen, Principal Computer Scientist

  • 1743 Posts
  • 603 Reply Likes
Looked at the two crash logs that you have submitted. Lr crashed at two different places but all seems related to reading JPEG previews from the preview cache db or Nikon raw files.

The macOS CoreGraphics API is implicated in one of the crashes. That is odd. I would say either the files are corrupted on the disk or there is some disk controller issues.

Given that you have created a brand new catalog and new set of photo files, and Lr still crashes. It is either the disk or the disk controller is flaky. Is the disk an internal drive? Try a new catalog and put it and the image assets on a different drive and see if it makes a difference. Is the cable secured?



====================

Crashed Thread:        27  Queue Processor - RenderQueue_ReadPreview


Exception Type:        EXC_BAD_INSTRUCTION (SIGILL)

Exception Codes:       0x0000000000000001, 0x0000000000000000

Exception Note:        EXC_CORPSE_NOTIFY


Termination Signal:    Illegal instruction: 4

Termination Reason:    Namespace SIGNAL, Code 0x4

Terminating Process:   exc handler [2552]




0   libsystem_malloc.dylib        0x00007fff619153eb nanov2_allocate_from_block + 615

1   libsystem_malloc.dylib        0x00007fff61914a61 nanov2_allocate + 130

2   libsystem_malloc.dylib        0x00007fff6191498e nanov2_malloc + 56

3   libsystem_malloc.dylib        0x00007fff61907dfd malloc_zone_malloc + 103

4   com.apple.CoreFoundation      0x00007fff357ffb0e __CFBasicHashRehash + 303

5   com.apple.CoreFoundation      0x00007fff358f44f1 __CFBasicHashAddValue + 89

6   com.apple.CoreFoundation      0x00007fff357fe180 CFDictionarySetValue + 187

7   com.apple.ImageIO.framework   0x00007fff38237ec0 IIOImagePlus::setGeometry(void*, CGImagePlusGeometry) + 1626

8   com.apple.ImageIO.framework   0x00007fff38237733 IIOReadPlugin::prepareGeometry(InfoRec*) + 871

9   com.apple.ImageIO.framework   0x00007fff382b8dde IIOReadPlugin::setupImageProviderCallbackV2(InfoRec*, CGImageBlockSet* (*)(void*, CGImageProvider*, CGRect, CGSize, __CFDictionary const*), __IOSurface* (*)(void*, CGImageProvider*, __CFDictionary const*)) + 28

10  com.apple.ImageIO.framework   0x00007fff382371df IIOReadPlugin::postInitialize(IIODictionary*) + 423

11  com.apple.ImageIO.framework   0x00007fff3822d792 IIOReadPlugin::callInitialize() + 312

12  com.apple.ImageIO.framework   0x00007fff3822d23c IIO_Reader_AppleJPEG::initImageAtOffset(CGImagePlugin*, unsigned long, unsigned long, unsigned long) + 112

13  com.apple.ImageIO.framework   0x00007fff3822bb2e IIOImageSource::makeImagePlus(unsigned long, IIODictionary*) + 474

14  com.apple.ImageIO.framework   0x00007fff3823c1ab IIOImageSource::createImageAtIndex(unsigned long, IIODictionary*) + 61

15  com.apple.ImageIO.framework   0x00007fff3823c0b2 CGImageSourceCreateImageAtIndex + 237

16  com.apple.CoreGraphics        0x00007fff35d3bb11 CGImageCreateWithJPEGDataProvider2 + 159



(Edited)
Photo of Carlos Cardona

Carlos Cardona

  • 793 Posts
  • 152 Reply Likes
Or try Disk Warrior to fix the damaged directory? Then see if those jpgs are still there or those sectors were mapped out as bad.
Photo of Per Arne Kvamsø

Per Arne Kvamsø

  • 5 Posts
  • 3 Reply Likes
I sent the computer to service. It is bad RAM, so they are changing the entire main board because the Ram is welded directly in the main board. Thank you for troubleshooting, I hope this will fix the issue.
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 16861 Posts
  • 2828 Reply Likes
Thanks for closing the loop. Not surprising it was a hardware issue. A system crash/restart usually means a low level failure such as a driver (bad video card driver, etc), failing hardware (hard disk, video card, etc.) or damaged OS installation.
Photo of Srdjan Petrovic

Srdjan Petrovic

  • 5 Posts
  • 0 Reply Likes
Hi, I also have the same problem on iMac 27" 5K late 2015 I use 32gb RAM OWC.
From the beginning when I bought the iMac, I also ordered the extra ram memory that I replaced with the original one, I do not remember well enough, but I think it was a period when the problems started.
I thought it was a different kind of problem, namely that it was software or an operating system. After many upgrades, I realized that it was not a problem, and my negligence was well deserved because I did not wear the service until a few days ago.
Authorized service said that the diagnostics they did show no hardware errors. That is, everything is ok. 
Before going to the service I tried to test the ram memory myself by individually removing and returning it, I came to the conclusion that a single memory is problematic. However, after a few months, the problem continued. And I returned a memory that seemed problematic to me. 
I installed Windows 10 on iMac and also tried to export photos through it and the same problem happened, iMac restarted.
I tried several times to install a fresh system( from Siera to Catalina), everything was reset to factory settings and again there were problems with them.
Now I tried with external hard disk, to install OS on it and through it to try to export the photo, for now everything works ok, but it scares me not to be the same problem again as it was with ram memory, some time ok then after problems again.

Do you have any advice on what to do?
Photo of Carlos Cardona

Carlos Cardona

  • 714 Posts
  • 139 Reply Likes
You tried to export the photos THROUGH Lightroom in Windows 10 THROUGH the Mac OS? You're just asking for trouble there! Keep it simple!
(Edited)
Photo of Srdjan Petrovic

Srdjan Petrovic

  • 5 Posts
  • 0 Reply Likes
"I tried several times to install a fresh system( from Siera to Catalina), everything was reset to factory settings and again there were problems with them.
I installed Windows 10 on iMac and also tried to export photos through it and the same problem happened, iMac restarted."


I tried not because I wanted to, but I wanted to remove the suspicion that there was a problem with mac OS. 
Photo of Carlos Cardona

Carlos Cardona

  • 714 Posts
  • 139 Reply Likes
That's like: I want to remove the suspicion that juggling 22 balls is hard, so I'll only juggle 21 balls! No. Using a separate Windows PC to do it, (not a Mac emulating Windows), would prove whether there was a Mac OS problem or not.
Photo of Srdjan Petrovic

Srdjan Petrovic

  • 5 Posts
  • 0 Reply Likes
I'm pretty sure you're wrong. Too many times it has happened that Apple updates OS with the problems they solve afterwards, especially the latest OS Catalina. If the problem were in any hardware, it would manifest itself on the Windows system as well as the mac OS. As it was the case ...
If it is a sin to use Windows on a but champ assistant, why Apple allowed it? 
Photo of Carlos Cardona

Carlos Cardona

  • 714 Posts
  • 139 Reply Likes
It's not a sin, it's just the more balls in the air the greater likelihood the OS will drop one!
Photo of Per Arne Kvamsø

Per Arne Kvamsø

  • 5 Posts
  • 3 Reply Likes
My problem was fixed when the dealer replaced the bad ram. Sorry, I don’t have any more advice for you.
Photo of Srdjan Petrovic

Srdjan Petrovic

  • 5 Posts
  • 0 Reply Likes
For the last two days I don't even know what I didn't do, I'm literally testing it myself.
I use memtest86 to detect if there is a problem on the RAM , there are errors on 3 memory out of 4. I thought great, but then it occurred to me to put that memory, which turned out to be good, into another slot...an error occurred. So now I have tried several times to insert different slots into different memory, somehow I managed to combine two memories to work one in slot 1 the other in slot 3.... 
I'm just testing it and I'll be doing it for the next couple of days, if everything turns out fine, I won't even return the other 16gb RAM.
Photo of Srdjan Petrovic

Srdjan Petrovic

  • 5 Posts
  • 0 Reply Likes
But all in all a huge headache around the Apple.
Photo of Rikk Flohr

Rikk Flohr, Official Rep

  • 7718 Posts
  • 1780 Reply Likes
I've reviewed the four crash reports associated with your email. They indicate you are using 9.2. Can you update to the latest, 9.2.1 and see if you are still crashing. I would recommend a clean install. 


Clean Classic Install Procedure
  • Close Lightroom
  • Restart the computer
  • Use the Adobe Creative Cloud App to uninstall Lightroom Classic
  • Restart the computer
  • Install Lightroom Classic via the Creative Cloud App without launching any other programs.
  • Restart the computer
  • Launch Lightroom
  • Wait 5 minutes 
(Edited)
Photo of Srdjan Petrovic

Srdjan Petrovic

  • 1 Post
  • 3 Reply Likes
It's been a long time since I had the problem about 3 years, so I update to 9.2.1. I'm sure nothing will help. 
I think I found a problem, I'm still testing but I think it's a problem with RAM. 
I removed 16gb and there is 16gb left but 8 in A1 port and 8 in B1 port. That's just how I managed it to work, now whether it's a problem in RAM or the motherboard so the slots are bad, I don't know. For now, it works.
Photo of Carlos Cardona

Carlos Cardona

  • 793 Posts
  • 152 Reply Likes
You may want to replace those 16GB with new chips later, jus' saying!