M

2 Messages

 • 

88 Points

Sat, Dec 12, 2020 6:47 PM

Lightroom Classic: version 6 crashes in the facial recognition module

Since a week my Lightroom crashes when opening the facial recognition modul. Program closes. 

I am working with Windows 10. 

I do not know. Mayby it has something to do with the latest Windows Update: 8. Dezember 2020 – KB4592438 (Betriebssystembuilds 19041.685 und 19042.685

Or it has something to do with the Installation of Photoshop Elements 2021 / Adobe Premiere Elements 2021

6 Messages

 • 

110 Points

10 m ago

Hi everyone,

I have the problem that switching to the "facial recognition" modul since ~ 2 weeks reproducibly leads to a program crash of my Lightroom 6.14 (under Windows).

De-installation and new installation did not help.

It has worked before.

Any idea what I could try besides a new setup of the whole computer ? E.g. specific registry entries to check ?

Many thanks in advance for your help

Ulf

Note: This comment was created from a merged conversation originally titled switch to "Facial Recognistion" leads to program crash, Lightroom 6

Adobe Administrator

 • 

1.2K Messages

 • 

20.3K Points

This thread is being merged into an existing thread for better tracking and response.

6 Messages

 • 

110 Points

10 m ago

If it is not a technical problem caused by a windows update, but just the expiry of a face recognition license Adobe got from a 3rd party, I assume that at least according to German law, Adobe has to fix it for 7 years starting from the purchase of the product.

Let´s hope Adobe gets enough negative comments to rethink their current behavior!

6 Messages

 • 

120 Points

Hi Ulf, was ist denn hier die Rechtsgrundlage? Müsste man Adobe vielleicht mal zurufen?

@non german speaking: I just asked for the law, which regulates this.

3 Messages

 • 

82 Points

Adobe simply don’t care. They are interested to make money with professionals, which use typically the subscription model and don’t face an issue. If a few people file a lawsuit, it is just noise for them and in worst case, they will refund the purchase price. So, from financial point of view a very low risk.

It is for sure dishonourable, but it look like that it matches there company values.

Just an example from a company with values:

I still  use a 8 year old tablet and still get security updates, also if OS updates are discontinued since 2 years. And for sure all functions are still working.

Nevertheless, Adobes behaviour should be a warning to all professionals, how Adobe treats customers.

9 Messages

 • 

162 Points

Meanwhile "RunAsDate" can help.

TML59

48 Messages

 • 

548 Points

Yes, that is a workaround shared already here. Thank you.

6 Messages

 • 

110 Points

10 m ago

Juste for the record, I downloaded libfrsdk-8.6.0.dll from different locations (www.dllme.com, www.pconlife.com, www.exefiles.com, ...) and replaced the faulty version in my Lightroom installation folder.

This does not fix the issue.

TML59

48 Messages

 • 

548 Points

Makes sense to me, if you replace the file with the same one... ;-)

6 Messages

 • 

110 Points

I just hoped the dll could be found without expiration date, as Adobe did not  build the file themselves. Maybe the file could have been found in an unlimited version elsewhere, who knows... 

TML59

48 Messages

 • 

548 Points

Ah, OK. Makes sense. Good try! Thanks :)

2 Messages

 • 

72 Points

10 m ago

The problem is not with the Cognitec DLL, but with the Adobe code calling it. For whatever reason, the Adobe CIT plugin is calling the FRsdk::FIRBuilder::buildVoidFIR() method of the DLL with a NULL pointer, at least on my Mac, so it's going to crash no matter what. Why the Lightroom code generates this NULL pointer depending on the date is beyond my feeble reverse-engineering skills, but it does not look like a licensing issue.

Arguably it is a logic bomb from Adobe, but good luck holding a large well-lawyered corporation accountable in America, or even Europe. This is forcing me to accelerate my migration to DarkTable (after Adobe stabbing us in the back, there is no way I am going to hold my photos and workflow hostage to non-open-source apps again, even from more honorable companies like Serif/Affinity), and this is proving much harder than my previous migration from Aperture to LR.

Here is the crash reason:

Crashed Thread:        28  Worker Thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [12123]

and the relevant backtrace:

