LrC 10.2 crashes on first Map access after Import, Mac OS Big Sur 11.2.3

Well, just when I thought I had the problem cracked exactly the same problem happened when I added RAW files to my newly created catalogue, only for it to crash immediately I entered the Map module! So, following the steps outlined to me by Adobe Support yesterday, I created a new catalogue, imported the RAW files and went to Map module, only for it to crash again - in a brand new catalogue! 

So it seems as if that workaround isn't a workaround, or at least not for long! I shall be contacting Adobe again today to see if they have any more bright ideas.

Reiterating what John Rellis said above. Please add problem details to the bug report at https://feedback.photoshop.com/conversations/lightroom-classic/lrc-crashes-upon-first-access-to-map-module-after-import/60686e00439e980adff75d76. I'm not sure they are used but it is most likely a good idea to send those crash dialogs in to Adobe when the crash occurs as well. Thanks All!

With regard to the Map module problems associated with Lightroom Classic (macOS 11.2.3 Big Sur), when Lightroom crashes immediately after importing new files (NEF & DNG) and then going to the Map module from either the Library or Develop modules, I just had the following exchange with Adobe, which has cured the issue:

Adobe: Thanks can you create a new catalog import the images try to work and see if it crashes?

Me: Yes, problem seems to be solved.

Adobe: Thanks, so you can import old catalog here and check it?

Me: Yes I have and it worked perfectly.

I hope that this helps others as it's a simple cure.

Adobe: OK. Then it’s fine. Also open system preferences and Go to: Security and privacy >privacy >full disk access>unlock it.unlock button is on bottom left once it is unlocked click the + sign and browse to Lightroom Classic and add it and check LR as sometimes they get corrupted and it happens.

I entered the following over on the bug report:

Further testing: I am usually using a Nikon Z 6II so I tried my D750 and results were exactly the same. I normally use Copy as DNG during import so I tried simply Copy and I received the same results, so it doesn't matter if I have DNG or NEF files when I select the Map module.

I wanted to include a NEF file so engineering has something handy to play with, but I don't know how to provide a NEF image. It seems that you are limited to JPEG/PNG/etc. In any case, I do not believe that the problem is image specific anyway. Instead it must have something to do with process or library.

Hi there, I'm seeing this behaviour too, LrC 10.2, MacBook Pro 13" late 2013 running Big Sur 11.2.3. It's really frustrating. It makes no difference what I import - it seems to be any files, I'm using NEFs from a D700 and D810 so nothing new and exotic there. It happens consistently and every time; when I restart Lightroom the Map module works fine.

I've tried reinstalling LrC to no avail, however I haven't reset my preferences file.

John, Thanks for that. I created a report there.

"I again processed an Import today and followed that with a Map module access that caused LrC to crash once again."

Sigh, that's too bad.  It's certainly possible the problem is unrelated to LR preferences and that simply restarting LR (which you do when you reset preferences) makes the problem less likely to occur for a while.

"I won't be able to try tech support again before next week."

Beware that Adobe tech support has a very bad reputation, especially for issues that are not well-understood and documented. They tend to say anything to close out a call they can't resolve.

"Interesting to see that I am no longer the only user with this issue. Can it be that few people are using Map module?"

Based on all the posts over the years in LR forums, I think a large fraction of LR users actively use the Map module (I do).  Typically, if a release introduces a problem in a well-used feature, we'll see lots and lots of posts about it.  I'm a moderator in three LR forums, and yours is the only thread I've seen about this in the last many months.  

I just searched the official feedback forum again and didn't see any similar bug reports in the past four months.  It's possible but less likely that I missed some (the forum's own search is horrendus, but I used Google site search instead).  So I encourage you to post a bug report:

https://www.lightroomqueen.com/send-bug-report-feature-request-adobe/ 

That provides a central placer for aggregating additional reports of similar symptoms. Adobe developers actively participate in that forum but are rarely seen here. They read everything posted there and sometimes engage.

I again processed an Import today and followed that with a Map module access that caused LrC to crash once again. Resetting Preferences has clearly not worked and it is unclear why it worked while the Adobe Tech was on the phone with me. I won't be able to try tech support again before next week.

Interesting to see that I am no longer the only user with this issue. Can it be that few people are using Map module?

Using a 2020 iMac 27" with the latest version of LR Classic and a 2019 MacBook Pro with the same, both running mcOS 11.2.3 Big Sur, I have exactly the same issue. Clicking on the Map module for the first time after importing files causes an immediate crash. Relaunching the application and clicking on the Map module works perfectly. I've sent off numerous bug reports to Adobe but nothing has happened!

Glad you got it resolved.