Lightroom: CC 2015.2 on MacOS 10.11 crashes

have you tried downloading and installing the patch from here: http://blogs.adobe.com/lightroomjourn...

That solved the problems! Thanx!

Hi Jeffrey, I celebrated to soon. It keeps crashing :(. I wrote this in the extra information box on the crash report:

"After an warming that another application had changed the metadata, I choosed the option dat the metadata form lightroom should be used. Than it crashed again!" (Checkbox for import photo is still unchecked)

Hi Sid,

There could be some issue when you installed 2015.2.1 installation. Is there any error message when Lr quits? I afraid your most recent issue is unrelated to the crash bugs that we fixed in Lr 6.2.1. Is this on Windows or Mac? Is there any error message in the console? Does Lr 6.2.1 just quit or crash? Is there any crash logs that you can share and send to Adobe?

Simon do you realize that D mode on machines lacking external processor is massively slower in LRCC than in LR 5.7? Please give top priority to fixing this. Stop messing with new features and interfaces until you make LRCC D mide usable again. Macbook pro 2015 13" 16g 1TB ssd. Yes i have tried unchecking the graphics box. No diff.

Simon - I have been sending the error logs all the times, to both Apple and Adobe. I can at least start Lightroom after the fix provided by Victoria. I am not sure what's going on but if I have a different problem then it shouldn't be resolved by the fix provided in this thread. I am pretty sure the startup crash is very related.

@Sid Good to hear at least you're up and running.


@Art You meant the Develop module is slower in LRCC than in LR 5.7 for you? For machines lacking external processor, do you mean lacking Graphics Processor (GPU)?

Yes precisely. Lacking external graphics processor. While drawing an area for cropping for example, their was no hesitation in 5.7. Now with LRCC there is a long lag (seconds). BTW I have not installed any of the updates of the past few weeks due to warnings by Laura Shoe. Thumbs up to Laura! Macbook Pro 13" 2015 16gig 1TB SSD. I update ooerating system etc obsessively, all current except for LRCC.

And checking or unchecking the graphics processor box makes no diff.

You have a fairly recent machine. There is no reason why the develop module is running slow for you. Can you post your system configuration from the system info dialog? and describe what aspect of the develop module that is particularly slow for you?

Simon I will address your questions but first note, more importantly, that I am far from alone. Look at item #23 on this thread, which I site below. This is the ".1" version before the .2 with all the crashes.

Has there been a radical change in the team that does your development or testing? Did you move development offshore or lose key people?

https://photographylife.com/lightroom...

23) DR Chevalier
July 10, 2015 at 12:22 pm

Hello Nasim, Thank you for your as always intelligently written article. I do not use Windows but will confirm that despite plenty of assurances of performance improvements, Lightroom 6.1/CC2015.1 is slower across the board. It definitely demands more memory. One of my students uses a MacBook while travelling and stores to external drives. In LR5 you could use Smart Previews for editing when the original was not present. You can as well in LR6 but it is so slow in this methodology that you can actually watch the changes happen long after you make them. My production machine is a Mac Pro from late 2014. Despite the best graphics Apple had, 32GB of RAM and internal SSD, the current release is visibly slower than the predecessor. 2015.1 fixed some problems, but I find that the longer I am in Lightroom, the slower it gets to the point where a complex piece of work may time out entirely. I have made a habit of exiting every hour or so to prevent surprises. It’s not optimal but not a major headache either. I don’t really see much of a difference between a machine with GPU support and one without except that the background processing can load more work in the job queue if the machine has a supported GPU.

Every new major upgrade will have some challenges. The initial releases of LR5 were certainly not optimal. This time is no different. I only wish that Adobe and their agents such as Kelbyone had not been so vocal about performance improvements right up front since the far and away consensus from customers is that it is a poorer performer. ......

====
Ok so that's the comment quoted from a thread on Photography Life. For me, The slowdowns are intermittent. Sometimes I get slowdowns, sometimes not. Always in D mode. Maybe, just maybe it's in photographs that have a lot of edits already. I am guessing and will pay more attention in the future. It might be in photographs where I did a lot of editing in 5.7 prior to converting to CC.1.