Thread 28 Crashed:: Worker Thread
0   libfrsdk-8.6.0.so             	0x00000001214989df FRsdk::FIRBuilder::buildVoidFIR() const + 31
1   com.adobe.CIT.plugins.FaceRecognitionCognitec	0x000000010eb7b345 0x10eb6e000 + 54085
2   com.adobe.CIT.plugins.FaceRecognitionCognitec	0x000000010eb792e0 0x10eb6e000 + 45792
3   com.adobe.CIT.plugins.FaceRecognitionCognitec	0x000000010eb7c27b 0x10eb6e000 + 57979
4   com.adobe.CIT.plugins.FaceRecognitionCognitec	0x000000010eb804c2 0x10eb6e000 + 74946
5   com.adobe.CIT.plugins.FaceRecognitionCognitec	0x000000010eb823c2 0x10eb6e000 + 82882
6   com.adobe.CIT                 	0x0000000110dea542 CIT::PluginInstance::DoFeatureAlgorithmRequest(char const*, CIT::DataCacheEx*, void*, int, void**, int*, CIT::IPluginHost*) + 162
7   com.adobe.CIT                 	0x0000000110df945f CIT::Task::DoTaskInternal(double, CIT::CitError&) + 1183
8   com.adobe.CIT                 	0x0000000110df8c83 CIT::Task::DoTask() + 131
9   com.adobe.CIT                 	0x0000000110dd662d CIT::CITManager::HandleCachedTaskRequest(std::tr1::shared_ptr<CIT::Connector>, CIT::UTF8String const&, CIT::PropertyList&, CIT::PropertyList&, bool&) + 1965
10  com.adobe.CIT                 	0x0000000110dd5834 CIT::CITManager::HandleRequest(std::tr1::shared_ptr<CIT::Connector>, CIT::PropertyList&, CIT::PropertyList&) + 404
11  com.adobe.CIT                 	0x0000000110de1b08 CIT::Connector::SendRequest(CIT::PropertyList&, CIT::PropertyList&) + 88
12  com.adobe.CIT                 	0x0000000110de25ff CIT::Connector::CallFeatureAlgorithmSync(unsigned char const*, char const*, CIT::PropertyList&, CIT::PropertyList&, unsigned char const*) + 415
13  com.adobe.CIT                 	0x0000000110d91476 WConnector_CallFeatureAlgorithmSync_1 + 166
14  com.adobe.ag.imageanalysis    	0x000000010fb82a1d 0x10fb5a000 + 166429
15  com.adobe.ag.imageanalysis    	0x000000010fb6cf76 0x10fb5a000 + 77686
16  com.adobe.ag.imageanalysis    	0x000000010fb6c9d0 0x10fb5a000 + 76240
17  com.adobe.ag.imageanalysis    	0x000000010fb6b7ee 0x10fb5a000 + 71662
18  com.adobe.ag.imageanalysis    	0x000000010fb67c01 0x10fb5a000 + 56321
19  com.adobe.ag.imageanalysis    	0x000000010fb715fb 0x10fb5a000 + 95739
20  com.adobe.ag.imageanalysis    	0x000000010fb782b7 0x10fb5a000 + 123575
21  com.adobe.ag.kernel           	0x00000001072e7e75 0x1072de000 + 40565
22  com.adobe.ag.kernel           	0x00000001072f65bd 0x1072de000 + 99773
23  com.adobe.ag.kernel           	0x00000001072e8141 0x1072de000 + 41281
24  com.adobe.ag.kernel           	0x00000001072e77d2 0x1072de000 + 38866
25  com.adobe.ag.kernel           	0x00000001072e839d 0x1072de000 + 41885
26  com.adobe.ag.kernel           	0x00000001072e0002 lua_pcall + 100
27  com.adobe.ag.kernel           	0x00000001072e1d56 0x1072de000 + 15702
28  com.adobe.ag.kernel           	0x00000001072e7e75 0x1072de000 + 40565
29  com.adobe.ag.kernel           	0x00000001072f65bd 0x1072de000 + 99773
30  com.adobe.ag.kernel           	0x00000001072e8141 0x1072de000 + 41281
31  com.adobe.ag.kernel           	0x00000001072e77d2 0x1072de000 + 38866
32  com.adobe.ag.kernel           	0x00000001072e839d 0x1072de000 + 41885
33  com.adobe.ag.kernel           	0x00000001072e0002 lua_pcall + 100
34  com.adobe.ag.kernel           	0x00000001072e1d56 0x1072de000 + 15702
35  com.adobe.ag.kernel           	0x00000001072e7e75 0x1072de000 + 40565
36  com.adobe.ag.kernel           	0x00000001072f65bd 0x1072de000 + 99773
37  com.adobe.ag.kernel           	0x00000001072e8141 0x1072de000 + 41281
38  com.adobe.ag.kernel           	0x00000001072e77d2 0x1072de000 + 38866
39  com.adobe.ag.kernel           	0x00000001072e839d 0x1072de000 + 41885
40  com.adobe.ag.kernel           	0x00000001072e0002 lua_pcall + 100
41  com.adobe.ag.kernel           	0x00000001072e1d56 0x1072de000 + 15702
42  com.adobe.ag.kernel           	0x00000001072e7e75 0x1072de000 + 40565
43  com.adobe.ag.kernel           	0x00000001072e8130 0x1072de000 + 41264
44  com.adobe.ag.kernel           	0x00000001072dff81 lua_call + 37
45  com.adobe.ag.substrate        	0x0000000107444af1 AgLua_callWithAutoReleasePool + 85
46  com.adobe.ag.kernel           	0x00000001072e7e75 0x1072de000 + 40565
47  com.adobe.ag.kernel           	0x00000001072f65bd 0x1072de000 + 99773
48  com.adobe.ag.kernel           	0x00000001072e8141 0x1072de000 + 41281
49  com.adobe.ag.kernel           	0x00000001072e77d2 0x1072de000 + 38866
50  com.adobe.ag.kernel           	0x00000001072e839d 0x1072de000 + 41885
51  com.adobe.ag.kernel           	0x00000001072e0002 lua_pcall + 100
52  com.adobe.ag.substrate        	0x0000000107437f27 0x107425000 + 77607
53  com.apple.Foundation          	0x00007fff38d430a2 __NSThread__start__ + 1194
54  libsystem_pthread.dylib       	0x00007fff62cb22eb _pthread_body + 126
55  libsystem_pthread.dylib       	0x00007fff62cb5249 _pthread_start + 66
56  libsystem_pthread.dylib       	0x00007fff62cb140d thread_start + 13

