Update #2: Lightroom 6.3/CC 2015.3 is now available which includes the previous import functionality, bug fixes and added camera/lens profile support.
Update: We plan to restore the old import experience in our next update. In the meantime, if you need to restore previous import functionality, or are experiencing other issues with Lightroom 2015.2.x/6.2.x, we recommend you roll back to the Lightroom 2015.1.1/6.1.1 update until things are reverted and corrected. See instructions here: https://helpx.adobe.com/lightroom/kb/roll-back-to-prior-update.html
We’re happy to announce the immediate availability of major updates across the Lightroom ecosystem today!
Release Notes
New Features – Lightroom desktop
Dehaze as a Local Adjustment*
We added Dehaze as a global adjustment in the Lightroom CC 2015.1 release and are excited to see the widespread interest in the feature. We wanted to extend the functionality, and I’m happy to announce that you can now apply Dehaze as a Local Adjustment. This means that you can use Dehaze with the Radial Filter, Graduated Filter and Local Adjustment Brush.
* Please note that this feature is not available in the standalone version of Lightroom 6
Revamped Import
We redesigned the Import experience to make finding and importing your photos easier and more visual. The redesign was driven by our desire to make the import workflow more explicit and clear. The workflow is 1. Select a source, 2. Select images 3. Choose any import settings (optional) and 4. Import.
The revamped Import experience is based on customer feedback and we’re excited to hear what you think.
- Select a Source: There is a new “Add Photos” screen which scans to identify the potential locations for photos on your hard drive. You can also easily select from a folder, a connected camera (via USB cable), a memory card, external hard drive, or Photoshop Elements catalog.
- Select images: The Import Dialog has been redesigned. Your source will already be selected (you choose it in step 1) so you can specify which images to import. We recommend importing all.
- Choose any import settings (optional): While there isn’t a need to change the default settings, you can open the gear icon (on the top right) to adjust and change import settings.
- Hit the import button.
Improvements to “Import from Photoshop Elements” feature
In addition to Import, we’ve revamped the Import from Photoshop Elements experience. Now you can migrate the images from your Photoshop Elements catalog into Lightroom easily. To do so, click on the Photoshop Elements icon in the “Add Photos” screen (step 1 from above). Select the Elements catalog and click the Import button. Lightroom will handle the rest for you automatically.
New Features – Lr mobile 1.3 (Android)
- Total color control. Refine the individual colors in your photos with the new Color / B&W adjustment tool.
- Just the right tone. Precisely control the tone of your photo with the new Tone Curve adjustment tool.
- Stand out. Bring out the best in your photos with adjustable vignettes.
- Find your photos faster. The new ‘Lightroom Photos’ collection displays your Camera Roll photos and videos by date, so you can find them faster.
- Your photo at its best. Crop the perfect photo with a redesigned experience that enables you to quickly adjust, align and auto-straighten.
- TIFF Filetype Support
Download the updates from the Google Play store here
New Features – Lr mobile 2.o (iOS)
- Free Lightroom! Unleash your creativity with free access to Lightroom for as long as you’d like on your smartphone or tablet.
- Better photos in a snap. Capture amazing moments with the in-app Adobe camera, streamlining shoot to share.
- Cut through the haze. Control the amount of atmospheric haze in your photos to recover color and contrast, or to create artistic effects, with the Dehaze adjustment tool.
- Make photo magic, faster. Seamlessly access Photoshop Fix to retouch your photos.
- Complete color control. Tune the colors in specific areas of your photos using the Targeted Adjustment tool, a new Color/B&W editing option.
- “Lights, camera, action.” Craft amazing video stories from your Lightroom photos— synced to the beat of your favorite music, with one-tap access to Premiere Clip.
- Find your photos faster. The new ‘Lightroom Photos’ collection displays your Camera Roll photos and videos by date, so you can find them faster.
Download the updates from the iOS App Store here (iPad | iPhone)
New Camera Support in Lightroom 6.2
- DxO ONE
- Leica S (Typ 007)
- Olympus E-M10 Mark II
- Sony A7SM2 (ILCE-7SM2)
* Please note that SuperRAW files from the DxO ONE are not supported.
New Tethered Camera Support in Lightroom 6.2
- Leica M Monochrom
New Lens Profile Support in Lightroom 6.2
| Mount | Name |
| Canon EF | Canon EF 600mm f/4L IS II USM |
| Canon EF | Canon EF 800mm f/5.6L IS USM |
| Canon EF | SIGMA 24-35mm F2 DG HSM A015 |
| Canon EF | TAMRON 18-200mm F/3.5-6.3 DiII VC B018E |
| Canon EF | TAMRON SP 35mm F/1.8 Di VC USD F012E |
| Canon EF | TAMRON SP 45mm F/1.8 Di VC USD F013E |
| Canon FD | Canon FD 28mm F2.8 |
| Canon FD | Canon FD 50mm F1.4 |
| Canon FD | Canon FD 135mm F2.5 S.C. |
| CONTAX 645 | Zeiss Distagon T* 2,8/45 |
| CONTAX 645 | Zeiss Distagon T* 3,5/35 |
| DJI | PHANTOM 3 Standard (DNG and JPEG) |
| GoPro | HERO+ LCD |
| GoPro | HERO4 Session |
| Leica M | Leica Summilux-M 28mm F1.4 ASPH. |
| Leica M | Zeiss Biogon T* 2,8/21 ZM |
| Leica M | Zeiss Biogon T* 2/35 ZM |
| Leica M | Zeiss Biogon T* 2,8/25 ZM |
| Leica M | Zeiss Biogon T* 2,8/28 ZM |
| Leica M | Zeiss C Biogon T* 2,8/35 ZM |
| Leica M | Zeiss C Biogon T* 4,5/21 ZM |
| Leica M | Zeiss C Sonnar T* 1,5/50 ZM |
| Leica M | Zeiss Distagon T* 2,8/15 ZM |
| Leica M | Zeiss Distagon T* 4/18 ZM |
| Leica M | Zeiss Planar T* 2/50 ZM |
| Leica M | Zeiss Tele-Tessar T* 4/85 ZM |
| M42 | Asahi PENTAX Super-Takumar 55mm f/1.8 M42 |
| M42 | Fujifilm FUJINON 50mm f/1.4 M42 |
| M42 | Fujifilm FUJINON 55mm f/1.8 M42 |
| MFT | Voigtlander MFT 10.5mm f/0.95 Nokton Aspherical |
| Minolta SR | Minolta MC ROKKOR 58mm F1.2 |
| Minolta SR | Minolta MC ROKKOR-PF 55mm F1.7 |
| Minolta SR | Minolta MC ROKKOR-X PG 50mm F1.4 |
| Minolta SR | Minolta MC TELE ROKKOR-PE 200mm F4.5 |
| Minolta SR | Minolta MC W.ROKKOR-HG 35mm F2.8 |
| Minolta SR | Minolta MD 50mm F2 |
| Minolta SR | Minolta MD Celtic 135mm F3.5 |
| Minolta SR | Minolta MD ROKKOR-X 45mm F2 |
| Minolta SR | Minolta MD ROKKOR-X 50mm F1.7 |
| Minolta SR | Minolta MD W.ROKKOR-X 28mm F2.8 |
| Nikon F | Minolta MD W.ROKKOR-X 28mm F2.8 |
| Nikon F | Nikon AF-S DX NIKKOR 16-80mm f2.8-4E ED VR |
| Nikon F | Nikon AF-S NIKKOR 24mm f/1.8G ED |
| Nikon F | Nikon AF-S NIKKOR 24-70mm f/2.8E ED VR |
| Nikon F | Nikon AF-S NIKKOR 200-500mm f/5.6E ED VR |
| Nikon F | Nikon AF-S NIKKOR 500mm f/4E FL ED VR |
| Nikon F | Nikon AF-S NIKKOR 600mm f/4E FL ED VR |
| Nikon F | Nikon NIKKOR 24mm f/2.8 AI |
| Nikon F | Nikon NIKKOR 50mm f/1.4 AIS |
| Nikon F | Nikon NIKKOR 50mm f/1.8 AI |
| Nikon F | Nikon NIKKOR-H Auto 50mm f/2 |
| Nikon F | Nikon NIKKOR-P.C Auto 105mm f/2.5 AI |
| Nikon F | Nikon NIKKOR-S.C Auto 50mm f/1.4 |
| Nikon F | Nikon NIKKOR-UD Auto 20mm f/3.5 AI |
| Nikon F | SIGMA 24-35mm F2 DG HSM A015 |
| Nikon F | TAMRON 18-200mm F/3.5-6.3 DiII VC B018N |
| Nikon F | TAMRON SP 35mm F/1.8 Di VC USD F012N |
| Nikon F | TAMRON SP 45mm F/1.8 Di VC USD F013N |
| Parrot | Bebop Drone (DNG and JPEG) |
| PENTAX | HD PENTAX-D FA 24-70mm F2.8ED SDM WR |
| SIGMA | SIGMA 24-35mm F2 DG HSM A015 |
Bug Fixes:
- When migrating from Photoshop Elements, Lightroom included face regions which were previously either rejected or deleted in Elements.
- The Eye dropper won’t sample color from image. Please note that this occurred when GPU enabled on Windows only.
- A range of AMD cards appear as unsupported on Windows. Please note that this was resolved with the AMD 15.9.1 beta driver release, which is available here
- The color matching camera profiles for the Olympus Style 1 and Stylus 1S disappeared after installing the Olympus 2.0 firmware upgrade.
- JPGs exported from Lightroom CC can be incompatible with some other applications due to a non standard header.
- Map, Book, publish, sync are not working for Creative Cloud Enterprise customers on Mac OSX 10.10.
- The Flickr Publish Service includes people keywords when it shouldn’t.
- All exported JPEGs in Slideshows have the same slide text.
- Images rendered as swapped blocks within the Slideshow module. Please note that this occurred only on Windows machines with AMD graphics cards.
- Lightroom CC Slideshow Module takes over selected display monitor until LR is closed. Please note that this occurred only on Windows machines with AMD graphics cards.
Installation Instructions
Please select Help > Updates to use the update mechanism in the Creative Cloud app.
Direct download links: Mac | Win
Thanks!
Is ‘Revamped Import’ available to perpetual license customers?
Yes, it is Stefan.
Oh, but why? This is a new feature with a new UI. I thought LR6 perpetual license customers are not supposed to get feature updates? Surely that’s a mistake?
I hope they either disable the new import dialog for perpetual license holders, or they enable all the other new features too.
I agree with you the new import is terrible. All my photos are on NAS and do I ever have to dance to get there now.
revamped Import experience
TURN OFF THE PRETTY. Can we have an option for just an efficient folder view and option/actions.
Agree. This reminds me of windows 8.
The creative cloud install doesn’t show this update.
The MAC link for people who have problems actually loads Lightroom 6.1.1
Not good !
So disappointing… I was really hoping that the LR desktop would have speed boost as my current workflow is inhibited by the poor performance. I have been doing research on even replacing using LR pending any speed improvements in the upcoming releases, but this article doesn’t even mention speed.
On the Mac even the stock & barebones Photos app feels like 10 times faster. Lightroom is the only app on my Macs that actually needs time to load thumbnails… how encouraging is this for an “image processing software”?
Are you sure the download links are correct? Shouldn’t they be pointing to the 6.2 release, and not 6.1.1?
Even though I’m a CC customer, will the installer in the zip file work seamlessly? In my case, my Internet connection is not always reliable and I pay for Internet by the MB. I’d prefer to download the installer using my own download tools and save the installer for possible later use, instead of using the Creative Cloud application. One feature of the Creative Cloud application that I find very frustrating is that in the case of an installation error (even a trivial one), it re-downloads the entire application installer.
The links are wrong! Here are the correct ones:
mac:
http://swupdl.adobe.com/updates/oobe/aam20/mac/AdobeLightroom-6.0/6.2/setup.dmg
win:
http://swupdl.adobe.com/updates/oobe/aam20/win/AdobeLightroom-6.0/6.2/setup.zip
Yet I am paying for this and there still no El Capitan update and Lightroom CC is not working in 10.11 El Capitan.
Why not? My LR CC is working great on EC…
The mac version of setup.dmg in its properties shows:
Created: Monday, July 27, 2015 at 11:42 and is 190.1 Mb.
After I’ve installed it I still have version Lightroom CC 2015.1.1
In Creative Cloud Desktop app I can not see any Updates available.
So, where is the correct link to version CC 2015.2?
The links do not provide the 2015.2 update. They only point to 2015.1.1
Sorry, links updated!
And the standalone version ???
Dehaze ???
Dehaze is only available in the Creative Cloud version of Lightroom.
Why?
I own licenses for LR 2, 3, 4, 5, and 6. I really like the product. However I will never buy into your subscription strategy. If the non-subscription version of LR becomes cripple-ware then I will switch to another vendor. Obviously, it is a decision that I will not make overnight but continuing to add features to the CC version without a good reason for omitting it from the non-CC version is a step in that direction.
There is no reason to leave out the dehaze functionality from LR 6. All of your cloud + mobile stuff should be enough reason for people to buy the CC version.
Agreed. I paid for their product (LR2, 4, 6, PS CS4, CS6); if they choose to cripple it to encourage migration for a subscription-based service…so long, Adobe.
アップデートしたあと、何度も強制終了される。さっさと直せクソアドビ。
A friend has just told me that with the latest upgrade you have removed “Move’ Functionality from your LR Import module. Is this true? If so, I do not want to upgrade. I am a professional photographer who has been particularly loyal to Lightroom because of the workflow possibilities and organizational functionality it affords me. I use move every single time I work on a job. Every single time. Now I hear I will no longer be able to do that and I am wonder why you are taking away away control from your users? Does everything really have to be dumbed down? The whole point and beauty of Lightroom is that I don’t have to worry where my images are on the disk, I can use Lightroom itself to organize them into the location I want them to be in. I have been an evangelist for this functionality, the move functionality, that lets me rename my files by date and relocate them to a folder named by date. I have resisted moving to Capture One because I have been so satisfied with your workflow and the organization features of LR. So I am scratching my head in disbelief that you would take away a function that people might actually use and be happy with. Why not just leave it there for people who are smart enough to use it? Before I make the mistake of upgrading, please can you confirm t is true you have taken away move and explan your reasoning and the process I will have to use instead in order to achieve what I am currently achieving with the previous version of the software. Thank you.
Yes it’s gone, and it sucks. I’m seriously considering reverting back to LR 6.1.1 for that reason alone. I’ll put up with the bugs, it’s better to have the move feature. I always dump all photos in one place, then use the import to move them where I want.
The other thing is no directory listing on the left for the import location, doesn’t default to the last used location you have to select it each time. And no directory listing for where you are putting the photos on the right, just a single line showing the directory name of path.
I don’t like the import at all, and if I can will revert to the older version.
I agree. This new flow is no longer efficient and cripples my workflow.
I agree with Sam – getting rid of the Move, Import Presets, displaying file extensions without having to click on the photos, plus other truly bizarre removals has me scratching my head.
Making de-haze local is fine and all, but how about some performance improvements? I have a pretty fast computer with a good graphics card and quite a bit of ram, and LR is SLOW. It’s actually quite annoying.
… sorry. You will never get performance emprovements, as they can only mess with UI; they bought software, not programmed it, remember? In fact every version is heavier then previous. Try to to run this on Pentium 4 (most common cpu in version one era).
Additionally to my previous comment I now hear the “Destination panel folders preview is gone, including the italic preview showing your chosen folder structure, the checkmarks to their right, and the volume information showing how much space was available on each drive.”
Do you understand that professionals use your software and they need to know this stuff for a reason?
If you take away all the technically useful stuff that you provided, your clientele will not be happy.
You have listed all your additions in this article but failed to address all the functionality you have taken away. This is not helpful for your customers.
that an the ability to sort importable files by date (unless i’m missing something). i really need to roll this update back; it’s horrifyingly crippling
stay away from this update it is BUGGY as hell.
for example the “synchronize folder” feature is not working
https://forums.adobe.com/thread/1970887
The update crashes when saving Tiff edits from Adobe Photoshop CC 2015.
Correct. Crashes for me as well. Sucks
This update is so slow that it is unusable with my system. Not a great start for such small updates!!
This new import dialogue is not very well integrated with the rest of Lightroom user experience wise and i personally highly dislike the design and toyish feel… Anyway, please bring the ‘move’ functionality back!!!!
Why is the update not available on my CC ? Or is it US only ?
The update started to roll out yesterday. It should be available everywhere now, please try again using the Creative Cloud app.
Same here: No Update available in CC.
Would like to know how much this costs?
Thank-you
I find the new import dialog to be somewhere between “desasterous” and “everybody run!”
Can I disable this in favour of the old logic?
You can disable it. Terry White had a video he made showing how to do this. Go to preferences and unmark “add all photos (or something like that), Sorry did not pay a lot of attention as it did not apply to what to Windows users or so he says in the video.
“Revamped Import” is increadably bad. Ugly, counter-intuitive – mindboggeling. Please revert ASAP!!! At LEAST include an option to deactivate!!
Hi, if you want to revert or roll back to a previous version of Lightroom (or any Adobe application), then just follow the instructions here:
http://prodesigntools.com/adobe-cc-version-control.html
Updated to LR CC 2015.2 on Mac OSx 10.11 and Macbook Pro. LR now crashes on import. Took me one hour of reading blog posts and suggested fixes to get around this, required resetting preferences to defaults. Very poorly tested apparently. The new import module is a complete regression in functionality. I very much prefer the previous import and want it back. Shame on Adobe.
While the original Import experience was indeed not the most intuitive, so I can see why Adobe decided to redesign it, I am baffled by the decision to make the new experience so ugly and inconsistent with the rest of the Lightroom UI? If you want to create Lightroom ‘Trippy Flowers’ or ‘Mickey Mouse’ edition, please go ahead but don’t force it on those of us who are paying for a professional tool.
They’ll make the rest of LR look like the new import dialogue soon enough. Adobe is trying to attract apple mobile users who don’t know what a computer is, let alone a folder structure.
Why is Lightroom mobile/web sync so confusing? On the desktop app, the only way to sync to mobile/web is by adding photos to Collections, so photos that are not in a Collection won’t sync. Videos won’t sync either, even if they are put in a Collection.
The new update for Lightroom mobile and web now has an ‘All Photos’ section, where the user can upload photos from camera rolls. The weird part is photos uploaded to the ‘All Photos’ section does not sit in any individual Collection, yet they can still sync with the desktop. To access these photos that aren’t in any Collections on their desktop app, the user would have to look into their ‘Smart Collections’ or the catalog folder for their synced mobile devices. So if the mobile/web apps allow photos to be synced without adding to a Collection, then why does the desktop app behave differently?
And the user cannot change the file directory of the mobile sync folders on their desktop whatsoever. So if the user usually imports all their photos from cameras using Lightroom’s default settings (which automatically creates a YEAR folder and a YEAR-MM-DD subfolder) and wants to manage their synced mobile photos the same way, they would have to do everything manually since there’s very limited option to do anything with the synced mobile photos in the desktop app.
And only the iOS version can sync videos; neither the desktop nor the Android version can sync videos. And only the iOS version got the update with the new in-app camera, the Android version doesn’t have it (yet). Still, a photo taken with the in-app camera is automatically uploaded to the ‘All Photos’ section, completely bypassing Collections, which, as said before, creates another layer of confusion for desktop users who actually wish to have some way to manage their mobile photos using their desktop app.
Really hope you guys can figure something out. Managing synced photos in one place shouldn’t be this difficult.
Hi Don, Yes I completely agree. Its on our plate and something that we’re working on.
Thanks
Sharad
If revamping import means making it unable to do so anymore, then you succeeded.. really what good is lightroom if you cant import or sync t files anymore
I am surprised Adobe has not sent out a statement regarding this botchy update, that and retract the update from being downloadable. My whole evening is screwed up and now I have to figure out whether I should downgrade and deal with reinstalling all the extra components I have (which I don’t have time to do really), and whether I should have hope that people get this fixed in a timely manner. This software is important every day, and I paid for it to work. Seriously? Lightroom is nearly unusable, the performance in 6.2 horrific. This is ridiculous.
Please give us the option to remain with the original import interface. Frankly it made more sense and it’s difficult to tell exactly where / what is being done with the new interface. It has less information, more button presses, and for those of us who used the prior version (and liked it) is simply a waste of our time. I HATE the new import interface.
agreed
While in lightroom when you have flagged or starred photos in the library module, if you try to take one of those into the develop module it crashes. Can you guys please fix this bug? You cannot cull images by flagging them, if all its going to do is crash when you try to go into the develop module.
Bump. I’m having the same issue. When I’m in the Develop Module, and click the button to filter by Flagged Photos only, Lightroom reliably crashes (Windows 8.1, AMD CPU, Radeon 7970 GPU)
See this post. You can roll back to the prior 6.1.1 update until things are reverted and corrected: http://blogs.adobe.com/lightroomjournal/2015/10/lightroom-62-import-update.html
This Connection is Untrusted
You have asked Firefox to connect securely to swupdl.adobe.com, but we can’t confirm that your connection is secure.
Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site’s identity can’t be verified.
Dear Adobe,
I will not be upgrading to Lightroom CC 2015.2 until the following are restored…
– To be able to see how file name looks before it is brought in to LR.
– To see the destination Folders
– Zoom is gone from the Import Loupe view.
– Filename is now hidden under a tooltip.
– Destination panel folders preview is gone, including the italic preview showing your chosen folder structure, the checkmarks to their right, and the volume information showing how much space was available on each drive.
– Total file size is gone from the bottom left corner.
– The filename preview (when renaming) is gone.
– Automatically eject card after import is finished
These are useful features that should have never been removed, and I just can’t understand how removing them made it any better for new or existing users!?!
I agree with William, the loss of functionality in the Import process was enough for me to revert to cc 2015.1.1, which was not painless. Depending on the photo project, I use multiple and varied presets during Import and like to be able to review the results of these settings before I hit the Import button. Please don’t dummy-it-down and reinstate the former import process.
For the very same reasons i will downgrade to 6.1
6.2 is unusable for me – it’s a showstopper
+1
Sorry, but this import dialog really really sucks! Please remove that sh… and give us something better. If I want to use Apples Photo I’ll use that but I pay for a professionel tool, or not?
And btw. still the same error. Select >10 images in the filmstrip and synchronize the development settings. There will always be some images at the end where values are not synchronized!
Wow, the import dialog gives me all my images that are already in Lightroom! Awesome!
Having upgraded, LR crashes every time on import ! Any suggestions ?
can you provide more details? what is your system’s specs (Mac / Win, version, etc.)?
Happens to me also. Mac El Capitan. Had to use time machine to go back and install my old version. This is a terrible upgrade. Caused me a lot of trouble today as I was up against a deadline.
Joe
It Happens to me also. Mac El Capitan. Had to use time machine to go back and install my old version. This is a terrible upgrade. Caused me a lot of trouble today as I was up against a deadline.
Joe
you removed features and make it sound like improvement..
it´s always sad day when the PR guys take over…..
Thanks, but why is the dehaze tool not coming to the standalone version? Does Adobe have a problem with its longterm and royal customers (in my case since LR 1)?
Can you please make the new import dialog optional or something like that? It really doesn’t work for me.
I just quickly want a list of folders and select the right one and get to work on my images.
I’m now either waiting forever for unneeded previews of the 27000+ files that are already in Lightroom, or if I just want to select a single folder I get a real small dialog with a minimal scrollbar to scroll through my library of currenty 600 folders …
What’s wrong with the quick and easy MacOS X (in my case) dialogs which I use all day in the Adobe other software?
Please give me as a professional a quick and dirty way to import my files. I know what I’m doing …I do it all day.
Thank you!
There is a preference to disable the “Add Photos” screen.
Your response doesn’t even begin to address the problem. The import process is a mess.
Why not spend more time on the GPU operation?
Why then giving an option if we all will disable it??
Some added info: I’m working on a 27 inch screen (at a resolution of 2560×1440), and if I select import -> drive, the dialog for selecting subfolders uses about 1/10 of my screen, on the left top, and the scrollbar is really small.
It makes selecting the right folder quite problematic, and 9/10 of my screen is not being used.
Also, the missing ‘eject after import option’ means an unnecessary extra step to the finder (MacOS X) when I’m importing from multiple cards after a shoot.
By adding global and local de-haze to only your leased version of Lightroom and denying it to your perpetual licence paying customers you are not encouraging me to move to CC you are making me more determind to to find a suitable alternative product.
There is a bug (or not optimized code), when applying a healing brush. It takes more time to finish operation than in previous release and during finding a second spot it freeze a mouse cursor for a while too. It didn’t work this way in previous release, where it was working smooth. I didn’t change any preferences since previous version installed. Thank you for solving out this problem.
I am unable to re-open LR after having opened it and closed it one time on my Win 10 desktop. I updated yesterday 10-05-15. Using the standard import screen the default font size is extremely small as are the check boxes. Is there some way to make those larger.
I have the same problem on windows 10. I open, then can’t re-open.
what seems to happen if you open the task manager, you will see a lightroom background task continue to run after exiting lighroom. Then every time I try to open lightroom, another lightroom background task starts.
If I end the lightroom background task, I can start lightroom without rebooting my computer
The new import dialog is one of the worst steps backwards that LR ever made. Please bring us back the former dialog, it worked well. How can I go back to LR 6.1.1?
i fear that is a way adobe thinks it can attract mobile user and noobs who don´t kwow what a FOLDER is….
time to look for alternatives like capture one.
You’re right – this entire update is all about the mobile ‘users’. Adobe has been moving that way for a while now. That’s why we’re not seeing the performance improvements in LR. All the engineering and design emphasis is going into mobile.
I’m baffled. Sorry Adobe are you reading this and all the other feedback?
I’m wondering if you guys are on LSD or crack all the time?
Do you ever USE your own software? Soooo many bad decissions lately by adobe!
I just started the new LR for the first time and I was PISSED because I thought that Photo’s started to import. But I realised it was the ‘new’ interface. Oh boy! It does not fit the current GUI, it looks to be a totally difference kind of program, also the cogweel with the settings is very iOS like, be we are pro’s and we need all the options all the time at our disposal. I really hope this isn’t a shift to a consumer based raw editor! I know it is too late, we all want a revert but you will never do this or admit it is really bad. Just keep all this feedback in mind when you try to alter the rest of the program. You guys really need more beta-users and beta feedback!
+1
could not agree more…..
I’m LR user since LR2, and I like this program. But if Adobe goes further this way, LR will die within the next few years. I don’t hope this but it’s not unlikely.
I agree. With the new import LR lost a lot of good functions like moving files when importing them. I don’t see why I should use another file explorer to delete files only because the new import does not support this option.
I guess it’s the absence of competition, Apple for instance stopped development on Aperture… very bad indeed. I think the decision to not add dehaze to the standalone version will (hopefully) backfire. I for myself feel let down.
It’s like somebody high up at Adobe read an article titled ‘Mobile is the future’!!! All the idiotic things we’ve seen have flown downstream from that.
Please bring back the old Import dialog. This new version is incredibly unusable. If you wanted a dumbed down “Lightroom Elements” then make that a separate product. Having an Import button without being able to see where your images are going is horrible. It will actually slow down a nice workflow by having to jump through hoops to get to the useable options. You tried to fix what was not broken. If you want to improve the Import process, make it faster at rendering previews or be able to flag images prior to Import. Lots of things could be done to improve on it, but the new “Add Photos” is ridiculous.
Dave Doeppel
Adobe Certified Expert Lightroom and Photoshop
This release represents Amateur Hour.
Hi Adobe
Your new version is unfortunaly very instable. I have within one hour work 5 crashes with the new version… and the importer is very ugly. I have now rolled back to last version and hope, your QC works with the next version better.
best regards
michael
Is there a possibility to add the lens profile for the sigma 24-35 2.0 DG HSM | Art to LR5.7 ?
Am I the only one who get crashes switching to Develop mode after the last update? I thought it was because of Graphic Acceleration but I turn it off and the problem is still there.
This Update is horrible… it crashes 20sec after start. its really buggy
How can i get back to previous Version? I need ist really now
Really?! The new import dialog is better now that you’ve simplified it so much that you have no idea what’s happening. Really?!
Ugh!!
In my view, you taken a dialogue that was logical and easy to use for a variety of different import scenarios and made changes that look nice visually but make it much harder to use.
How can I get the old import system back? The technical develop changes are appreciated, but now this window dressing.
The new import is a hell – not responding any more (I had to terminate LR), what are you doing Adobe? Who is programming this buggy ….? Did you test this with a lot of external drives attached and SD-Cards plugged into the reader? Please Adobe let me configure the Import: In the Configuration properties I can tell you which network dirve(s), sd-card(s), external / internal drive(s) LR should use for the import, here at my computer I always use exactly one, LR does not need to scan my entire computer for images – it can’t find any elsewhere, so please stop scanning and let me help LR, I know where LR should seek. The usability is soooooo bad and mostly not responding – sorry, please give me my old Import dialog back.
Here is the algorithm:
FOR all directories configured in the LR configuration (and optional sub directories)
{
IF known file extension add to imports list (use c++11/14 for this)
}
FOR all images in import list
{
display thumbnail
IF already in LR database mark as “already imported”
}
LET user select / multi-select images for the import
LET user add keywords, destination path a.s.o.
DO the import (in PARALELL) I have more than one CPU
correction: (use c++11/14 filesystem or this)
And please compress / zip the lrcat-catalog file on close and un-compress / unzip when opening, it saves a lot of space e.g. 900 MB -> 130 MB.
Lightroom 6.2 is hanging when I shut it down in Windows 7 (64 bit). I can still see it in the processes. The application will not restart until I end the process. Error is repeatable…
new import module is very buggy. Haven’t gotten past that to explore more.
WARNING: UPDATE DEFAULTS TO AUTO UPLOAD ALL PHOTOS
Shameless and untrustworthy move by Adobe. Not cool, not smart. Grounds for cancelation.
Crashes on import
Crashes on Export to JPEG file
Crashes on photo Sync
Crashes on Delete of multiple files
I’m using a late 2013 Mac Pro W/64GB RAM, Dual D500 GPU’s and a variety of other expensive bits and this application update has been a very major disappointment so far. It’s cost me an entire day of finding a workaround in order to complete some time sensitive work.
Incredibly, Adobe has charged me the month CC membership fee. Will we be seeing a discount of this fee given the failure of this update, at least until you people get it remedied??
In all fairness to Adobe, there are some really neat features in this update and I personally have not seen too many stability issues. But I went ahead and made a complete step-by-step video tutorial for those looking to move back to Lightroom CC 2015.1.1 / Lightroom 6.1.1. See http://bit.ly/rollbacklightroom for more details on how you can revert to an older version until some of these bugs are gone.
—
David Marx
look at the adobe forums. especially on apple system this version is extremely unstable.
i found 3 bugs that are repeatable…. and affect me every day.
with all fairness this is unaceptable.
there is no quality management at all at adobe as ist seems.
or hwo do you expalin that these bugs are reported by so many peopel just 2 hours after release?
sorry for the typos i am in a hurry and post from my phone…..
Thank you thank you thank you for offering up these rollback instructions!!!
Dearest Adobe-
I am a professional Lightroom instructor, author and image organizer and I have been praising LR since the beta. Up until now I’ve let the stupid things you do slide. But, now I can no longer. You can’t take away features and functionality. You must put back the MOVE and the option to ALLOW duplicates. Your original LR designers put them there for a reason. I use these two features on a daily basis with my clients during extensive organization/folder restructuring, duplicate deleting, moving from one drive to another and so on. I can’t do my job now. Nor can I tell my clients to not upgrade. Just put them back and the world can continue.
Hi. I am really struggling with mobile workflow. Perhaps you have some advice because I’m concerned about CC and LR Mobile iOS. I have 80,000+ images in one catalog on a Mac Desktop version of LR. I’m very organized. All files are in a folder system by year then YYYYMMDD. I rename all my files so the file names are YYYYMMDD – description before I import them to LR. Therefore, even images that come off my iPhone are in this format and filing system.
I’ve always treated my iPhone like any other camera. However, I am finding myself doing more and more processing on the iPhone itself. It’s miserably confusing when I take 10 shots of something similar and then start processing one, saving multiple versions as I work through a series of mobile apps.
I need a system to keep the versions of mobile files on my iPhone together and a way to keep them together when I import them to LR.
I wanted to use LR Mobile for this but I’m terrified by a system that sucks all my iPhone images into a collection and then dumps them into one large folder with useless file names. I can’t begin to think how to then rename them and organize them into my folder structure.
Is there something I’m missing? What are people doing with their mobile images? Just relying on keyboarding to find things in LR Desktop? What happens if I use LR Mobile and have that large folder of images and then import the same images through my normal process? Will they sync together? What if I don’t modify the file name?
Any thoughts would be appreciated.
This new version (2015.2) on my PC, an i7 quadcore 12GBRAM, takes constantly at least 25% of CPU time, even when doing nothing with the photos. Thus generaring a huge performance issue. Browsing is very slow and all the commands run at 1/10 of the speed of previous version.
Stay away from this release!!!
Is there a way to downgrade to previous version 2015.1.1?
Alberto Fanelli
Upgraded LR on CC last night. Now when I try to delete a photograph the whole system crashes and blanks to my homescreen saver. Then I receive an Error Report message with a lot of coding on it, and option to cancel or Report to Apple. Once I click Report, then it goes back to Lightroom again.
Happens every time I try to delete and last night I spent nearly an hour and a half trying to get it going. Still no joy.
What is the problem – it needs to be sorted immediately.
When you do an upgrade why don’t you send out a Blog announcement or email to all Creative Cloud users, and non users, on the changes and how to procveed with the importing of photographs, which is the biggest upgrade item from what I can see.
The whole screen filled with my files and I couldn’t see how or where to find the destination on where to place the folders (Pictures) and create a new folder.
It seems a mess – completely!
On Win 7 64bit, LR 6.2 has a memory leak when generating previews. I went back to 6.1.1 and repeated the test and it works fine. Which is a shame, as LR 6.2 includes profiles for the 600mm II.
This is probably the WORST version of LR so far!
The revampt IMPORT is terrible and can’t be used no more. I have to revert back to the old version of this program.
If the import is not fixed, I can’t upgrade to new versions no more. Sad to say! There are TO many issues and most people above have alrady mentioned them but… oh my god.. this is SO bad
The new Import is a more than one step back – I have absolutely no clue on what your were when this decision has been taken. Please give us back the old one which was about perfect.
Remove the ‘Move’ option if you like as it’s not a suggested best practice anyway – and just give us back all the other options not available anymore – simply put: take the old code and release 6.3 with the import from 6.1!
I stopped using Lightroom for now, it crashes every minute or so, whatever I do, there is no single thing to point to.
In the new import module for some reason they removed the automatic unmounting of my memory card after importing, I cant understand that.
I also have frequent crashes. Never had this before with Lightroom (speaking about versions 1.0 beta to 6.1).
even some of the “prominent internet” photographer say you should not install this version.
it´s really sad to see things get worse and worse with adobe.
i fear the next photoshop version will be full of bugs too.
I just downloaded the 30 day trial version of Lightroom CC. I have many pictures with significant haze on the far mountains. I am unable to use the dehaze just on the mountains. It changes the whole image. The brush tool doesn’t work.
Please help.
Thanks!
I’m not sure if this will help anyone else, but this release of Lightroom has been crashing on me every minute today, until I tried deleting my previews (Lightroom Catalog Previews.lrdata) file/container.
This is a bit drastic, but I have a deadline, and Lightroom has not crashed once in more than an hour since removing my previews, so it might be worth a try if this version of Lightroom is crashing on you too.
Oh feck. Your import system has never been the greatest: for instance your autorename is bjorked and I’ve never found a way to run an external script as part of the import process. Now you’ve taken away MOVE, you’ve put in a pretty-pretty screen that does precisely nothing, an autoscan that doesn’t simply give me the option to go to the source folder I always use and which massively slows my machine down AND it’s buggy and unreliable.
Nice going, Adobe – are you taking lessons from Apple?
I like the local dehaze option.
But please improve Fuji XTRANS rendering. This is really necessary.
No only is this update like the last one a joke with small to no features, but this one is also a total mess !
Installed a few minutes ago. Crashes after 2 minutes each time. No possibility to MOVE files without copying them !! Crashes on editing. Wonderful.
We are a pro lab relying on your software to have our job done.
Please correct this quickly and add the possibility to MOVE files back !
And also : I totally backs the comments over the total inefficient XTRANS rendering, which also did not change since the update.
Re. New import and unstable release.
ill considered, incomplete, inept. I could go on. Shame on you Adobe. Amateur behaviour. The good features such as dehaze drowned by crazy priorities and implementation standards.
For a change can we have some features that have been requested for years on your forums rather than adding another tranche of code that will occupy space on our drives without adding value. What a waste of effort.
I gave a presentation to approx 100 photographers last week on the recent features of Lightroom. If I knew this release was on the way I would have cancelled the presentation.
Sad that more space is occupied on the popular Lightroom blogs on how to roll back the install. Embarrassing…..
I’m reverting back to 6.1.1. The import is horrible.
1. (and worst problem) No move option. That will really mess up my workflow and knowing me I will losse track of multiple copies of photos. I’m with someone else who said I really want a ‘Move and convert to DNG’ but just the plain move option back and I would be willing to stick with this update.
Other issues on their own would not be enough to make me revert to the older version.
2. After closing (at least closing LR from the import screen) it won’t launch again, have to kill it in Task Manager before it will open again.
3. The fancy import screen shows me all sorts of places I have photos on the machine… except the one I want to import from. You can turn that screen off luckily.
4. Once you’ve turned off the fancy first screen of the import it defaults to the first of the places it found photos NOT the place I imported from last and not one I want to use.
5. No directory listing of the destination on the right so can’t visually see if you’ve got the right place selected.
Can I turn off the new import ‘feature’?
I haven’t seen a worse implementation of such a feature ever – literally it slows down my workflow because what used to be quick clicks zipping through different folders is now having to hunt through inefficient ‘big icons’ and tiny links. Not to mention removing useful features like ‘auto-eject after import’.
Auto-Tone on import has been broken also… Lightroom just built me 399 “smart” previews, each with an exposure adjustment of -5.00… really nice to have 399 totally black images to sort through. This just isn’t good enough… proper testing before deploying updates would be a good idea.
the main reason i ” free trial” to Lr CC is so i could use mobile features it was nice… now it works when it wants to and i used to be able to load different collections not anymore; Lr crashes for no apparent reason and now i’m stuck with a year’s sub… &^#@!!@$. (i think i’m going back to the old days of “darkroom”.. oh wait i’m already in the dark… 🙂
Wow, this has crashed 4 times in one hour editing session for me on OS X El Capitan. It’s like beta software.
Can I please have the old import back? Or is there an easy way to toggle the interface?
-bill
Hi
downloaded the update 20 hours ago and my LR catalogue can not be read. Other people in my organisation in Australia are also having same problem.
The chat support line is not responding.
The import dialog is the worst step back I have ever seen. It takes away features, is extremely slow, and makes “looks” a priority over functionality. This is supposed to be a professional program, what the hell is wrong with you?
I have some images that I keep in two locations; one set on a portable hard disk, and another on a Drobo attached to my iMac. My portable HDD is my master library, and my Drobo is just for reference and backup, but I like to keep both versions of each image in my Lightroom catalog, so that I can grab an image from the Drobo when my portable HDD is offline, and also to ensure that my backups are not corrupt.
Since I started using Lightroom back in the first beta, this has always been possible. I simply unchecked the “Don’t import suspected duplicates” checkbox, and I was able to add a second copy of each image to my catalog, and work the way I want to work.
Now, with the new import window, this option has disappeared, stopping me from importing some resent work and all future work from my Drobo. I can export the original files from my portable HDD and add them to the catalog at the same time, to circumnavigate this shortcoming, but I have backup scripts in place that copy the files over automatically for me when I attach the portable hard drive, so they are already on my Drobo.
So, how do I add these second copy images now Adobe?
I agree with the others who say the import process is a disaster. Surely it is time for Adobe to front up to their customers and say that you got it wrong. Plug-ins are locked out, crashes everywhere, this release is just awful. I have rolled back to 6.1 and won’t move until the many errors are fixed. Please talk to us.
Not impressed with the import screen – there was nothing wrong with the previous version.
In particular the loss of the panel showing how many images will be imported in to each date folder is greatly missed – please return it.
Lightroom is now broken!
The new, downgraded and degraded IMPORT workflow is a ridiculous step backwards. Not only have extra steps been introduced but critical safety features, such as actually seeing where your valuable photos will go and what they will be called have been culled.
It is not simpler to not be able to see what Lightroom is going to do with my photos. It is not better to not be able to tell how many are being imported to each folder or how many folders, if any, will be created.
What is more, with Adobe taking backward leaps like this I now need to not only roll back to the prior release (a non-trivial waste of time), but also be a paranoid forum reader should any future updates become available, since I cannot afford to waste my time on software updates that remove features that I paid for and used every day.
To be honest, if Adobe is prepared to wreck the photo import process, they are just as likely to wreck the catalog, library or develop functions at some point in the future so that they can be ‘simplified’ for an easier user experience.
I bought Lightroom for a similar reason to my DLSR – control and access to features. If I wanted a dumbed-down point and shoot system I would stick to my phone camera and iPhoto.
Like others have said above, I too really don’t care for the new Import “dialog”.
It seems to have less functionality than the former (perfectly fine) Import dialog, and it just doesn’t fit with the rest of the Lightroom interface. What’s with the rounded (blue) buttons, the non-native checkboxes, different accordions/disclosures, giant text in the titlebar, etc.?
I’ve also experienced a lot of issues with the Import dialog:
* It seems to take longer to appear
* I’ve seen it appear, disappear, then reappear
* Once it Imported my photos, then wouldn’t go away (so I had to restart Lightroom to get back to the Library module)
* It’s two screens now instead of one (first choose device, then choose photos)
* I can no longer minimize the Import dialog to, for example, check which number I want to begin the next sequence/import (something I do quite often)
In addition, I’ve had regular hangups and crashes with this version since installing it yesterday.
I really hope Adobe reconsiders the new Import dialog, or at least offers an “Advanced/Legacy” preferences checkbox to restore the original Import dialog.
If it ain’t broke, (please) don’t fix it.*
* PS. I know the Import dialog was changed because many(?) users found it complicated, but I’ll bet there are just as many (more?) that liked it just the way it was. Thanks for your consideration.
…oh, and Synchronize Folder no longer works either (as someone else also mentioned above).
I also liked the previous import dialog better – what was wrong with it? Adobe may consider this release as an ‘achievement’, upsetting royal (and paying!) customers (since version 1.0 beta) in one single swoop.
I am horrified by the direction Adobe has taken with this latest LR update. the new interface is just the first sign of what we can expect for the future of LR UI.
Sorry professional photographers. Adobe doesn’t care about us anymore. We’re not the customers they want moving forward.
This all stems from a mobile first mentality that is destroying a formerly professional product. Why the big buttons? Because someone on a hybrid device can use their fingers more easily. Why the simplified UIs? Because acolytes of iDevices don’t know how to use real computers.
Adobe is breaking up with us people… They already have a profile up on Tinder.
A whole day gone, and not one single photograph processed, Yesterday was great, Tomorrow???
LR 2015.2 6.2 CRASHES when trying to delete rejected masters
Process: Adobe Lightroom [5524]
Path: /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/MacOS/Adobe Lightroom
Identifier: com.adobe.Lightroom6
Version: Adobe Lightroom [1044713] (6.2)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Adobe Lightroom [5524]
User ID: 501
Date/Time: 2015-10-08 20:27:25.527 -0500
OS Version: Mac OS X 10.11 (15A284)
Report Version: 11
Anonymous UUID: A1A91611-3271-6E12-EFC1-9750B932AA96
Time Awake Since Boot: 34000 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Exception Note: EXC_CORPSE_NOTIFY
Global Trace Buffer (reverse chronological seconds):
11.437369 AppleJPEG 0x00007fff8ea5211c [0x7fdb0dae0800] Decoding completed without errors
11.437533 AppleJPEG 0x00007fff8ea500fc [0x7fdb0dae0800] Options: 2x-1 [FFFFFFFF,FFFFFFFF] 0001D060
11.437533 AppleJPEG 0x00007fff8ea4ffae [0x7fdb0dae0800] Decoding: C0 0x00500026 0x000A354A 0x11111100 0x00000000 2062
11.439353 AppleJPEG 0x00007fff8ea5211c [0x7fdb0e69ac00] Decoding completed without errors
11.439353 AppleJPEG 0x00007fff8ea500fc [0x7fdb0e69ac00] Options: 2x-1 [FFFFFFFF,FFFFFFFF] 0001D060
11.439353 AppleJPEG 0x00007fff8ea4ffae [0x7fdb0e69ac00] Decoding: C0 0x00500036 0x000A354A 0x11111100 0x00000000 2518
11.439353 AppleJPEG 0x00007fff8ea5211c [0x7fdb0e68c000] Decoding completed without errors
11.439353 AppleJPEG 0x00007fff8ea500fc [0x7fdb0e68c000] Options: 2x-1 [FFFFFFFF,FFFFFFFF] 0001D060
11.439353 AppleJPEG 0x00007fff8ea4ffae [0x7fdb0e68c000] Decoding: C0 0x00500036 0x000A354A 0x11111100 0x00000000 1432
11.439353 AppleJPEG 0x00007fff8ea5211c [0x7fdb0dad4400] Decoding completed without errors
11.439353 AppleJPEG 0x00007fff8ea500fc [UNSUP] Options: -619860668×33554559 [FF000000,FFFFFFFF] FFFFFFFF
11.439353 AppleJPEG 0x00007fff8ea4ffae [0x7fdb0dad4400] Decoding: C0 0x00500036 0x000A354A 0x11111100 0x00000000 2700
11.439353 AppleJPEG 0x00007fff8ea5211c [0x7fdb09e53600] Decoding completed without errors
11.439353 AppleJPEG 0x00007fff8ea500fc [0x7fdb09e53600] Options: 2x-1 [FFFFFFFF,FFFFFFFF] 0001D060
11.439353 AppleJPEG 0x00007fff8ea4ffae [0x7fdb09e53600] Decoding: C0 0x00500036 0x000A354A 0x11111100 0x00000000 2488
11.439353 AppleJPEG 0x00007fff8ea5211c [0x7fdb0e65fc00] Decoding completed without errors
11.439353 AppleJPEG 0x00007fff8ea500fc [0x7fdb0e65fc00] Options: 2x-1 [FFFFFFFF,FFFFFFFF] 0001D060
11.439353 AppleJPEG 0x00007fff8ea4ffae [0x7fdb0e65fc00] Decoding: C0 0x00500036 0x000A354A 0x11111100 0x00000000 2079
11.439353 AppleJPEG 0x00007fff8ea5211c [0x7fdb09e47200] Decoding completed without errors
11.439353 AppleJPEG 0x00007fff8ea500fc [0x7fdb09e47200] Options: 2x-1 [FFFFFFFF,FFFFFFFF] 0001D060
11.439353 AppleJPEG 0x00007fff8ea4ffae [0x7fdb09e47200] Decoding: C0 0x00500036 0x000A354A 0x11111100 0x00000000 2432
11.439353 AppleJPEG 0x00007fff8ea5211c [0x7fdb0dabf400] Decoding completed without errors
11.439353 AppleJPEG 0x00007fff8ea500fc [0x7fdb0dabf400] Options: 2x-1 [FFFFFFFF,FFFFFFFF] 0001D060
11.439353 AppleJPEG 0x00007fff8ea4ffae [0x7fdb0dabf400] Decoding: C0 0x00500036 0x000A354A 0x11111100 0x00000000 2282
11.441525 AppleJPEG 0x00007fff8ea5211c [0x7fdb0e63d400] Decoding completed without errors
11.441525 AppleJPEG 0x00007fff8ea500fc [0x7fdb0e63d400] Options: 2x-1 [FFFFFFFF,FFFFFFFF] 0001D060
11.441525 AppleJPEG 0x00007fff8ea4ffae [0x7fdb0e63d400] Decoding: C0 0x00500036 0x000A354A 0x11111100 0x00000000 2120
11.441525 AppleJPEG 0x00007fff8ea5211c [0x7fdb0e633800] Decoding completed without errors
11.441525 AppleJPEG 0x00007fff8ea500fc [0x7fdb0e633800] Options: 2x-1 [FFFFFFFF,FFFFFFFF] 0001D060
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_c.dylib 0x00007fff8e10924b trecurse + 19
1 libsystem_c.dylib 0x00007fff8e10927b trecurse + 67
2 libsystem_c.dylib 0x00007fff8e10929d trecurse + 101
3 com.adobe.ag.substrate 0x0000000108473f51 0x10844d000 + 159569
4 com.adobe.ag.substrate 0x000000010845527d 0x10844d000 + 33405
5 com.apple.CoreServices.FSEvents 0x00007fff88270b0b implementation_callback_rpc + 1917
6 com.apple.CoreServices.FSEvents 0x00007fff8826e6ca _Xcallback_rpc + 254
7 com.apple.CoreServices.FSEvents 0x00007fff8826e79e FSEventsD2F_server + 54
8 com.apple.CoreServices.FSEvents 0x00007fff88273fd9 FSEventsClientProcessMessageCallback + 44
9 com.apple.CoreFoundation 0x00007fff889c7f8c __CFMachPortPerform + 252
10 com.apple.CoreFoundation 0x00007fff889c7e79 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 41
11 com.apple.CoreFoundation 0x00007fff889c7de9 __CFRunLoopDoSource1 + 473
12 com.apple.CoreFoundation 0x00007fff889bf81b __CFRunLoopRun + 2171
13 com.apple.CoreFoundation 0x00007fff889bed38 CFRunLoopRunSpecific + 296
14 com.apple.HIToolbox 0x00007fff8aa8ed55 RunCurrentEventLoopInMode + 235
15 com.apple.HIToolbox 0x00007fff8aa8eb8f ReceiveNextEventCommon + 432
16 com.apple.HIToolbox 0x00007fff8aa8e9cf _BlockUntilNextEventMatchingListInModeWithFilter + 71
17 com.apple.AppKit 0x00007fff8c78bf3a _DPSNextEvent + 1067
18 com.apple.AppKit 0x00007fff8c78b369 -[NSApplication _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 454
19 com.apple.AppKit 0x00007fff8c77fecc -[NSApplication run] + 682
20 com.apple.AppKit 0x00007fff8c749162 NSApplicationMain + 1176
21 com.adobe.Lightroom6 0x00000001082cd9a9 main + 953
22 libdyld.dylib 0x00007fff923f45ad start + 1
Thread 1:
0 libsystem_kernel.dylib 0x00007fff98d6e78a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff95e3d58c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff95e3b375 start_wqthread + 13
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff98d6f0a2 kevent_qos + 10
1 libdispatch.dylib 0x00007fff8f9871ad _dispatch_mgr_invoke + 216
2 libdispatch.dylib 0x00007fff8f986e15 _dispatch_mgr_thread + 52
Thread 3:
0 libsystem_kernel.dylib 0x00007fff98d6e78a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff95e3d58c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff95e3b375 start_wqthread + 13
Thread 4:
0 libsystem_kernel.dylib 0x00007fff98d6e78a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff95e3d58c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff95e3b375 start_wqthread + 13
Thread 5:
0 libsystem_kernel.dylib 0x00007fff98d6e78a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff95e3d58c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff95e3b375 start_wqthread + 13
Thread 6:: Worker Thread Dispatcher
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
7 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
8 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
9 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
10 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
11 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
12 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
13 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
14 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
15 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
16 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
17 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
18 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
19 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
20 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 7:: cr_scratch
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.AgImageIO 0x000000010f016b6b 0x10ee33000 + 1981291
3 com.adobe.ag.AgImageIO 0x000000010f1fd36b 0x10ee33000 + 3973995
4 com.adobe.ag.AgImageIO 0x000000010efe0361 0x10ee33000 + 1758049
5 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
6 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
7 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 8:: Queue Processor – AgPhotoAvailability
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
7 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
8 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
9 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
10 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
11 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
12 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
13 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
14 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
15 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
16 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
17 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
18 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
19 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
20 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
21 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
22 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
23 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
24 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
25 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
26 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
27 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
28 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
29 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
30 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 9:: AsyncDataServer
0 libsystem_kernel.dylib 0x00007fff98d6faaa write + 10
1 com.adobe.wichitafoundation 0x00000001086738a7 0x1085d4000 + 653479
2 com.adobe.wichitafoundation 0x000000010866f68c 0x1085d4000 + 636556
3 com.adobe.wichitafoundation 0x000000010866f2d8 0x1085d4000 + 635608
4 com.adobe.wichitafoundation 0x0000000108665e3f 0x1085d4000 + 597567
5 com.adobe.wichitafoundation 0x000000010865c7da 0x1085d4000 + 559066
6 com.adobe.wichitafoundation 0x0000000108607b79 0x1085d4000 + 211833
7 com.adobe.wichitafoundation 0x00000001085ff101 0x1085d4000 + 176385
8 com.adobe.wichitafoundation 0x00000001085ffd94 0x1085d4000 + 179604
9 com.adobe.wichitafoundation 0x00000001085ffc9d 0x1085d4000 + 179357
10 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
11 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
12 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
13 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
14 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
15 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
16 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
17 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
18 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
19 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
20 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
21 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
22 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
23 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
24 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
25 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
26 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
27 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
28 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
29 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
30 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
31 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
32 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
33 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
34 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
35 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
36 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
37 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
38 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
39 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
40 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
41 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
42 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
43 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
44 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
45 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
46 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
47 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
48 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
49 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
50 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
51 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
52 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
53 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
54 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
55 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
56 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
57 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
58 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
59 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
60 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
61 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
62 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
63 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
64 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
65 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
66 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
67 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 10:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x00007fff98d68c96 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff98d680d7 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff889c0024 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff889bf4ec __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff889bed38 CFRunLoopRunSpecific + 296
5 com.apple.AppKit 0x00007fff8c8e1eed _NSEventThread + 149
6 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
7 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
8 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 11:: Preview Server
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e666 AgConditionLock_wait + 182
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
7 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
8 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
9 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
10 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
11 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
12 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
13 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
14 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
15 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
16 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
17 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
18 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
19 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
20 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 12:: Queue Processor – PreviewFileStore
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
7 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
8 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
9 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
10 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
11 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
12 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
13 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
14 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
15 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
16 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
17 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
18 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
19 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
20 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
21 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
22 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
23 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
24 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
25 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
26 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
27 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
28 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
29 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
30 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 13:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x00007fff98d68c96 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x00007fff98d680d7 mach_msg + 55
2 com.apple.CoreFoundation 0x00007fff889c0024 __CFRunLoopServiceMachPort + 212
3 com.apple.CoreFoundation 0x00007fff889bf4ec __CFRunLoopRun + 1356
4 com.apple.CoreFoundation 0x00007fff889bed38 CFRunLoopRunSpecific + 296
5 com.apple.CFNetwork 0x00007fff943ffc2d +[NSURLConnection(Loader) _resourceLoadLoop:] + 412
6 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
7 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
8 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
9 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 14:: Queue Processor – NegativeQueue
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
7 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
8 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
9 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
10 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
11 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
12 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
13 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
14 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
15 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
16 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
17 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
18 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
19 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
20 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
21 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
22 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
23 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
24 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
25 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
26 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
27 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
28 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
29 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
30 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 15:: Queue Processor – HistogramQueue
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
7 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
8 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
9 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
10 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
11 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
12 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
13 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
14 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
15 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
16 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
17 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
18 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
19 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
20 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
21 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
22 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
23 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
24 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
25 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
26 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
27 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
28 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
29 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
30 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 16:: Queue Processor – RenderQueue_Render
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
7 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
8 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
9 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
10 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
11 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
12 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
13 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
14 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
15 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
16 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
17 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
18 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
19 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
20 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
21 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
22 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
23 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
24 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
25 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
26 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
27 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
28 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
29 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
30 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 17:: Queue Processor – RenderQueue_ReadPreview
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
7 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
8 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
9 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
10 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
11 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
12 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
13 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
14 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
15 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
16 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
17 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
18 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
19 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
20 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
21 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
22 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
23 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
24 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
25 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
26 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
27 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
28 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
29 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
30 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 18:: Queue Processor – RenderQueue_Video
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
7 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
8 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
9 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
10 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
11 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
12 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
13 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
14 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
15 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
16 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
17 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
18 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
19 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
20 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
21 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
22 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
23 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
24 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
25 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
26 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
27 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
28 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
29 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
30 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 19:: Queue Processor – RenderQueue_Face
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
7 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
8 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
9 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
10 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
11 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
12 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
13 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
14 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
15 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
16 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
17 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
18 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
19 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
20 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
21 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
22 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
23 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
24 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
25 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
26 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
27 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
28 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
29 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
30 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 20:: Worker Thread
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
7 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
8 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
9 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
10 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
11 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
12 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
13 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
14 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
15 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
16 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
17 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
18 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
19 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
20 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
21 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
22 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
23 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
24 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
25 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
26 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 21:: Worker Thread
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
7 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
8 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
9 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
10 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
11 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
12 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
13 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
14 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
15 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
16 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
17 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
18 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
19 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
20 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
21 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
22 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
23 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
24 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
25 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
26 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 22:
0 libsystem_kernel.dylib 0x00007fff98d6e162 __recvfrom + 10
1 VulcanMessage5.dylib 0x000000011bbd33e6 vcfoundation::net::Bsd::Recv(int, void*, int, int) + 16
2 VulcanMessage5.dylib 0x000000011bbd265d vcfoundation::io::BSDNamedPipe::Read(void*, unsigned long) + 21
3 VulcanMessage5.dylib 0x000000011bbd1a18 vcfoundation::io::BufferedReader::InternalRead(char*, long) + 82
4 VulcanMessage5.dylib 0x000000011bbd194e vcfoundation::io::BufferedReader::Read(void*, unsigned long) + 50
5 VulcanMessage5.dylib 0x000000011bbcc4f8 vcfoundation::io::IVCChannel::ReadFully(void*, unsigned long) + 46
6 VulcanMessage5.dylib 0x000000011bbcc996 vcfoundation::io::Serializer::InternalDeserialize() + 30
7 VulcanMessage5.dylib 0x000000011bbcc93d vcfoundation::io::Serializer::Deserialize() + 9
8 VulcanMessage5.dylib 0x000000011bbd07c2 vcfoundation::ncomm::Connection::ReadIn() + 22
9 VulcanMessage5.dylib 0x000000011bbd04e9 vcfoundation::ncomm::NCService::ReadResponse(vcfoundation::ncomm::INCRequest*, vcfoundation::ncomm::INCListener&, vcfoundation::ncomm::NCService::ConRef&) + 37
10 VulcanMessage5.dylib 0x000000011bbd016a vcfoundation::ncomm::NCService::Execute(vcfoundation::ncomm::INCRequest*, vcfoundation::ncomm::INCListener&) + 166
11 VulcanMessage5.dylib 0x000000011bbd00bd vcfoundation::ncomm::NCService::Execute(vcfoundation::ncomm::INCRequest*) + 29
12 VulcanMessage5.dylib 0x000000011bbc2f46 adobe::vulcan::servicemgr::CSIRequest::Execute() + 50
13 VulcanMessage5.dylib 0x000000011bbc39c1 adobe::vulcan::servicemgr::RegisterForEventsRequest::Run() + 995
14 VulcanMessage5.dylib 0x000000011bbd12e8 vcfoundation::thread::AbstractThread::Run() + 50
15 VulcanMessage5.dylib 0x000000011bbd2e09 vcfoundation::thread::Thread::ThreadProc(void*) + 9
16 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
17 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
18 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 23:: Worker Thread
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
7 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
8 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
9 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
10 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
11 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
12 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
13 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
14 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
15 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
16 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
17 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
18 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
19 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
20 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
21 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
22 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
23 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
24 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
25 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
26 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 24:: Worker Thread
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
7 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
8 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
9 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
10 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
11 com.adobe.ag.kernel 0x00000001082ebd66 0x1082e7000 + 19814
12 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
13 com.adobe.ag.kernel 0x00000001082f1b3c 0x1082e7000 + 43836
14 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
15 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
16 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
17 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
18 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
19 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
20 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
21 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
22 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
23 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
24 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
25 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
26 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 25:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x00007fff98d6e222 __select + 10
1 com.apple.CoreFoundation 0x00007fff889fd29a __CFSocketManager + 762
2 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
3 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
4 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 26:: AgFileInfoService “/”
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
7 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
8 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
9 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
10 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
11 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
12 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
13 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
14 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
15 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
16 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
17 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
18 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
19 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
20 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 27:: AgFileInfoService “/Volumes/Time Machine”
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 com.adobe.ag.kernel 0x000000010830e5d5 AgConditionLock_wait + 37
3 com.adobe.ag.kernel 0x0000000108308078 AgTransitQueue_dequeueToLuaState + 91
4 com.adobe.ag.kernel 0x0000000108308fae 0x1082e7000 + 139182
5 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
6 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
7 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
8 com.adobe.ag.kernel 0x00000001082e9b36 lua_call + 37
9 com.adobe.ag.substrate 0x000000010846cf0f AgLua_callWithAutoReleasePool + 85
10 com.adobe.ag.kernel 0x00000001082f188f 0x1082e7000 + 43151
11 com.adobe.ag.kernel 0x00000001082ffe83 0x1082e7000 + 102019
12 com.adobe.ag.kernel 0x00000001082f1b4d 0x1082e7000 + 43853
13 com.adobe.ag.kernel 0x00000001082f11ea 0x1082e7000 + 41450
14 com.adobe.ag.kernel 0x00000001082f1da4 0x1082e7000 + 44452
15 com.adobe.ag.kernel 0x00000001082e9bb7 lua_pcall + 100
16 com.adobe.ag.substrate 0x0000000108460a00 0x10844d000 + 80384
17 com.apple.Foundation 0x00007fff957e2084 __NSThread__start__ + 1351
18 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
19 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
20 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 28:
0 libsystem_kernel.dylib 0x00007fff98d6e78a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff95e3d58c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff95e3b375 start_wqthread + 13
Thread 29:
0 libsystem_kernel.dylib 0x00007fff98d6e78a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff95e3d58c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff95e3b375 start_wqthread + 13
Thread 30:
0 libsystem_kernel.dylib 0x00007fff98d6df5e __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff95e3e73d _pthread_cond_wait + 767
2 IMSLib.dylib 0x000000010bba3cd0 0x10bb75000 + 191696
3 IMSLib.dylib 0x000000010bba3c4c 0x10bb75000 + 191564
4 IMSLib.dylib 0x000000010bba39f6 0x10bb75000 + 190966
5 IMSLib.dylib 0x000000010bba2393 0x10bb75000 + 185235
6 IMSLib.dylib 0x000000010bb9a9ab 0x10bb75000 + 154027
7 IMSLib.dylib 0x000000010bb767b4 IMS_releaseRef + 38
8 com.adobe.Lightroom6 0x00000001082d4583 0x1082cc000 + 34179
9 IMSLib.dylib 0x000000010bbb444f 0x10bb75000 + 259151
10 IMSLib.dylib 0x000000010bbb2142 0x10bb75000 + 250178
11 IMSLib.dylib 0x000000010bbb4d2b 0x10bb75000 + 261419
12 IMSLib.dylib 0x000000010bb9b4ee 0x10bb75000 + 156910
13 IMSLib.dylib 0x000000010bb83389 0x10bb75000 + 58249
14 libsystem_pthread.dylib 0x00007fff95e3d9b1 _pthread_body + 131
15 libsystem_pthread.dylib 0x00007fff95e3d92e _pthread_start + 168
16 libsystem_pthread.dylib 0x00007fff95e3b385 thread_start + 13
Thread 31:
0 libsystem_kernel.dylib 0x00007fff98d6e78a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff95e3d58c _pthread_wqthread + 1283
2 libsystem_pthread.dylib 0x00007fff95e3b375 start_wqthread + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000108473a3b rbx: 0x0000000108473a3b rcx: 0x0000000000000012 rdx: 0x0000000000000002
rdi: 0x0084000000000000 rsi: 0x0000000108473a3b rbp: 0x00007fff5792ce60 rsp: 0x00007fff5792ce40
r8: 0x0000000000001000 r9: 0x0000000000000012 r10: 0x000000008fa9844b r11: 0x0000000000000fff
r12: 0x00007fdaf0473d80 r13: 0x00007fdb1766c340 r14: 0x0000000000000002 r15: 0x0084000000000000
rip: 0x00007fff8e10924b rfl: 0x0000000000010206 cr2: 0x00007fdaf3837bfe
Logical CPU: 0
Error Code: 0x02000004
Trap Number: 133
Binary Images:
0x1082cc000 – 0x1082dafff +com.adobe.Lightroom6 (Adobe Lightroom [1044713] – 6.2) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/MacOS/Adobe Lightroom
0x1082e7000 – 0x108329fff +com.adobe.ag.kernel (AgKernel Version 1.0 – 1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/AgKernel.framework/Versions/A/AgKernel
0x108341000 – 0x108405fff +com.adobe.ag.ui (views version 0.0.1d1 – 0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/AgUI.framework/Versions/A/AgUI
0x10844d000 – 0x108495fff +com.adobe.ag.substrate (com.adobe.ag.substrate 6.2 – 1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/AgSubstrate.framework/Versions/A/AgSubstrate
0x1084bc000 – 0x1085bdfff +com.adobe.amtlib (9.0.0.21 – 9.0.0.21) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/amtlib.framework/Versions/A/amtlib
0x1085d4000 – 0x10884afff +com.adobe.wichitafoundation (com.adobe.wichitafoundation 6.2 – 1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/WichitaFoundation.agtoolkit/Versions/A/WichitaFoundation
0x108b7b000 – 0x108b7bfff +com.adobe.lightroom.AdobeCrashReporter (1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/PlugIns/Adobe Crash Reporter.bundle/Contents/MacOS/Adobe Crash Reporter
0x108b80000 – 0x108b83fff +com.adobe.AdobeCrashReporter (7.1 – 7.1.4) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/AdobeCrashReporter.framework/Versions/A/AdobeCrashReporter
0x10bb75000 – 0x10bcacfe7 +IMSLib.dylib (9.0.1.20 – 9.0.1.20) /Library/Application Support/Adobe/*/IMSLib.dylib
0x10bf0e000 – 0x10bf4eff7 +com.adobe.AAM.AdobeUpdaterNotificationFramework (UpdaterNotifications 9.0.0.3 – 9.0.0.3) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/UpdaterNotifications.framework/Versions/A/UpdaterNotifications
0x10d37d000 – 0x10d37dfe7 +cl_kernels (???) cl_kernels
0x10d85e000 – 0x10d85ffff +com.adobe.ag.xml (com.adobe.ag.xml 6.2 – 1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/XML.agtoolkit/Contents/MacOS/XML
0x10ed39000 – 0x10ed54ffb com.apple.security.csparser (3.0 – 57336.1.9) /System/Library/Frameworks/Security.framework/PlugIns/csparser.bundle/Contents/MacOS/csparser
0x10ee33000 – 0x111559fff +com.adobe.ag.AgImageIO (com.adobe.ag.AgImageIO 6.2 – 1.0.0d1) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/CameraRaw.lrtoolkit/CameraRaw
0x111f86000 – 0x111f94fff +com.adobe.ag.video-toolkit (com.adobe.ag.video_toolkit 6.2 – 1) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/video_toolkit.agtoolkit/Contents/MacOS/video_toolkit
0x111fee000 – 0x11202efff com.apple.glut (3.6.3 – GLUT-3.6.3) /System/Library/Frameworks/GLUT.framework/Versions/A/GLUT
0x1120a3000 – 0x1120e4ff7 +com.adobe.ag.bridgetalk (com.adobe.ag.bridgetalk 6.2 – 1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/BridgeTalk.agtoolkit/Contents/MacOS/BridgeTalk
0x112110000 – 0x1121caff7 +com.adobe.ag.imageanalysis (com.adobe.ag.imageanalysis 6.2 – 1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/ImageAnalysis.agtoolkit/Contents/MacOS/ImageAnalysis
0x1121da000 – 0x1122aefff +com.adobe.CIT (2.3.0.33236 – 2.3.0.33236) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/CIT.framework/Versions/A/CIT
0x1122be000 – 0x1122c2ff7 +com.adobe.CITThreading (2.3.0.33236 – 2.3.0.33236) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/CITThreading.framework/Versions/A/CITThreading
0x1123e7000 – 0x1123eeff7 +com.adobe.lightroom.import (com.adobe.ag.import 6.2 – 1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/PlugIns/Import.lrmodule/Contents/MacOS/Import
0x112462000 – 0x112464fff +com.adobe.boost_system.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/boost_system.framework/Versions/A/boost_system
0x11259e000 – 0x1125aaff7 +com.adobe.boost_signals.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/boost_signals.framework/Versions/A/boost_signals
0x1125b8000 – 0x1125beff7 +com.adobe.boost_date_time.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/boost_date_time.framework/Versions/A/boost_date_time
0x112802000 – 0x11280ffff +com.adobe.boost_threads.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/boost_threads.framework/Versions/A/boost_threads
0x11281f000 – 0x11284fff7 +com.adobe.dvamediatypes.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/dvamediatypes.framework/Versions/A/dvamediatypes
0x112a6d000 – 0x112ad4ff7 +com.adobe.dvatransport.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/dvatransport.framework/Versions/A/dvatransport
0x112b22000 – 0x112b4dff7 +com.adobe.dvamarshal.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/dvamarshal.framework/Versions/A/dvamarshal
0x112b71000 – 0x112b95ff7 +com.adobe.dvaunittesting.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/dvaunittesting.framework/Versions/A/dvaunittesting
0x1146fc000 – 0x114a23fff +com.adobe.mediacoreif.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/mediacoreif.framework/mediacoreif
0x114c1d000 – 0x114ebbfff +com.adobe.dvacore.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/dvacore.framework/Versions/A/dvacore
0x114ff3000 – 0x115241fff +com.adobe.dynamiclink.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/dynamiclink.framework/Versions/A/dynamiclink
0x115390000 – 0x115422fff +com.adobe.dvaaudiodevice.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/dvaaudiodevice.framework/Versions/A/dvaaudiodevice
0x115489000 – 0x115545fff +com.adobe.dvaplayer.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/dvaplayer.framework/Versions/A/dvaplayer
0x115605000 – 0x115645fff +com.adobe.dvanet.framework (8.0.0 – 8.0.0.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/dvanet.framework/Versions/A/dvanet
0x1158a4000 – 0x1158f0fff +com.adobe.ag.cef-toolkit (com.adobe.ag.cef_toolkit 6.2 – 1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/cef_toolkit.agtoolkit/Contents/MacOS/cef_toolkit
0x11590c000 – 0x119499f1f +libcef.dylib (31523.6.11) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/Chromium Embedded Framework.framework/Versions/A/libcef.dylib
0x119829000 – 0x11985ffff com.apple.audio.midi.CoreMIDI (1.10 – 88) /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0x119888000 – 0x1198a1fff libexpat.1.dylib (12) /usr/lib/libexpat.1.dylib
0x119a32000 – 0x119a4dff7 +com.adobe.ag.help (com.adobe.ag.help 6.2 – 1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/PlugIns/AdobeHelpClient.lrmodule/Contents/MacOS/AdobeHelpClient
0x119a57000 – 0x119a5afff +com.adobe.ag.headlights (com.adobe.ag.Headlights 6.2 – 1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/PlugIns/AdobeHeadlights.lrmodule/Contents/MacOS/AdobeHeadlights
0x119a60000 – 0x119a9afff +com.adobe.pip (7.3.1.61) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/AdobePIP.framework/AdobePIP
0x119acc000 – 0x119c08fff +com.adobe.headlights.LogSessionFramework (7.3.1.61) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/LogSession.framework/LogSession
0x119cd3000 – 0x119cfcfff +libSLCacheWrapper.dylib (1) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/LogSession.framework/Resources/libSLCacheWrapper.dylib
0x119d0e000 – 0x119d11ff7 +com.adobe.ag.discburning (com.adobe.ag.discburning 6.2 – 1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/DiscBurning.agtoolkit/Contents/MacOS/DiscBurning
0x119d18000 – 0x119d3dff7 com.apple.DiscRecordingUI (9.0.1 – 9010.4.3) /System/Library/Frameworks/DiscRecordingUI.framework/Versions/A/DiscRecordingUI
0x119d5f000 – 0x119d65fff +com.adobe.ag.email (com.adobe.ag.email 6.2 – 1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/PlugIns/Email.lrmodule/Contents/MacOS/Email
0x119d79000 – 0x11a2fbff7 +com.adobe.ag.coretech-toolkit (com.adobe.ag.coretech_toolkit 6.2 – 1.0) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/CoreTechToolkit.agtoolkit/Contents/MacOS/CoreTechToolkit
0x11a51a000 – 0x11a85eff7 +com.adobe.AGM (AdobeAGM 4.30.51.34488 – 4.30.51.34488) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/AdobeAGM.framework/Versions/A/AdobeAGM
0x11a8cc000 – 0x11a8ebfff +com.adobe.BIB (AdobeBIB 1.2.03.34488 – 1.2.03.34488) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/AdobeBIB.framework/Versions/A/AdobeBIB
0x11a8f3000 – 0x11a919ff7 +com.adobe.BIBUtils (AdobeBIBUtils 1.1.01 – 1.1.01) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/AdobeBIBUtils.framework/Versions/A/AdobeBIBUtils
0x11a921000 – 0x11ac46fff +com.adobe.CoolType (AdobeCoolType 5.15.00.34488 – 5.15.00.34488) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/AdobeCoolType.framework/Versions/A/AdobeCoolType
0x11ac8e000 – 0x11addcff7 +com.adobe.ACE (AdobeACE 2.20.02.34488 – 2.20.02.34488) /Applications/Adobe Lightroom/Adobe Lightroom.app/Contents/Frameworks/AdobeACE.framework/Versions/A/AdobeACE
0x11adf0000 – 0x11af1efff +com.winsoft.wrservices (WRServices 7.0.0
I’m not a fan of the new import. I don’t like the splash screen with someone else’s photo in it. I found THAT confusing the first time I saw it. I thought it was trying to import photos that weren’t mine.
I couldn’t find the folder on my hard drive with photos I wanted to import. The list only had folders with photos that had already been imported. I had to turn off “show add photos” screen in Prefs>General before I could find my desktop and the photos I wished to import.
Also, I see that the “move” checkbox has been eliminated, but I actually had some photos MOVED to the destination folder, while others were copied. Inconsistent and confusing. (I’m on Mac OS X Yosemite 10.10.5 and LR CC).
The new Import function is totally unusable. I have no idea where my imported photos are going to go.
Give us back our destinations views.
my feedback for revamped import. i hate it. I hate it. i hate it. Did I mention, that I hate it. Also can’t import .mov files anymore. The old import system was a bit clunky but was much easier to use.
New IMPORT interface is not easier, absolutely makes import process more difficult. I’m totally disappointed by this kind of update.
Here’s the situation: I make small previews to sent to the client/stylist/makeup/whoever. Then I get the names of files from them, so I need to process in post-production only those files. But with new user interface of IMPORT screen I cannot see the names of files for import!!! Imagine, I have a folder with thousands of photos from the photoshoot, and I want to import and process only 10 of them. So now I have to hover mouse over EACH image and wait for floating tip to get its filename! This is 1000% annoying!
Totally dissapointed. Like a step back for lightroom, not step forward.
Import screen is a complete disappointment!
The worst thing is that I cannot see the filenames. I usually get the list of filenames from client/stylist/makeup/whoever, and then import only necessary files to process. With new user interface I need to hover each thumbnail and wait for tooltip – this is ridiculous, complicates the process of importing a lot!
I think this is a huge step back away from users, not the way how people expect Lightroom should evolve.
Ahem, … perhaps Apple needs to resuscitate Aperture. Competition is healthy!
I don’t know what Adobe was thinking or who it might have gotten these suggestions from but it certainly was NOT from Photographers.
No crashes here so far (Using OS X El Capitan) but other than that I agree with everything mentioned above.
I just spent 30 minutes trying to figure what I was doing wrong after the “memory card was not ejected properly” notice.
Thanks Peter for confirming no crashes on El Capitan. We’re looking to improve Import and memory card eject is on our list.
Thanks
Sharad
The new import function is an absolute disaster!! Please give us back the old import function.
One thing I am missing on the import dialog is to back up to a second hard drive. I literally used this for every import. Adobe please bring back this option during import. I assume you made this program for professional photographers as well as occasional photographers. You have dumbed the import functionality down to where it is unusable for the professional.
This option is in the Right Hand panel under the Advanced section. Look for “Make Secondary Copy To:” Check it to enable and choose your second copy destination.
See that, Adobe? Right there? That’s one of the many ways your new import dialog is worse: longtime users – experienced users! – are unable to find features. In the supposedly “better and easier” import dialog. And all of that for the sake of some new users who couldn’t figure out the dialog. LR is not a newbie tool, it’s a professional tool and requires some learning. We all went through that learning curve and now you want to make it harder for us?
Eye candy does not equal usability.
Yes worst upgrade ever to 6.2. Import is completely crap. Slow and close to unusable. I have been in holding pattern for hours while it is doing god know what. Was trying to load 2000 pictures from specific location. Instead I have to wait for it to scan my whole NAS or some other crap. I used to be loyalist and tried to convert anyone interested in photography to get Lightroom. No longer. Why do Stand alone purchasers not get all the features that CC version has such as De Haze. I travel all over the world shooting and believe it there are many places that do not have internet where I am shooting. Great Adobe you view of the world is so small that every who use it must live in a city. Adobe gets all my money up front for the software and I get a less than package. Screw you Adobe. Now figuring out how to roll back to previous version and then find a different software to replace Adobes less than view of the world.
Some features, such as import, did not need updating at all. Please revert import dialog. This new one is next to useless and I will be reverting to a previous version of lightroom until this is fixed.
Overall, I like the update. Although, I really NEED the option to “MOVE” when I import photos to the catalogue.
Please, bring it back.
Why can’t we have the old import back? It just worked and did the job. Now i need even MORE time instead of less time. Buggy Update ..
The latest update for lightroom is unuseable. Crash,Crash,Crash.. Not responding… Not responding… Not responding. Much like adobe to this blog. The software is now unuseable!!!!!!!!!
T. Fisher,
Have you installed CC2015.2.1 yet?
Consider posting details including OS, Version, System Specs, Operations when crash occurs, and any error messages on the support forum at this url: http://feedback.photoshop.com/photoshop_family/products/photoshop_family_photoshop_lightroom
Anyone else having problems with Intel HD530 and lightroom CC 2015.2? I get the blue screen in Develop when I enable the GPU processing. 🙁
Great! Lightroom for Dummies. Your new import dialogue and screen SUCK!!! Is there an option to have an intelligent reversion to the last iteration????
Adobe this is s***. And you know it. I’ve used the stand alone version FOREVER!!! I’m a professional and have been for nearly 20 years. What do you mean that you aren’t including all the features in Lightroom 6? So now you are telling me that the version I JUST BOUGHT is like LIghtroom Elements and NOT a full professional version? I want a refund.
I guess you really are forcing us all into a MUCH MORE EXPENSIVE CC program. I’m really not happy. And frankly – Lightroom 6 has been nothing but slow and caused nothing but heartache ever since I bought it.
If pleasing the masses of “fauxtographers” seems to be your focus; maybe it’s time for me to start looking for another solution.
I keep reading that even buying a MUCH more expensive and faster Mac doesn’t even fix this problem. So please fix it.
Furthermore…exporting often causes Lightroom 6 to crash. You certainly cannot keep editing something else while exporting is occurring. Synchronizing folders isn’t working. It says there are images to import then just doesn’t do it.
Lots and lots of bugs.
In fear of sounding a bit whiny, the new Lightroom update must be someones idea of a joke. I, like many other
professionals, have come to rely on the outstanding performance of Lightroom as a tool in the preparation of images for my clients prior to this update. The entire formate from selecting the source of images to be imported to the preparation of web galleries for client review now have the look of something like flicker or smug mug compete with the appearance of an amateur site demeaning the quality of professional work. What is it that you have taken away? Professionalism? What is it that you have given us we can rest easily with when we finally go home late at night? You also sprung the update on us with the idea that all would be better. Well, it is not and you should really talk with professionals prior to distributing such a heinous update.
I’m trying to import files into the new edition of Lightroom CC. The new UI is TERRIBLE. Quit trying to dumb things down and just give us something that works. How many neophyte photographers do you think are going to buy this…read my lips VERY FEW. This is a professional tool, offer it as such. This is an EPIC FAILURE and I’m wasting hours of valuable time trying to work around this PIECE OF TRASH. I’ll give it a couple more days and if it isn’t fixed, see you later, I’m off to something else.
For some reason the new import won’t recognize my external HD, is this common?
The round robin editing, Lightroom > Photoshop > Lightroom is broken. File doesn’t show on the Library after closing in Photoshop. You have to synchronize it again for it to show.
I haven’t changed anything in the preference. This is really annoying!
Lightroom is working ok for me with the upgrade. I like it, helps my work process as I’m rather chaotic in how I’ve been working with all my photo files. I just wish I could use one of my own photos for the background on the import screen. There should be a check box in the preferences to turn off the background, use a solid color or select an image of one’s own. It does have a bit of a consumer-ish feel to it, I wish they had included a “pro look” option for the import interface.
import is terrible. slow slow slow…….
Why no Eject card function? How did you perceive that we eject the card? Why does my LR import function key now take me directly to the second import screen, by-passing the LR for dummies first screen? Why did you delete the entire Destination panel that held all the folders so you could easily check that you were in the right folder? I’ve found everything else in the new interface but I really don’t think it’s easier. I teach LR and I know what you were trying to do, but I think you missed the mark. I’m also trying to explain all the new features for my LR website but having trouble finding good info…your Help manual says the Eject card option is there!!
P.S. I agree with Josh Glese, I want to use my own photo. It’s somewhat of an insult to see someone else’s photo on my LR import screen!
OK, figured out why the first screen no longer shows. When I un-clicked the Show Import Screen in Preferences it directed the program to skip that first annoying screen. I forgot that I took this action as someone started talking to me right then and I forgot that I had actually done that! So, at least that question is answered. I think it would have been good if Adobe let everyone know they could do this right up front; that you don’t have to have that first screen come up at all.
This update is horrible. It’s hanging when I try to import photos from my iPhone 6. This worked fine before.
The new UI looks pretty but is useless unless basic functionality is working!
Are the comments above correct in saying the app no longer ejects cards after import? How can this be?
So now we need to go to the finder to eject? Is this true? Who thought that was a good idea?
I’ve always thought it was crazy there wasn’t a way to eject the card without importing. Sometimes we put the wrong card in the card reader and need to eject it. There’s should be an eject button next to the card in the import window. The only way to do it is to go to the finder. All other photo apps have this feature. It’s basic stuff.
See this post. You can roll back to the prior 6.1.1 update until things are reverted and corrected: http://blogs.adobe.com/lightroomjournal/2015/10/lightroom-62-import-update.html
Please return the ‘don’t import suspected duplicates’ option in the import dialogue window.
“Select images: The Import Dialog has been redesigned. Your source will already be selected (you choose it in step 1) so you can specify which images to import. We recommend importing all.”
Thanks for your recommendation Adobe, but let us work in a manner that matches our workflow!!!!
See this post. You can roll back to the prior 6.1.1 update until things are reverted and corrected: http://blogs.adobe.com/lightroomjournal/2015/10/lightroom-62-import-update.html
Where is the people view face recognition in Lightroom CC?
Running win7, and the latest updated version of LRCC, on photographer subscription.
No sign of the face recognition functionality anywhere!
Any clues?