The symptom is that in D mode, things like drawing an area to be cloned have a lag waiting to see the actual area that I am drawing.

For the filter (not sure of correct name - control on the right where you can draw an area to be filtered) the same thing is true. If I turn on the "selected mask overlay" that shows in red the area you are drawing to be changed, the appearance of red has a notice-able lag. I have to guess as to how I am drawing.

Both problems are intermittent.

Monitor: Sometimes I an old external monitor (1920, 23") and sometimes I use the built-in screen. Never 4k.

Configuration:
Hardware Overview:

Model Name: MacBook Pro
Model Identifier: MacBookPro12,1
Processor Name: Intel Core i7
Processor Speed: 3.1 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache (per Core): 256 KB
L3 Cache: 4 MB
Memory: 16 GB
Boot ROM Version: MBP121.0167.B12
SMC Version (system): 2.28f7

=====
As developers it is always tempting to add new features but please give reliability and responsiveness a higher priority than new features.

You can revert back to LR 6.1.1: http://www.lightroomqueen.com/how-do-...

Well, I did that (using a backup), but my confidence in Lightroom has been greatly diminished. Just saying ...

Apparently starting up with shift and alt pressed and resetting preferences solved the problem finally.

I have my images stored on a samba network drive, but the catalog is locally on my drive. The hang up seems to happen only when the network drive is connected. Without it everything seems to work because I have smart previews enabled. Once I mount my network drive Lightroom goes to max CPU and eventually freezes.

They fixed the largest issues the same week the product shipped.
Now they are working on the remaining issues, plus the import UI.

Did anyone try a clean user account anywhere along the line? Modern MacBook Pro's should have no trouble running LR6. How did you go about downgrading - is it definitely running 6.1.1?

I downgraded per what one of the reps recommended. Open app dropdown from Adobe CC dialog in header, scroll to bottom, find the previous versions accordion, find your app, and choose a previous version. You can go way back. I'm running 6 not 6.1.1.

I just got off screen share with my 6th or 7th rep. In this scenario she turned on my macs root user. I logged into the root user, and updated permissions on Lightroom to include the root user. Then went into disk repair or something similar and repaired permissions for the hundredth time. I have not tested for crashing yet, since I've been on multiple shoots each day, but I'll have some time to test this evening.

I just wanted to make sure I added this to convo for anyone that is frustrated beyond belief like me...

"I'm running 6 not 6.1.1."

Note that 6.1.1 / 2015.1.1 fixes some very serious export bugs in 6.0 / 2015.0. I recommend that others revert back to 6.1.1 / 2015.1.1 -- based on all the reports in the forums, it is the best of the version 6 releases in terms of stability.

I couldn't do anything but 6 or else Lightroom was unusable. At least I can do some work in between the 30+ crashes a day on 6. I'll do the best thing, and test completely on 6. Confirm that I'm better off than I was before. If so, upgrade to 6.1.1 and move up in versions if my testing shows better performance/no crashing.

They issued one fix (6.2.1) and are working on another large set of fixes.

6.2.1 only made it worse for me. My lightroom is unusable as it stands right now. Hopefully you guys fix it soon

For one thing, it shows that Adobe is no good at project management. The evolution of this software is badly specified and when it comes to development, testing and product release it just shows a team completly at loss with reality.
And I shall not extend on the "customer care" aspect.
At Adobe, only one thing counts: the bottom line!

I was told 6.3 is coming soon. As I wrote below, if your Lightroom is unusable, downgrade to 6 and see if you can at least work in between crashes. Also I published a little background on what Adobe reps did with the root user on my machine to help alleviate the issue. Worth a try for anyone here as well who has an unusable Lightroom at version 6.2.1. I personally still need to put my Lightroom through more paces.

Lr 6.3 would not only contain bug fixes, but also new camera and lens support for the holidays. That has its own dependencies. The team wants to take time to make sure it is a solid release. Thanks for your understanding. 

Simon, I imagine I and many others will be reimbursed monetarily for our frustration and non-working versions of Lightroom? Who do we talk to, to be compensated for this catastrophe??

I have since tested my Lightroom with the root user permissions added and it's still crashing. I have also created a new catalog, imported my old photos, and the crashing is still happening... THIS. IS. RIDICULOUS. Obviously Lightroom all three versions/patches are not compatible with Capitan. Has anyone at Adobe admitted that yet? It's not our hardware. It's not our catalog. It's not the graphics acceleration.. Lightroom is now buggy and incompatible..

I am two weeks into lost time, angry clients, late nights because I can't complete work in a timely manner..

Danny, I hear your frustration with the Lr 6.2 release. No one on the Lr team wants to release a buggy product. Accident do happen and bugs do creep through undetected sometimes. We're doing everything we can do make sure the next dot release is rock solid and it takes a little bit more time to ensure that.

For the time being, you can follow Victoria's excellent instruction to revert to Lr 6.1.1 http://www.lightroomqueen.com/how-do-i-roll-back-to-lightroom-2015-1-1-or-lightroom-6-1-1/.

There are a list of documented Lightroom issues with the Mac OSX 10.11, see https://helpx.adobe.com/lightroom/kb/lightroom-and-el-capitan---mac-os-10-11.html. A few of the issues will need help from our partners.

When you experienced a crash, please submit the crash log to Adobe so that we could investigate it. I just looked our crash report dashboard and did a search with your email address. I found no matches. So I cannot tell if your particular crashes have been resolved.

If you're interested, I can ask to add you to our private beta prerelease program so that you can have an early access to the early Lr 6.3 build to make sure that your issue has been resolved. Let me know.

My particular crashes have not been resolved. Here is the case number that details everything that's taken place currently.

0187155058

I am reverted to 6.0 because every other version above 6 makes Lightroom absolutely and completely useless.

I would very much like to be a part of the beta so that I can potentially have the fix soon than later.

@danny The case number is foreign to me. I'll ask around internally to find out more info.

The best way to report Lightroom crashes and get it directly in front of Lightroom developers is to submit the crash report to Adobe via the Adobe Crash Reporter dialog that comes up after the crash (on Mac). Provide your name and email address (so that we can contact you for more details if necessary). Also tell us a thing or two on what you are doing in Lr while the crash happens.

On Windows, we rely on Windows Error Reporting service and monitor that as well.

If you don't see the Adobe Crash Reporter dialog, try deleting the file ~/Library/Preferences/com.adobe.crashreporter.plist (which stores the "don't show again" preference for the Adobe crash reporter).

Trust me I see the crash dialogue. We're good friends. I directly email my crash reports, per a reps recommendation, to a direct email address with my case number attached.

Thanks, Danny. When Lr crashes again for you, submit the crash log directly through the crash dialog. There will typically two. The first one would ask you to send the crash report to Apple. Submit that. And then the Adobe Crash Reporter dialog would come up. Type in your email address and name and provide a brief description on the circumstances of the crash.

I (and Lr development team) have direct visibility into such crash reports and can act on it with the full information. Our internal staff has forwarded your case notes to me. It does not have the actual crash log and it is not helpful for me to determine the issue that you have. It sounds like it is a random crash in your case. Please post back on this thread after you submitted a crash log and I can search for it.

If you launch the Console app on Mac OSX, under the "User Diagnostic Reports", there should be records of crash logs from the previous Lightroom crashes. Please zip, upload and share them on some online store (like dropbox) or your CC sync folder (if you're a CC member) that I can take a look.

I have this same problem. No idea what causes it.

@jens @harold Please see my post http://feedback.photoshop.com/photoshop_family/topics/lightroom-cc-2015-2-takes-100-cpu-when-creativ... that might resolve your high Lr CPU usage during idle.

@Simon Thank you, I will try this.