(edited)

6 Messages

 • 

110 Points

Hi fazalmajid, thank you for your work ! It's a great job having tried to do that. I switched to Lightroom because it was the only software which had profiles for my camera lens.

Now, I understand that I made a mistake.

Do you know if Lightroom catalog can be imported into Darktable ?

(if Darktable is Windows compatible)

2 Messages

 • 

72 Points

@grasdubide (love the handle, being a gros plein de soupe myself)

There is no direct import, but if you have XMP sidecar files enabled in LR, DarkTable will sync the metadata. It's far from perfect, the keyword management in DarkTable seems very clunky (I haven't had time to explore it properly yet). On the plus side, the new version doesn't crash randomly like it did in the last version I tried maybe a year ago.

Camera profiles seem good for the most part, but for really old cameras like my 2001 vintage Canon EOS D30 the colors in DNG conversions are completely off with massive green-cyan color casts (the CRW are fine, so much for DNG as an archival format), but if you actually open the CRW stacked with the DNG the DNG's aberrant color profile gets applied to the CRW and ruins it.

(edited)

TML59

48 Messages

 • 

548 Points

@fazalmajid I believe the problem is with the DLL. Removing the file stops the crash

6 Messages

 • 

110 Points

@TML59, is there a companion file I can delete on a mac?  MacOS doesn't have dll files...

TML59

48 Messages

 • 

548 Points

Try deleting this folder (or what you have on a Mac that looks similar).

No guarantees and make a backup so you can restore the files if this does not help.

C:\Program Files\Adobe\Adobe Lightroom\CIT\Plug-ins\FaceRecognition

11 Messages

 • 

282 Points

10 m ago

I am facing the exact same problem with Lightroom 6.14 on macOS "Mojave" - a supported operating system of Lightroom 6, that is!

I must add that I specifically upgraded to Lightroom 6 (from 4) because of the new face recognition module.

