LR2.1, Develop Module, and WB

Something I noticed last night:
NEF files from my D90 with WB set for 'flash' on camera, and 'as shot' in
the 'Develop Module' results in color temperature of 6000 and tint -9.
I must use the Develop Module's 'Flash' setting to get the correct temperature of 5500. Is this normal? I've made over 15K D70 NEF images
and I don't recall the Develop Module's WB reacting like this when 'as shot' was selected. I do have 'Camera Matching Profiles' (beta-2) installed. Any ideas?

There are many threads on this subject on the forum over the past year. Have a read of this one.
http://www.adobeforums.com/webx/.59b6becb/10

Similar Messages

  • I have lost my "Basic" panel in the Develop module and can't figure out how to get it back. My right panel goes from the Histogram straight to the Tone Curve panel.  My Basic panel should be below the Histogram.  Any ideas how to get it back.  I have even

    I have lost my "Basic" panel in the Develop module and can't figure out how to get it back. My right panel goes from the Histogram straight to the Tone Curve panel.  My Basic panel should be below the Histogram.  Any ideas how to get it back.  I have even uninstalled my lightroom and reinstalled it with same issue.  Help!!!

    Right click on or near one of the other headers and a pop-up will appear and you will be able to select the Basic Panel for viewing.

  • Lightroom 5.4 64-bit crashes when switching to develop module (and during random other functions)

    This seems to be a new issue that has developed over the past few days. I have been using Lightroom for multiple years without too many issues. Within the last 90 days I have upgraded to Lightroom 5. Today, upon loading up Lightroom (either 3.6 or 5.2) they both crash upon switching over to the develop module. I have upgraded 5.2 to 5.4, uninstalled 3.6, restarted my computer; still crashes with error message: "Adobe Photoshop Lightroom 64-bit has stopped working - A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." Which upon clicking "Close Program" it simply closes the program. Any ideas as to why this is happening and a possible fix? This is greatly impacting workflow. Following is a copy of my System info from Lightroom.
    Lightroom version: 5.4 [955652]
    Operating system: Windows 8.1 Home Premium Edition
    Version: 6.3 [9600]
    Application architecture: x64
    System architecture: x64
    Logical processor count: 8
    Processor speed: 2.3 GHz
    Built-in memory: 7944.2 MB
    Real memory available to Lightroom: 7944.2 MB
    Real memory used by Lightroom: 298.6 MB (3.7%)
    Virtual memory used by Lightroom: 268.0 MB
    Memory cache size: 103.5 MB
    Maximum thread count used by Camera Raw: 4
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    Displays: 1) 1920x1080
    Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 5.4
    Library Path: C:\Users\Joshuah\Pictures\Lightroom\Lightroom 5 Catalog.lrcat
    Settings Folder: C:\Users\Joshuah\AppData\Roaming\Adobe\Lightroom
    Installed Plugins:
    1) Behance
    2) Canon Tether Plugin
    3) Facebook
    4) Flickr
    5) Leica Tether Plugin
    6) Nikon Tether Plugin
    Config.lua flags: None
    Adapter #1: Vendor : 8086
        Device : 416
        Subsystem : fa721179
        Revision : 6
        Video Memory : 0
    Adapter #2: Vendor : 1414
        Device : 8c
        Subsystem : 0
        Revision : 0
        Video Memory : 0
    AudioDeviceIOBlockSize: 1024
    AudioDeviceName: Speakers (Conexant SmartAudio HD)
    AudioDeviceNumberOfChannels: 2
    AudioDeviceSampleRate: 44100
    Build: Uninitialized
    CardID: 1046
    Direct2DEnabled: false
    GPUDevice: D3D
    MaxTexture2DSize: 8192
    OGLEnabled: true
    Renderer: Intel(R) HD Graphics 4600
    ShaderModel: 11.1
    Vendor: Intel
    VendorID: 32902
    Version: 8086:0416:fa721179:0006

    I have had this same issue now. I have been away from my pc for a week or so and now i cannot use the Develop button
    Lightroom version: 5.4 [955652]
    Operating system: Windows 7 Business Edition
    Version: 6.1 [7601]
    Application architecture: x64
    System architecture: x64
    Logical processor count: 8
    Processor speed: 3.5 GHz
    Built-in memory: 32651.3 MB
    Real memory available to Lightroom: 32651.3 MB
    Real memory used by Lightroom: 366.3 MB (1.1%)
    Virtual memory used by Lightroom: 328.1 MB
    Memory cache size: 205.9 MB
    Maximum thread count used by Camera Raw: 4
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    Displays: 1) 1920x1080, 2) 1920x1080, 3) 1920x1080
    Seeming this seems to have stopped around the 21st of May and its now the 9th of June, does this mean we just do nothing about it and hope and pray that one day Adobe, who are very quick to take our money every month, can resolve this ? Has there been a fix noted for this yet ?

  • Color shift between Develop Module and other modules in Lr 5.7.1

    Hello,
    I'm getting a color shift between the devolop module and any other module in Lr.
    It's a recent problem that I've been experiencing since the last update.
    I'm using Lr as part of the Adobe Photographers Bundle in a Windows 8.1 pro.
    Below I have an example for the kind of color shift i'm seeing. The image on the left is from the Devolop Mobule and the one on the right is form the Library Module.
    Is this happening to any one else? Does any one know why?
    I would appreciate any help.

    Gautam is correct in that the preview mechanism isn't the same in Develop and the other modules and, you must view the color in Develop at 1:1 to see an accurate preview. The color space is different that's probably why you see this difference in reds (especially if you use a wide gamut display).
    IF you build your own ICC profiles for your display, be sure the software is not building a V4 (version 4) profile, stick with V2.
    As for exporting and comparing, be sure the secondary application is color managed! Otherwise it's expected that there is a visual disconnect between LR and that app.

  • Relative Adjustments in Develop Module and Presets...

    Hi there,
    the new Lightroom 4 beta is great and has some really good improvements inside (e.g. the "new" shadows/highlight or the new possibilities in the adjustment brush).
    But what I really miss is the possibility to make relative adjustments in the Develop Module. Primary this is useful in presets to make steps of correction. I can do very limited relative adjustments for single parameters partially in the Library Module, but it goes not far enough and I can not save any preset from that or even combinations of adjustments.
    An Example:
    I have an image which is nearly perfect. All adjustments are almost done. Now, I want to give the image a +10 in Clarity or -3 in Brightness relative to all current adjustments. Those relative adjustments are perfectly to increase or decrease simple adjustments stepwise, but also really helpful for stepwise bringing in or out more complex adjustments.
    Another Example:
    I have an image with no corrections. No I can push Clarity, Shadows/Highlights, Saturation etc. from a preset which brings in more and more of a complex set of adjustments, which are just right for this type of image.
    I think, a small checkbox behind a slider would be perfect to set relative or absolute adjustments. This settings should be saved within a preset to make some/all adjustments relative to the exisiting ones, or - if deactivated - absolute adjustment, like in the current version of Lightroom.
    What do you think about that? It would be great to see that in future betas or the final Lightroom 4 product.

    If they've been discussed at length, I'm surprised not to see them. Much has been provided that I would have guessed has received less requests.
    And while I understand that Adobe might simply want feedback on what they have provided, what would be the best forum for letting them know what we feel has not yet been provided.

  • Very different color noise between develop module and library

    There is a marked difference in the appearance of an image when viewed in the library versus the develop module. The color noise in the library module is very bad, while in the develop module, the noise reduction is doing a pretty good job. This is strictly a view problem, because if I export from the library, the proper color noise reduction is applied and it appears as it does in the develop module. This is not the first time that I have found this problem between the two modules. Any idea why this is happening? And, is there a fix in the works? It makes it hard to view images in the library.
    If I boost the color noise reduction up to 100, the library image starts to look ok, but that doesn't account for the huge difference at lower settings.
    There is also a dramatic slow down in the develop module when trying to make any of these changes in noise reduction and more, and also in side-by-side when trying to scroll around in the image to compare areas. Things really crawl. There is a definite two or three second delay before things respond. I have 8gigs in this mac pro, which worked beautifully with LR 3.6

    And, is there a fix in the works?
    Try rendering 1:1 previews for noisy images.

  • Develop Module and Preset Application

    I would love a way to apply my general adjustments to a copy of a photo and reset all adjustment sliders so I can then consistantly apply a Develop Preset.  I have a large number of develop presets that provide me with particular "looks" I use a lot, but these are not "relative" to the global adjustments made correcting the original photo, i.e. exposure, brightness, contrast, etc.  If my photo has these global adjustments made to it and then I apply a preset, it never looks the same as the previous photo I used that preset with.  Even if I make a virtual copy the original slider adjustments are maintained rather than reseting them to a neutral starting point.  Right now, I export my photo as a PSD file to PS and immediately close it and then apply my develop preset to the PSD file to get consistant results.  This is the same reason why people have to develop RAW and JPG presets, which is double the work.

    Not sure if you found a solution or an efficient way to "export" your photo to psd (seems like you "edit in photoshop" and just save) but you could build an Export preset with these options
         same folder as original
         check "add to this catalog"
         existing file = choose a new name for the exported file
         filename = custom text + filename (to end up with something like COPY_originalname.psd)
         file settings / format = PSD or TIFF
         rest leave empty (or as per your preference)
    If you have a large number of files to export, you can go for a coffee (or a full lunch) while it exports. Then you can apply your develop presets to the new image.
    Additionnally you can create a smart collection with filter = filename starts with your custom text (i.e. "COPY_" in the example) to access your copies quickly
    Hope this helps

  • LR2 hang in develop module with graduated filter

    I was in the Develop module and had just used the graduated filter to draw up from the bottom of the image. When I let go of the pen, the hourglass appeared and LR stopped responding. Many minutes later, I finally gave up and clicked on the window's close button. I got the usual Windows "app is not responding" dialog and told Windows to kill lightroom.
    While LR was in the hung state, I started Procmon to see if anything interesting was visible there. While I saw no activity in lightroom.exe, I did see an endless series of operations in csrss.exe. These two operations were repeated endlessly:
    543751 10:32:26.2519678 PM csrss.exe 1372 RegOpenKey HKLM\Software\Policies\Microsoft\Windows\Control Panel\Desktop NAME NOT FOUND Desired Access: Read
    543752 10:32:26.2519724 PM csrss.exe 1372 RegOpenKey HKU\.Default\Software\Policies\Microsoft\Windows\Control Panel\Desktop NAME NOT FOUND Desired Access: Read
    After killing lightroom, I no longer saw that pair of operations.
    I have no idea whether this could be related to the lightroom hang or not, but thought I would pass it on in case it provided a clue.
    Running Windows XP SP2 with all updates (except SP3) applied, nVidia 7600 GT, E6700 Core 2 Duo, 4 GB RAM (3.2 GB available), plentiful hard drive space free. Catalog is new with LR2 by re-importing all images; catalog was not converted from 1.4.1.

    I'm having the same issue with graduated filter and adjustment brush and also one othe the predefined settings, I forgto which one, but it would lock up LR ervery time. My 30 day trial is now over and I think that I'm going to wait for LR2.x to be released :<(...
    WinXP SP2, 3.0GHz Xeon 5260, 4GB, +30GB HD space

  • Photos in Library module and after export look different than in Development module

    Hello,
    I experience a problem.
    After I update photos in the Development module, the updates seem not to be shown in the Library module. And when I subsequently export to Flickr, Flickr is also showing the original photo, not the adapted one.
    I noticed this the first time after making Blacks a bit deeper, causing a sunflower to become a deeper yellow. I thought that my adaptations were not applied in the Library module. After I checked with cranking down the Saturation all the way back (to almost black-and-white), that adaptation WAS applied in the Library view. So it had to be something else, causing the same color difference between the Library and Development modules.
    When I switch from the Library module to the Development module, I see a slight delay in applying my changes, but they are applied. Before they are applied, I can see that the original photo is shown and that looks the same as in the Library module and on Flickr.
    The photostrip on the bottom of the Lightroom screen also shows the original photos only, unless I go to the development module and select a photo (adaptations are applied in the photostrip after I select the photo, not before).
    After I played a bit more in the Development module, I found something strange in the Camera Calibration menu of the Development module. The Adobe Profile (my default) caused an obvious color difference between the Library (less saturated) and the Development (more saturated) modules. The Camera Standard profile also showed a (very) slight difference, but I was unable to notice the differences using the other profiles.
    So I was thinking (but it's only a guess), that the profiles are not applied in the Library view and on export, but they are in the Development module?
    I use Lightroom 5.6, Camera RAW 8.6.
    Please help me, as this is very annoying. I currently cannot export my photos to Flickr or anywhere else, unless I overcompensate before exporting. And I really don't want to do that. My Lightroom photo is my perfect photo, and I want to keep it that way...
    Many thanks in advance for any help,
    Peter

    Hi ssprengel,
    Thanks for your reply. Let me react to each possibility you mention and provide some extra information.
    - "Check your Export / File Settings / Image Format and make sure they are set to JPG not Original". Done that, it's not on Original, but on jpg. This would not explain why I see the difference in the Library and Development modules, by the way. But better to know for sure.
    - "...the most likely thing that is wrong is your color-management on your computer is not working properly". It is a PC with Windows 7. I have been using Lightroom for maybe 6 years and I never had this problem before. The last time I changed my setup is more than a year ago and this problem only started to happen a short while ago (after the update to Lightroom 5.6? I'm not sure, but that's the only thing that has changed lately). I use a Spider to create a custom profile that is correct for my setup and do a regular update on the profile.
    - "what brand and model of monitor do you have?" I have an EIZO FlexScan S2411W and use that for a long time as well. I chose this brand of monitors for its good color reproduction and I have been happy with it for years now.
    What I am not getting is why would all this show a difference between the Library and Development module? The only difference is the Lightroom software that is switching from one module to another, and that should deliver the same photo. I'm also stating in my first post that the differences are very noticeable using the Adobe Standard Camera Profile in the Development module. I have a feeling that the profile is part of the problem.

  • I own LR and Develop module has been disabled---asking for me to renew membership??

    I purchased Lightroom in 2013 (not Creative Cloud subscription). I recently purchased a new computer and downloaded LR to that one. I have LR registered under my Adobe ID and its listed under "products" that I own, I'm signed into LR with my Adobe ID on my desktop. When I downloaded the program, I used my key I received when I purchased the program to get it up and running. Today I tried going into the Develop module and it says that it has been disabled and to renew my membership to get access to the Develop module again. I do not have the CC subscription...I own it. SOOO, I've been searching and trying to follow Adobe troubleshooting for a few hours and now I've decided to see if I can just get the answer here. Where can I input my key in the program on the desktop or get it to see that I OWN the program and do not need to purchase the membership? On my desktop CC icon, it says that my "trial version" has expired.
    Thanks in advance!

    LR Develop module shows "Disabled.Please renew your membership".You can reinstall the creative cloud application from the below link and then sign in with your Adobe ID(email address registered with Adobe)
    https://creative.adobe.com/products/creative-cloud

  • Is vision development module in labview 8.6. sufficient for real-time image acquisition and analysis using a webcam

    Hi, 
    I'm new to labview and trying to develop an eye-tracker using labview 8.6. It has the vision development module and i was wondering if this was sufficient for real-time image acquisition and processing or would i be needing any other software tools.
    Solved!
    Go to Solution.

    Hello, certainly it is possible and sufficient for real-time tracking!
    About eye tracking - if you need an example, you can find the code here:
    https://decibel.ni.com/content/blogs/kl3m3n/2013/10/08/real-time-face-and-eye-detection-in-labview-u...
    The code uses OpenCV functionalities along with the LabView UI (and some other functions like overlay).
    Hope this helps a bit.
    Best regards,
    K
    https://decibel.ni.com/content/blogs/kl3m3n
    "Kudos: Users may give one another Kudos on the forums for posts that they found particularly helpful or insightful."

  • Photos in Develop module look different when switching to library module

    Hello everyone this is my first post on adobe.  I ran into a problem today for the first time using lightroom 5.  I recently purchased lightroom 5 about 2 weeks ago and have been in love using it.  I have ran into 0 problems until today.  I uploaded some new photos and was going through them under the develop module editing the photos and what not.  When I am done editing I usually go to the library module and export them.
    Today I tried to do that exact thing and ran into this issue:  the colors in the photo are changing ever so slightly when I switch to the library module and are not exporting exactly as I edited them in the develop module. 
    I have tried changing the contrast/clarity to see if it would remain when switching and it does.  But for some reason the yellow on the flower in the picture becomes less vibrant when seen/exported from library module.  It is very frustrating because I spend alot of time editing the photo in a develop module and every transfers but the colors it seems.  It becomes more dull and less vibrant.
    It is not the photo itself.  I think it is something wrong with my lightroom?  I uninstalled and reinstalled and the same issue keeps happening.

    Just to clarify. When you compare the exported image to the original inside LR do they look the same when viewed together in the Library module, and how about when both are viewed in the Develop module? Are you using a wide gamut monitor and do you also use a hardware monitor calibrator? All of these things affect how images looks in LR and some are fixable, but others are not as Web Weaver posted.
    There is also another issue that can cause the Library module view and exported images to look different than they do in the Develop module:
    http://feedback.photoshop.com/photoshop_family/topics/afm8rbh6tnc31
    The solution is to view the image at 1:1 (100%) view size. You can also use more conservative Sharpening settings (i.e. lower) and more aggressive Luminance Noise Reduction settings (i.e. higher), which will significantly decrease the view difference.

  • Lightroom crash in Develop module with RAW files with sidecar files from ver 3

    The issue probably has to do with the differences in settings between the two versions but I figured I would document what I am experiencing. 
    I am using the 64 bit version of Windows 7.
    I imported a group of pictures with the XMP sidecar files generated with Lightroom v3.  All the image files, a mixture of Canon Mark 5D II RAW and jpg files from my point & shoot UFO camera, imported without issue picking up all my tagging and GPS settings. When importing you are put into the Library module and from the Library module I could click on any RAW or jpg file, look at the meta data and view full screen.
    I then entered the Develop module with a jpg picture selected and none of my settings made it across. The process was set to 2012.  I was able to try out the new adjustments and all worked very well. 
    I then selected a RAW file while still in the Develop module and all hell broke loose.
    I got a tip window pop up, the film strip went orange, the rest of the app screen then became greyed out and then behind tip pop up a crash window containing this information appeared:
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: lightroom.exe
    Application Version: 4.0.0.1
    Application Timestamp: 4ef2621d
    Fault Module Name: MSVCR100.dll
    Fault Module Version: 10.0.40219.1
    Fault Module Timestamp: 4d5f034a
    Exception Code: c000041d
    Exception Offset: 000000000003c1be
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033
    Additional Information 1: cc7e
    Additional Information 2: cc7e9ac0f4374c9d4c9f2c948a85a235
    Additional Information 3: 41e7
    Additional Information 4: 41e779def86567567ae94271de75e4e9
    There was no other path but to have the app close after that.  Now since Lightroom has left off with the RAW file in the develop module when I restart the app it starts in the develop module with that same RAW image selected and I crash before I can change to a jpg.   I am probably going to have to delete and recreated the data file to use the app again
    After the all this I went back and checked to see how I had the catalog settings in LR 3 set because there were no sidecar files for the jpg images.  I did not have the option to write settings to jpg and tif files but did have write settings to sidecar set.  So I have a bit of a mystery why I have no sidecar files for jpg files when I should have based on the way the settings were.  This probably explains why I had no issues at all with them in LR 4.
    I am going to get LR 4 working again and then import the same batch of pictures without any sidecar files and see if I have any issues.  I will report back soon.
    When I imported the files without the sidecar files I had no issues at all but the RAW images came under older process not the 2012 process. There were no settings without the sidecar files so why would the app not start the images at the most recent process level? I updated then to 2012 and some of the setting sliders changed.  I tried all the adjustment might use with both RAW and jpg files and no issues were observed.
    The new develop module does seem to light darker areas without impacting other lighter areas better.  The brush toll does work better and I see some additional settings were added along with presets.
    As I posted elsewhere, I am disappointed content aware fill and healing were not included.  This is the functionality that would save me from going to Photoshop when I have some undesirable reality in an image.
    I tried out the new geo coding functionality and I really like it as it beats using Google maps on the web (painfully slow these days), dropping latitude / longitude markers, copying and pasting the data from the markers into a Lightroom plug-in and then going through a time consuming three step process.

    Idem for me on Mac:
    No problem to developp a RAW file from a D300 never develop before in LR 3 but when I enter a RAW file develop in LR3 into the develop module of LR4, Lightroom Crash. The report on Mac:
    Process:         Adobe Photoshop Lightroom 4 [412]
    Path:            /Applications/Adobe Photoshop Lightroom 4.app/Contents/MacOS/Adobe Photoshop Lightroom 4
    Identifier:      com.adobe.Lightroom4
    Version:         Adobe Photoshop Lightroom 4.0 Beta [800002] (4.0)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [295]
    Date/Time:       2012-01-13 18:46:19.729 +1100
    OS Version:      Mac OS X 10.6.8 (10K549)
    Report Version:  6
    Interval Since Last Report:          24816 sec
    Crashes Since Last Report:           11
    Per-App Interval Since Last Report:  3225 sec
    Per-App Crashes Since Last Report:   11
    Anonymous UUID:                      B2BF54C2-46B7-4994-A520-D74AD1B91289
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000126c5f000
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Thread 0 Crashed:  Dispatch queue: com.apple.main-thread
    0   com.adobe.ag.AgImageIO                  0x0000000116f384f4 private_load_AgColorProfile + 386306
    1   com.adobe.ag.AgImageIO                  0x0000000116f2e7e7 private_load_AgColorProfile + 346101
    2   com.adobe.ag.AgImageIO                  0x0000000116f2ccdc private_load_AgColorProfile + 339178
    3   com.adobe.ag.AgImageIO                  0x0000000116f2c5e4 private_load_AgColorProfile + 337394
    4   com.adobe.ag.AgImageIO                  0x0000000116f2cb7c private_load_AgColorProfile + 338826
    5   com.adobe.ag.AgImageIO                  0x000000011702773b private_load_AgColorProfile + 1365833
    6   com.adobe.ag.AgImageIO                  0x0000000117029937 private_load_AgColorProfile + 1374533
    7   com.adobe.ag.AgImageIO                  0x0000000116f3f3eb private_load_AgColorProfile + 414713
    8   com.adobe.ag.AgImageIO                  0x0000000116f3f4cd private_load_AgColorProfile + 414939
    9   com.adobe.ag.AgImageIO                  0x0000000116fb8e70 private_load_AgColorProfile + 913022
    10  com.adobe.ag.AgImageIO                  0x0000000117147175 private_load_AgColorProfile + 2544003
    11  com.adobe.ag.AgImageIO                  0x00000001171482d6 private_load_AgColorProfile + 2548452
    12  com.adobe.ag.AgImageIO                  0x0000000116eb7d71 0x116eae000 + 40305
    13  com.adobe.ag.AgImageIO                  0x0000000116ecc4fc AgDevelopSupport_load + 27921
    14  com.adobe.ag.AgImageIO                  0x0000000116ecc6d5 AgDevelopSupport_load + 28394
    15  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    16  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    17  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    18  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    19  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    20  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    21  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    22  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    23  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    24  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    25  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    26  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    27  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    28  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    29  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    30  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    31  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    32  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    33  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    34  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    35  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    36  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    37  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    38  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    39  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    40  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    41  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    42  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    43  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    44  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    45  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    46  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    47  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    48  com.adobe.ag.ui                         0x000000010009b4a5 AgUI_fontFullNameL + 36981
    49  com.apple.AppKit                        0x00007fff884d5d75 -[NSView _drawRect:clip:] + 3566
    50  com.apple.AppKit                        0x00007fff884d354b -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 2112
    51  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    52  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    53  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    54  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    55  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    56  com.apple.AppKit                        0x00007fff884d3ed6 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 4555
    57  com.apple.AppKit                        0x00007fff885f19c4 -[NSNextStepFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topVi ew:] + 276
    58  com.apple.AppKit                        0x00007fff884cf3de -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 2683
    59  com.apple.AppKit                        0x00007fff88448c0e -[NSView displayIfNeeded] + 969
    60  com.apple.AppKit                        0x00007fff883fe5a4 -[NSNextStepFrame displayIfNeeded] + 76
    61  com.apple.AppKit                        0x00007fff88443aba _handleWindowNeedsDisplay + 678
    62  com.apple.CoreFoundation                0x00007fff82f75b07 __CFRunLoopDoObservers + 519
    63  com.apple.CoreFoundation                0x00007fff82f51434 __CFRunLoopRun + 468
    64  com.apple.CoreFoundation                0x00007fff82f50d8f CFRunLoopRunSpecific + 575
    65  com.apple.HIToolbox                     0x00007fff896db7ee RunCurrentEventLoopInMode + 333
    66  com.apple.HIToolbox                     0x00007fff896db5f3 ReceiveNextEventCommon + 310
    67  com.apple.HIToolbox                     0x00007fff896db4ac BlockUntilNextEventMatchingListInMode + 59
    68  com.apple.AppKit                        0x00007fff88418eb2 _DPSNextEvent + 708
    69  com.apple.AppKit                        0x00007fff88418801 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155
    70  com.apple.AppKit                        0x00007fff883de68f -[NSApplication run] + 395
    71  com.apple.AppKit                        0x00007fff883d73b0 NSApplicationMain + 364
    72  com.adobe.Lightroom4                    0x0000000100001c35 main + 1073
    73  com.adobe.Lightroom4                    0x00000001000017fc start + 52
    Thread 1:  Dispatch queue: com.apple.libdispatch-manager
    0   libSystem.B.dylib                       0x00007fff88de9c0a kevent + 10
    1   libSystem.B.dylib                       0x00007fff88debadd _dispatch_mgr_invoke + 154
    2   libSystem.B.dylib                       0x00007fff88deb7b4 _dispatch_queue_invoke + 185
    3   libSystem.B.dylib                       0x00007fff88deb2de _dispatch_worker_thread2 + 252
    4   libSystem.B.dylib                       0x00007fff88deac08 _pthread_wqthread + 353
    5   libSystem.B.dylib                       0x00007fff88deaaa5 start_wqthread + 13
    Thread 2:  Worker Thread Dispatcher
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    9   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    10  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    11  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    12  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    13  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    14  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    15  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    16  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    17  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    18  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    19  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 3:  ace
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   ...ple.CoreServices.CarbonCore          0x00007fff8150dd87 TSWaitOnCondition + 118
    3   ...ple.CoreServices.CarbonCore          0x00007fff8147cff8 TSWaitOnConditionTimedRelative + 177
    4   ...ple.CoreServices.CarbonCore          0x00007fff81476efb MPWaitOnQueue + 215
    5   com.adobe.ag.AgImageIO                  0x00000001170d944f private_load_AgColorProfile + 2094173
    6   com.adobe.ag.AgImageIO                  0x00000001170d9a16 private_load_AgColorProfile + 2095652
    7   ...ple.CoreServices.CarbonCore          0x00007fff8144f0d1 PrivateMPEntryPoint + 63
    8   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    9   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 4:  ace
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   ...ple.CoreServices.CarbonCore          0x00007fff8150dd87 TSWaitOnCondition + 118
    3   ...ple.CoreServices.CarbonCore          0x00007fff8147cff8 TSWaitOnConditionTimedRelative + 177
    4   ...ple.CoreServices.CarbonCore          0x00007fff81476efb MPWaitOnQueue + 215
    5   com.adobe.ag.AgImageIO                  0x00000001170d944f private_load_AgColorProfile + 2094173
    6   com.adobe.ag.AgImageIO                  0x00000001170d9a16 private_load_AgColorProfile + 2095652
    7   ...ple.CoreServices.CarbonCore          0x00007fff8144f0d1 PrivateMPEntryPoint + 63
    8   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    9   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 5:  ace
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   ...ple.CoreServices.CarbonCore          0x00007fff8150dd87 TSWaitOnCondition + 118
    3   ...ple.CoreServices.CarbonCore          0x00007fff8147cff8 TSWaitOnConditionTimedRelative + 177
    4   ...ple.CoreServices.CarbonCore          0x00007fff81476efb MPWaitOnQueue + 215
    5   com.adobe.ag.AgImageIO                  0x00000001170d944f private_load_AgColorProfile + 2094173
    6   com.adobe.ag.AgImageIO                  0x00000001170d9a16 private_load_AgColorProfile + 2095652
    7   ...ple.CoreServices.CarbonCore          0x00007fff8144f0d1 PrivateMPEntryPoint + 63
    8   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    9   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 6:  cr_scratch
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.AgImageIO                  0x0000000116fe717e private_load_AgColorProfile + 1102220
    3   com.adobe.ag.AgImageIO                  0x000000011718f99b private_load_AgColorProfile + 2841001
    4   com.adobe.ag.AgImageIO                  0x0000000116fb7fb9 private_load_AgColorProfile + 909255
    5   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    6   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 7:  AsyncDataServer
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x00000001000415af AgConditionLock_wait + 171
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    9   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    10  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    11  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    12  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    13  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    14  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    15  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    16  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    17  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    18  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    19  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 8:  Queue Processor - AgPhotoAvailability
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 9:  Preview Server
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x00000001000415af AgConditionLock_wait + 171
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    9   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    10  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    11  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    12  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    13  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    14  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    15  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    16  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    17  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    18  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    19  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 10:  Queue Processor - PreviewFileStore
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 11:  Worker Thread
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    9   com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    10  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    11  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    12  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    13  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    14  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    15  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    18  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    19  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    20  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    21  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    22  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    23  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    24  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    25  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 12:  Queue Processor - NegativeQueue
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 13:  Queue Processor - HistogramQueue
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 14:  Queue Processor - RenderQueue_Render
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 15:  Queue Processor - RenderQueue_ReadPreview
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 16:  Queue Processor - RenderQueue_Video
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    7   com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    8   com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    11  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    12  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    13  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    14  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    15  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    18  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    19  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    20  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    21  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    22  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    23  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    24  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    25  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    26  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    27  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    28  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    29  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 17:  Worker Thread
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    9   com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    10  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    11  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    12  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    13  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    14  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    15  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    18  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    19  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    20  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    21  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    22  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    23  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    24  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    25  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 18:
    0   libSystem.B.dylib                       0x00007fff88dd0d7a mach_msg_trap + 10
    1   libSystem.B.dylib                       0x00007fff88dd13ed mach_msg + 59
    2   com.apple.CoreFoundation                0x00007fff82f51902 __CFRunLoopRun + 1698
    3   com.apple.CoreFoundation                0x00007fff82f50d8f CFRunLoopRunSpecific + 575
    4   com.apple.Foundation                    0x00007fff87ebb14f +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 297
    5   com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    6   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    7   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 19:  com.apple.CFSocket.private
    0   libSystem.B.dylib                       0x00007fff88e14932 select$DARWIN_EXTSN + 10
    1   com.apple.CoreFoundation                0x00007fff82f73468 __CFSocketManager + 824
    2   libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    3   libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 20:  Worker Thread
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.kernel                     0x000000010004152a AgConditionLock_wait + 38
    3   com.adobe.ag.kernel                     0x000000010003d007 AgTransitQueue_dequeueToLuaState + 90
    4   com.adobe.ag.kernel                     0x000000010003d125 AgTransitQueue_dequeueToLuaState + 376
    5   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    6   com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    7   com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    8   com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    9   com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    10  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    11  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    12  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    13  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    14  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    15  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    16  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    17  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    18  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    19  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    20  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    21  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    22  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    23  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    24  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    25  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 21:
    0   libSystem.B.dylib                       0x00007fff88deaa2a __workq_kernreturn + 10
    1   libSystem.B.dylib                       0x00007fff88deae3c _pthread_wqthread + 917
    2   libSystem.B.dylib                       0x00007fff88deaaa5 start_wqthread + 13
    Thread 22:  Queue Processor - renderPixmapWorkerThreadQueue
    0   libSystem.B.dylib                       0x00007fff88e0ba6a __semwait_signal + 10
    1   libSystem.B.dylib                       0x00007fff88e0f881 _pthread_cond_wait + 1286
    2   com.adobe.ag.AgImageIO                  0x0000000116fe71de private_load_AgColorProfile + 1102316
    3   com.adobe.ag.AgImageIO                  0x0000000116fb8110 private_load_AgColorProfile + 909598
    4   com.adobe.ag.AgImageIO                  0x0000000116fb8d53 private_load_AgColorProfile + 912737
    5   com.adobe.ag.AgImageIO                  0x0000000117147175 private_load_AgColorProfile + 2544003
    6   com.adobe.ag.AgImageIO                  0x00000001171482d6 private_load_AgColorProfile + 2548452
    7   com.adobe.ag.AgImageIO                  0x0000000116eb7d71 0x116eae000 + 40305
    8   com.adobe.ag.AgImageIO                  0x0000000116ecc4fc AgDevelopSupport_load + 27921
    9   com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    10  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    11  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    12  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    13  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    14  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    15  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    16  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    17  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    18  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    19  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    20  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    21  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    22  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    23  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    24  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    25  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    26  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    27  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    28  com.adobe.ag.kernel                     0x0000000100018af9 luaL_gsub + 1513
    29  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    30  com.adobe.ag.kernel                     0x000000010001f702 luaD_call + 97
    31  com.adobe.ag.kernel                     0x00000001000143a1 lua_call + 47
    32  com.adobe.ag.substrate                  0x0000000100192e15 AgLua_callWithAutoReleasePool + 82
    33  com.adobe.ag.kernel                     0x000000010001f5e0 luaD_precall + 1004
    34  com.adobe.ag.kernel                     0x000000010002e506 luaV_execute + 3218
    35  com.adobe.ag.kernel                     0x000000010001f713 luaD_call + 114
    36  com.adobe.ag.kernel                     0x000000010001eeab luaD_rawrunprotected + 56
    37  com.adobe.ag.kernel                     0x000000010001ef4d luaD_pcall + 80
    38  com.adobe.ag.kernel                     0x00000001000150b6 lua_pcall + 277
    39  com.adobe.ag.substrate                  0x0000000100187231 makeTaskStatusLink_L + 619
    40  com.apple.Foundation                    0x00007fff87e3c114 __NSThread__main__ + 1429
    41  libSystem.B.dylib                       0x00007fff88e09fd6 _pthread_start + 331
    42  libSystem.B.dylib                       0x00007fff88e09e89 thread_start + 13
    Thread 23:  cr_area_task
    0   com.adobe.ag.AgImageIO      

  • Crash in develop module RAW files with sidecar files from Lightroom 3

    The issue probably has to do with the differences in settings between the two versions but I figured I would document what I am experiencing. 
    I am using the 64 bit version of Windows 7.
    I imported a group of pictures with the XMP sidecar files generated with Lightroom v3.  All the image files, a mixture of Canon Mark 5D II RAW and jpg files from my point & shoot UFO camera, imported without issue picking up all my tagging and GPS settings. When importing you are put into the Library module and from the Library module I could click on any RAW or jpg file, look at the meta data and view full screen.
    I then entered the Develop module with a jpg picture selected and none of my settings made it across. The process was set to 2012.  I was able to try out the new adjustments and all worked very well. 
    I then selected a RAW file while still in the Develop module and all hell broke loose.
    I got a tip window pop up, the film strip went orange, the rest of the app screen then became greyed out and then behind tip pop up a crash window containing this information appeared:
    Problem signature:
    Problem Event Name: APPCRASH
    Application Name: lightroom.exe
    Application Version: 4.0.0.1
    Application Timestamp: 4ef2621d
    Fault Module Name: MSVCR100.dll
    Fault Module Version: 10.0.40219.1
    Fault Module Timestamp: 4d5f034a
    Exception Code: c000041d
    Exception Offset: 000000000003c1be
    OS Version: 6.1.7600.2.0.0.256.1
    Locale ID: 1033
    Additional Information 1: cc7e
    Additional Information 2: cc7e9ac0f4374c9d4c9f2c948a85a235
    Additional Information 3: 41e7
    Additional Information 4: 41e779def86567567ae94271de75e4e9
    There was no other path but to have the app close after that.  Now since Lightroom has left off with the RAW file in the develop module when I restart the app it starts in the develop module with that same RAW image selected and I crash before I can change to a jpg.   I am probably going to have to delete and recreated the data file to use the app again
    After the all this I went back and checked to see how I had the catalog settings in LR 3 set because there were no sidecar files for the jpg images.  I did not have the option to write settings to jpg and tif files but did have write settings to sidecar set.  So I have a bit of a mystery why I have no sidecar files for jpg files when I should have based on the way the settings were.  This probably explains why I had no issues at all with them in LR 4.
    I am going to get LR 4 working again and then import the same batch of pictures without any sidecar files and see if I have any issues.  I will report back soon.

    When I imported the files without the sidecar files I had no issues at all but the RAW images came under older process not the 2012 process. There were no settings without the sidecar files so why would the app not start the images at the most recent process level? I updated then to 2012 and some of the setting sliders changed.  I tried all the adjustment might use with both RAW and jpg files and no issues were observed.
    The new develop module does seem to light darker areas without impacting other lighter areas better.  The brush toll does work better and I see some additional settings were added along with presets.
    As I posted elsewhere, I am disappointed content aware fill and healing were not included.  This is the functionality that would save me from going to Photoshop when I have some undesirable reality in an image.
    I tried out the new geo coding functionality and I really like it as it beats using Google maps on the web (painfully slow these days), dropping latitude / longitude markers, copying and pasting the data from the markers into a Lightroom plug-in and then going through a time consuming three step process.

  • Problems with LR4 -  Develop Module - Edit in CS5

    I've just upgraded from LR3 to 4
    When I make adjutments on a RAW or JPEG file in the develop module, and then send it to PS5 for more work, not all the adjustments show up in CS5.
    Example, I cropped an image, and then made local exposure adjustments using the 'brush' tool.
    Exported to CS5 using 'Photo' 'Edit in', and the image goes to CS but only the crop adjustment is showing.
    I've done all the updates on CS, but this is a pain.
    I'm running a MAC with Snow Leopard OS
    Can I uninstall the upgrade and reinstall..?  Would that be any use...??

    I was greatly confused by all this for a while, but think I finally figured it out, thanks to CSS Simon and others here (I'm new to Lightroom, having only used Ps/ACR previously).
    What happens is that "render using Lightroom" doesn't involve ACR at all. It goes straight to Photoshop (and puts the rendered file alongside the raw). The other option, "open anyway", renders the file through ACR. But ACR 6.6 and before can't read PV2012, that's why you need to install the ACR 6.7 Release Candidate, which can (although it doesn't give you access to the 2012-specific sliders).
    Another thing that tripped me up at first was that no Lightroom edits at all would show up in Bridge or ACR, even with ACR 6.7 installed. I finally discovered that I had to set Lightroom catalog settings to "automatically write metadata changes to xmp" - otherwise all Lightroom edits would just exist in the Lightroom catalog and not be visible to other applications.
    This is of no importance if you only use Lightroom, but it certainly is if you have a mixed workflow with Photoshop and Bridge.

Maybe you are looking for

  • My iPhone is stuck in recovery mode and won't restore

    I have an iPhone 4 4.2.10 and it is in recovery mode. I plugged it in to restore it and it still won't restore it gives me a few errors sometimes a (1) or a 3194 error. I dont care if I have to restore it just please tell me how to fix it. I'm desper

  • How to turn off screen redraw while running scripts?

    I am sure this would be the number one question on the FAQ for Photoshop scripting, but I cannot seem to find it anywhere.  I know it may be possible because this is something you can do in InDesign.  Any ideas?  Obviously I want to make Photoshop pr

  • Accessing Selected Value from Payment Terms (Item 47) in AR Invoice Form

    Hi, Have just started working in SAP Business One and SDK adn would really appreciate any help I could receive. I'm trying to access the selected value from Payment Terms field(Item 47) in the AR Invoice Form. Have successfully managed to do this aga

  • How do I export a movie from imovie to a particular mobileme album

    The Mobileme Gallery option in the Share menu of iMovie does not provide for exporting to a particular mobileme album. What is the best way to do this?

  • Value questions for SAP HR Reporting

    I am working as a "SAP HR Functional consultant". I am preparing Value Questions that can benefit End users with respect to SAP HR Reporting. Could you kindly help me by sending some questions [If you have any ] & Also tell me how to prepare them? <b