If Adobe is selling a product with a perpetual license, fully aware that the product (parts thereof) will expire (and don't tell me they weren't aware about the time-limited license they made with that German company (https://www.cognitec.com/) that provided the face recognition module), then this is fraud, IMHO. I feel cheated.

So if Adobe would sell a current version of Lightroom Classic with a perpetual license - re-assuring that all licenses are now time-unlimited - I would certainly give them my money!

But after this disaster I am certainly not continuously funding (with a subscription) a product that in the worst case - if Adobe feels like abandonding its development in favour of the latest fancy web-app - stops working again.

Organising my photos is a lifetime investment! It's not about the money only: it is about trust that I can keep using the software for as long as I want and live!

That trust is now gone, unless Adobe gets a grip and re-negotiates the license agreement with that 3rd party and fixes Lightroom 6.14!

(edited)

6 Messages

 • 

110 Points

I feel the same. All the time I spent learning Lightroom (with a payed course), understanding it, using it, with trust in future, is lost.

Switching to another app is really frustrating.

Having the feeling that I lost all this time makes me really angry

2 Messages

 • 

72 Points

Oliver you are so right.

I am just a 'hobby photograph' and don't want a rented software.

(edited)

6 Messages

 • 

110 Points

10 m ago

I am also having this issue, and I'm glad to have found this thread.  I tried the system date trick, and I was able to successfully delete some photos without LR crashing.  (I'm on a MacBook with Mojave, and the same issue persisted on my backup machine, running Sierra).  I have some more tests to see if I can import/delete without changing the date and without crashes.  I've already disabled the auto facial recognition.

The repetitive crashes also had the lovely side effect of corrupting my photo hard drive... a now 4TB headache going on two weeks.  Fortunately, I have everything backed up, but it has illuminated some holes I have in my backup process that I will be rectifying post haste.

Needless to say, I don't want my photo editing software to randomly crash, through no fault of my own, kthxbai :)

6 Messages

 • 

110 Points

Ok, so I’ve messed with this for a few days now, and as long as I change the system date, I can operate LR without crashing. However, that is not a longterm fix. As soon as I set it back, it crashes anytime I try to import or delete photos from my catalog - and facial recognition is disabled. I’m hoping this smart community can find a more permanent workaround!

4 Messages

 • 

80 Points

10 m ago

I am getting kicked out of Lightroom classic every time I go to people mode.  It was working.

Note: This comment was created from a merged conversation originally titled Lightroom Classic: people mode

Adobe Administrator

 • 

563 Messages

 • 

10.2K Points

Which version of Lightroom Classic are you using?

What exactly happens when you select the People view?

Thanks,
Sunil

4 Messages

 • 

80 Points

Version 6.1  I click on 'o', it pulls up the people mode showing different people and in about 2 seconds Lightroom closes.

10 Messages

 • 

154 Points

9 m ago

It's embarassing that Adobe does not WANT to help with that issue. I understand that they won't support new OS or new cameras, etc. but stop working an UNCHANGED system because of a date check is unacceptable for me.

I think many of us have been paying (and would continue to do so) for  new versions every year or two but on a VOLUNTARY base rather than being forced by a rental model. 

3 Messages

 • 

98 Points

@wildf Yes, exactly.  :-)

Champion

 • 

6K Messages

 • 

103.7K Points

9 m ago

Regarding the workaround of changing the computer clock, note that many programs and parts of the operating system itself use time to ensure proper syncing and caching of data and correct networking. They assume that the clock only moves forward ("monotonically increasing").  Moving the clock back, even for a short period of time, opens you up to the risk of mysterious behavior by these programs, including data loss.

10 Messages

 • 

154 Points

@John_R_Ellis 

That's exactly what I am afraid of and why I am looking for a less risky work around.

I guess there is not a chance of creating a Virtual Machine which works with a different system clock which, let's say, would go 10 years back (for an easy math and for giving us enough time to find a new workaround again)?

2 Messages

 • 

70 Points

I'm using a host MacBook with Big Sur - with a virtual machine (Parallels 15 with Mojave OS X) with Lightroom 6.14 and a few other small 32-bit programs.  The virtual machine is ~35GB, and the host MacBook has sufficient resources to run this with 16GB RAM and free SSD space.

- Lightroom catalog (~11GB)  is on the virtual machine drive storage.

- Photo folders (~40K photos) are on the host Mac drive storage, accessed by Lightroom as "Shared Folders"

I change the clock inside the virtual machine to work around the bugs described in this thread. For this I had to change the virtual machine (VM) configuration by closing the VM, editing Parallels Options > More Options > Time: Do not sync, then restart the VM.  I have not changed any DLL files: it's the standard install of Lightroom 6.14.

I use a bash script in the VM to start Lightroom - mentioned earlier in this thread:

#!/bin/bashsudo date 1001083020  # 10-01-2020 08:30open -a "Adobe Lightroom"sleep 30sudo sntp -S time.apple.com

In Lightroom I'm able to sync folders, optimize the catalog, use People face recognition, delete photos, import photos.   Sometimes I disable the sntp command to let some things complete (sync folders, deleting many photos at once, removing missing photos).

After a week of use this seems robust but, like life, who knows what lies ahead :)

(edited)

6 Messages

 • 

110 Points

9 m ago

So someone earlier mentioned an alternate solution to changing the system date is to rename the libfrsdk-8.6.0.dll file, which contains the plugin for the facial recognition.  I personally don't care about this feature; I just want LR to keep working - including imports and virtual copies.  Does anyone know where I can find this file or the corresponding file on a Mac?  TIA

10 Messages

 • 

154 Points

9 m ago

So we have learned that Geolocation had stopped working around 2 years ago and face recognition a month ago.

Is there any other feature or even an essential functionality which has stopped working so far?

I read something about problems with importing new photos or creating virtual copies which I luckily haven't had so far (fingers crossed!)?

I am working on two Macs, both with older operating systems (LR 6.0 with MacOS 10.9 and LR 6.14 with MacOS 10.12).

Please those who are suffering further issues, let me know what those are so that I am getting aware of the full trouble I might be facing as well.

10 Messages

 • 

154 Points

Just another question:

Does anyone of you know any feasible alternative of Lightroom:

- Import of the Lightroom library so that the work of the past years isn't lost (development, keywords, recognized faces)

- Non destructive RAW development and editing

- Smooth workflow with Photoshop (or an alternative as powerful as PS)

- Powerful enough to administrate a database of hundreds of thousands photos

If there was such an alternative I would be very keen to switch.

189 Messages

 • 

4.6K Points

On1 and Capture One both have LR catalog import. They both also will display a very close approximation of your current LR edits. Capture One is the more robust raw developer of the two. Neither have (yet) the robust DAM features of LR, or face detection.

All in all, my fear is that there will come an OS upgrade (win or mac) which will render LR V6.x totally useless and we will be out of luck, permanently. Perhaps caught off guard at a most inconvenient time.

TML59

48 Messages

 • 

548 Points

9 m ago

Stay tuned... I'm still working on something and there might be some light at the end of the tunnel...

9 Messages

 • 

162 Points

May be a good idea was, to send eMails to the support of Adobe.

Thousands of buyers or more can wake them up !?

10 Messages

 • 

154 Points

@TML59 That would be awesome!

Something less risky than manipulating the system date...

Thank you for the effort you are spending for doing what I would expect of Adobe who got hundreds of Euros from each of us over the different versions bought from them:  solving the problem they created.

10 Messages

 • 

154 Points

@Rainer

Unfortunately Adobe doesn‘t care at all about their costumers havi g problems and asking for solutions, not even about their SaaS users which are constantly paying a monthly fee...

It‘s just the ignorance of a quasi monopolist.

But give it a try!

189 Messages

 • 

4.6K Points

@TML59 Gives a hint, please!

TML59

48 Messages

 • 

548 Points

Days... not weeks I hope

189 Messages

 • 

4.6K Points

8 m ago

Taking legal action won't cost us anything if a large law firm takes this on as a class-action lawsuit. They live for things like this. It could be a tasty piece of fruit for them.

3 Messages

 • 

80 Points

8 m ago

I have Lightroom 6.14 installed on my desktop for everyday use & my laptop for when on holidays. Lightroom on the desktop is crashing like everyone elses when using People/Face Recognition and started in December the same. It will work if I change the date back.

 

However the program on the laptop is not crashing at all when using People/Face Recognition.  The laptop has the current date set and works with no manipulation at all. The difference is the laptop has not been online since middle to late last year.

10 Messages

 • 

150 Points

@ALR20 this is very interesting

can you give the os version of each ?

is your laptop on internet now and still working (LR I mean) ?

3 Messages

 • 

80 Points

The desktop is running on Win10, while the laptop is running on Windows 7.  So that is another difference.   I haven't connected the laptop to the internet yet to test if Lightroom works after connecting.   

10 Messages

 • 

150 Points

hope for you it will still work ;)

but otherwise it would be a great discovery

458 Messages

 • 

6.7K Points

I was just about to ask whether any of you had tried running LR 6 on the OS that it was designed to run on. It was never designed to run on Win 10 or the latest MacOS. I see ALR20 above has done that and it works fine! It may run for ever on the OS it was designed for!

Bob Frost

2 Messages

 • 

70 Points

This is indeed promising. When I executed my lightroom.exe in compatibility mode, it did not crash on face module (I have a system date set to current date, the host system is Windows 10 - constantly connected to the Internet).
This could replace my workaround of using RunAsDate - unless it causes other issues.

(edited)

9 Messages

 • 

162 Points

8 m ago

I have the same problem. But the support in Germany told me, it's an old version.

TML59

48 Messages

 • 

548 Points

Adobe support in Germany? Yes, for sure LR6 is an old version. It was the last sold with a perpetual license (one that -if the environment around it doesn't change- should work forever).

The next LR versions are all subscription based and cost >100 / year.

Just so you know: suddenly the face recognition module stopped working last December. As one can restore functionality but resetting the date to a time before Dec 2020, this seems related to a license issue. The latter makes it as least look like we were all sold a license that was called perpetual but in fact was not...