Lightroom 5 - sync in develop is erratic
In develop, when I select a group of images in the thumbnail filmstrip at the bottom and apply snyced settings, lightroom will sometimes apply these settings to the next image I select, even though it wasn't highlighted when syncing. Also there is some erratic behavior with synced files sometimes reverting back to their original settings when I move on. Will this be addressed in the next update?
This is not the normal behavior of Lr.
If it persists I would suggest that you replace the Preference File.
This file can go "funny" and is then responsible for all kinds of strange behavior of Lr. The remedy is replacing the Preference File.
BTW: Re-installing Lr does not replace the Pref. File since it is designed to "survive" upgrades / updates / re-installations.
See here for where to find the Preference file for your OS: http://helpx.adobe.com/lightroom/kb/preference-file-locations-lightroo m-4.html
See here for how to go about Replacing the Preference File: http://lightroomers.com/replacing-the-lightroom-preference-file/745/
Similar Messages
-
Question?
I have accidentally deleted a large number of develped images in Lightroom before I did a backup. I reimported the original raw files back into Lightroom hoping the develop settings would be re-established but no luck. Notice system mau have done an auto-backup as have an lrcat-journal file. Can I use this to restore my develop settings. I also have jpgs generated from all the deleted images.Hello,
if you have a backup of your catalog you can do the following:
1. Backup your catalog first
2. Restore your backup catalog to some location
3. Open your current catalog and select "files->import from another catalog".
4. Select your backup catalog and your lost images. LR ask you if you want to overwrite the current settings or save them as a virtual copy.
As an alternativ you can open your backup catalog, select the "lost" images and save the development settings as xmp sidecar fiels (using ctrl-s). Then open your current catalog, seletct the images and use "Metadata->Read Metadata from files". -
I am using Lightroom 5.5 on OS X. I have created several small collections with about 180 images and I am trying to sync them via Lightroom mobile for later iPad access. The first collection syncs properly, and then Lightroom syncing seems to hang. The label in the upper right shows "Syncing 150 photos" but does not count down. Opening and closing LR does not restart the process.
PROBLEM STILL EXISTS...
I spoke to soon! I tried adding a couple of more collections to sync. Lightroom shows "Syncing 814" photos on upper left, but never apparently syncs any. If I exit Lightroom it notifies me there are 814 images to sync. When I reopen it seems to pick up and stall where it left off. These new collections are not posting - this is the same problem as before.
I am pretty sure there is a serious bug in Lightroom here. I encourage support to contact me. -
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 -
LightRoom 4 Trial: Develop not working
Hi There. I just downloaded the Trial Version of Lightroom 4 for mac. I imported photos and they in a catalogue. When i select a photo then click the "Develop" tab I get a message that says "no image selected". I have watched a few different videos and tried multiple things but It seems that the develop module is not available on the Lightroom Trial. However, I have read on these forums that the tutorial does not block any features that the full version does not have. Can anyone explain what I might be doing wrong?
Thanks -JonThis happened to me too. Just downloaded LIghtroom4 trial today, could not get any photos to stay selected into Develop mode. No thumbs were loading in film strip. Restart fixed it, so thanks for posting both issue and tip.
-
Lightroom 4.1 Develop Module Preview Problems
Hi All,
I have been using LR4 and now 4.1 since beta and subsequently the first release and now 4.1RC. I too have been irritated by the lack of responsivness compared to LR3.6 but in 4.1 it does seem to have improved. BUT the problem I am seeing is that the preview image in develop module chnages to a lower res and muddier looking version as I drag most of the various adjustment sliders, once the slider is realeased the image refreshed to a better resolution version. This happens in all panels from Basic to Detail and even Effects. It is almost as if Adobe are increasing the apparent speed by applying the adjustment to a low res embedded file first and then to the full RAW data in the background. On detailed images it is more irritating that the slow develop module in LR4.0 as it makes adjustments impossible to preview until the slider has been deslected. The same occurs if you select the slider setting digits and advance using the cursors. Very frustrating indeed. I will be going back to LR4.0 and fingers crossed that this is resolved when LR4.1 is reeased in full.
My PC is fairly good, Win 7 64bit with Quad Intel 9550 cpu (2.83Ghz) with 8Gb ram, GTX-260. I have the same problem at work with a dual cpu (8 cores total) Zeon 5365 (3.0Ghz) and 12Gb Ram & Quadro FX4600. The problem does not seem to manifest in the second display preview but this is laggy and obviously not any use for setting local adjustments.
Anyone else had a similar issue to this? I cant find any reference to it on the web or these forums.
BGhibbyI have exactly same symptoms as Dave Mayfield.
Except I moved images to sub-folders and renamed them, from within Lightroom.
After it locked up, it did not show sub-folders in Library and all the images have question marks on them. If I show it where the file is in Explorer, it does not show any changes.
I Imported one folder and it could see the images in the folder.
Some were without any changes.
Some were the final edited configuration, but not change history shows in Develop. It is if it kept an Exported fersion.
HELP!
Jack Lane -
Lightroom 2.2 Develop Module Lockup Problems
I have a Windows XP SP2 system with the following specs:
AMD 64 X2 4400+ processor
2GB of Ram
Nvidia 6600GT Graphics (128mB ram)
NView shut off
3D settings: performance
Norton Internet Security 2009 with Lightroom, cache and image file types excluded from scans
The problem that I am experiencing is as follows:
When I am editing an image in the develop module, the Lightroom application will randomly freeze. When the application freezes, the title bar of the Lightroom application window will revert to the blue bar that is the default for the active window within Windows and the cursor symbol will switch to the hourglass and the Lightroom will be completely unresponsive. Sometimes, the problem will clear itself in 30 60 seconds time and the program will become operational again. But, on other occasions it will remain completely locked up and will require a forced shutdown and restart of Lightroom using Control-Alt-Delete.
This problem started with Lightroom 2.0 but occurred infrequently. With Lightroom 2.1 and 2.2, the lockups occur much more often. Also, I have had one instance where the computer completely locked and I had to do a forced shutdown of the entire computer with the power button. When I attempted to restart Lightroom, it complained about not being able to read the database and shut itself down. I started the application again and it came up but appeared to have reverted to an older database backup as I lost all of the edits that I had made during this working session.
I havent been able to determine any specific task that triggers the lock up but I am using the develop module and am doing tasks like selecting another image on the filmstrip, making an adjustment or selecting another tab in the develop pane.
I have updated my nVidia driver to the latest released version as I thought that this might help but I didnt see any changes following the update.
This problem never occurred with Lightroom versions 1.x and my system is very stable otherwise. I treated the temporary lockups as an annoyance but having the database not be readable after the forced shut down of the computer is extremely concerning to me.
I love the idea of Lightroom and plan to stay with it but I need help in resolving this issues. Thanks in advance for your suggestions.
Dave MayfieldI have exactly same symptoms as Dave Mayfield.
Except I moved images to sub-folders and renamed them, from within Lightroom.
After it locked up, it did not show sub-folders in Library and all the images have question marks on them. If I show it where the file is in Explorer, it does not show any changes.
I Imported one folder and it could see the images in the folder.
Some were without any changes.
Some were the final edited configuration, but not change history shows in Develop. It is if it kept an Exported fersion.
HELP!
Jack Lane -
Lightroom 2.0 Develop Control Speed Issue?
Hi, just upgraded from Lightroom 1.4.1 to Lightroom 2.0.
First off, a big hats off to the fantastic talents at Adobe for putting out a pretty great release with some killer features. I am really enjoying the update---particularly the awesome camera profile feature----now my reds and oranges from my Canon DSLR are exactly as I expected them to be.
Now a problem I seem to be noticing (before commenting please check below the problem text to see my setup and also the things I have already done to resolve the issue):
The Problem:
I notice that when I am in the Develop module and manipulating the controls to do my edits that compared to version 1.4.1 the controls seem to be a good deal less smooth (in that I mean it is a good deal more difficult to get nice smooth fine controls---rather it seems jumpy and moves in coarser increments). This just might be my mind, but when I enable a second monitor the controls seem to be even more jumpy or less smooth).
To make sure I wasn't imagining things I opened up another catalog of images in version 1.4.1 (a catalog that hadn't yet been converted over to the new 2.0 version) and carried out the same edit. In version 1.4.1 the controls were extremely smooth and moved so finely that I was able to get 1 digit changes very easily with my mouse.
What I have already done to resolve this problem:
1. I have properly updated my catalog to the 2.0 version.
2. I have optimized and restarted the catalog.
3. I have made sure that auto write to XMP was NOT enabled.
My system (fairly new and fairly powerful):
--Macbook Pro 2.5 Core 2 Duo Penryn
--4 GB of RAM
--Catalog on fast RAID drive setup for 0 connected via Firewire 800 (same as before the lightroom update)
--Free space on Macbook Pro is about 150GB
--512 GeForce 8600M GT Nvidia card
The Questions:
Is anyone else having this problem? Also does anyone think this might have anything to do with recent news about 8600M GT cards going bad---perhaps Lightroom 2.0 takes advantage of the GPU more so than 1.4.1 did? If Lightroom 2.0 is indeed taking advantage of the graphics card more than 1.4.1 does anyone think that 2.0 might over working the graphics card and therefore allowing the card's flaw to show through in jittery UI controls?
Other thoughts?
Thanks in advance for people replying to this post.I also have a problem with the adjustment brush. Very slow and jerky to use, almost useless with larger brush. If I try to adjust the slider once an area is selected it can take >4s to update and if a bit hesitant in moving the slider each tiny movement gets interpreted as a new command and the display gets updated every 4s until it runs out of commands in the buffer. Also I get the problem with the sliders remaining coupled to the cursor even when it is somewhere else entirely. At first I thought it was operating like the curve region sliders but something else is happening.
Using
LR2 full
XP Pro SP2
dual core pentium 3.2GHz
4Gb RAM
Matrox Millennium P650 PCIe 128
>40Gb free space all drives
cache on different drive to program
Wacom tablet -
I am sure this topic has been beaten to death, but I have yet to find an answer.
First off, my sync speeds are painfully slow. I have 50 Mbs down and 5 Mbs up on my ISP so speed isn't an issue on my end. I tested my connection speed while Lightroom wasn't even open and very little network activity was taking place.
Now, Lighroom has been stuck on the same photo count in the "status" area showing the sync for hours. I have tried restarting Lightroom a couple times to restart the connection with no luck in getting anywhere.
Has anyone found a solution to this? I really want this sync between Lightroom desktop and mobile to work, but so far it seems to be great in concept.
I am using Lightroom 5.5 on an iMac running Mavericks.I'm not entirely sure what status you're in right now from the thread - whether you stuck in his sync or it's slow?
And what steps have you taken to get into the situation you're currently at? You're syncing a lot of images, so did you just start sync by logging in, then selecting all these collections for sync and then waiting for it to sync? Or have you performed any steps in the meantime? Are you syncing new images both from your desktop to your devices and from the devices back to the desktop at the same time?
According to the log you have been running for ~8 hours and synced ~3000 photos. That's not great performance overall, but it's also not bad enough to make me sure that there's something going wrong here.
If it's just going slowly, does stopping Lightroom and restarting speed things up again? We shouldn't really be getting much slower over time with those image counts, but it's possible there is some issue there that we haven't caught.
-Guido -
Lightroom libary and development tool shows different colors
My problem is, that photos are shown different in color between libary and development tool in Lightroom 3.6. The libary shows corrected color in photos, the development tool not.
When I switch between libary and development tool sometimes, the development tool shows then the same colors.
AlfredIs your monitor profiled and calibrated, with a hardware tool (e.g. Spyder, Colourmunki etc)?
If there's no profile, or it's faulty, there can be problems. In Develop module LR uses ProPhoto RGB colour space, but in Library module it uses Adobe RGB. They'll look different if colour management isn't working, which requires a monitor profile that contains colour space information. -
Lightroom 2 save develop settings after folder remove?
I just upgraded to Lightroom 2 and notice that it doesn't save images' develop settings after I remove the folder from the library. So next time I reimport that folder, my develop settings previously applied to those images are gone! Anyway to fix this?
>Frankly, I don't quite understand what's going on.
Neither do I. x.x
Here is an example of what's going on.
I import a photo.
I edit that photo in Dev Module such as recovery, clarity and noise reduction(Luminance).
As I opted for "automatically write changes into XMP", now I've got those changes in the XMP sidecar file as well as in the Lightroom 2 Catalog.lrcat.
At the same time, I have now 4 lines of History including 'Import'(Highlight Recovery, Clarity, Luminance Smoothing)
Quite normal and no problem until here.
When I open that photo several days later, I suddenly have that little up-arrow icon(meaning "metadata was changed externally").
And the photo is like the one I imported without three changes I made above.
Naturally, in History, there is only one line, 'Import'.
Now I have two option,
1. "import Settings from Disk"
2. "Overwrite Settings"
If I chose 1, I have my edited photo back with 3 changes above. It's from XMP (or Catalog), I guess. However, 3 lines of changes in History disappear and only 'Import from metadata' and 'import(date and time) remain. So I can't really use history to see what exactly I've done with that photo. (Well I still can see each change with the right side panel but it's not as quick and convenient as History.
If I chose 2, of course, I lose both my edited photo and 3 lines of History. It's just as if I imported from my Compact Flash. -
Lightroom 3.0 Develop Issue: Can't Access Develop Module
Hello. Need to tap you guys' expertise!
Went into develop module on my Lightroom 3.0 run on Windows Vista. Did some editing with the color, closed the color I was working with, opened and used a new color, went to erase and the pic disappeared! Screen faded. I closed the program, re-entered my LR and this message showed up on a wide empty screen:
?:0:attempt to compare number with string
I exited the message box and went into my Library. Then, after finding pics, hit the develop module tab, would not come up. Same message appeared. I can access everything else in my LR but the develop module. I have tried to reboot the computer and re-access LR, not successful as message still appears. Tried closing and re-opening LR, but the same thing happens. Not sure what happened as this never happened to me before.
Can anyone offer any insight as to what may have happened and what I can do to fix this problem? I am pulling my hair out as I have pics to finish and cannot make any changes on any of them! Ugh! HELP!!!!! Grrrrrr...........Just wanted to point out that re-installing Lightroom hardly ever solves a problem.
Updating to the latest version usually will do.
Should the preference file deletion not solve the issue, try to create a new catalog and just import the images you need to get ready urgently.
Better to start over with them than not getting anything done.
You can always import from this partial catalog afterwards, when you will have restored the rest.
This should address catalog corruption.
For same root cause you could also try your last backup(s) of catalog.
User presets could be the culprit, as well (move them hiding from LR).
Worst case: LR is an early detection means for damaged RAM...
I wish you a speedy solution,
Cornelia -
Lightroom 1.1 Develop Module - Film Strip
I noticed in lightroom 1.0 the film strip at the bottom of the Develop module would show if you had made any adjustments to the Photo's by placing a small box with a + and - sign, this seems to be missing in 1.1 is there a way to enable this function.
This must be thread number ten or so on the exact same issue. Make the flimstrip just a shade bigger.
-
Hi,
I need to overcome 3 inter-related challenges in my current Adobe Lightroom project.
Here is the situation:
1) I have got an online database which stores individual image records. I've written a Lightroom export plugin for my clients to upload their images to our server and adding records to my online database. Ideally, for each image they have uploaded, I would like to add a database id reference to their images in Lightroom. My first question is : What would be the best approach to write the database reference to an image in Lightroom? EXIF? Metadata? Keywords?
2) Once I've got the images from my clients, I take those images and I create a separate Lightroom catalog and import those images into that catalog on my computer. I then modify those images for my clients and what I want to do next is to export those changes that I have made and return it to my clients. I do not want to export them as separate images to save large transfers, I just want to export the changes. Is there any ways in Lightroom that allows me to achieve that?
3) Finally, if number 2 is possible and I am able to export the changes in some kind of export file(s). Is there anyway for my clients to sync their images with the changes that I made? Updating their images in their existing catalog on their computer.
Thanks in Advance,
SimonHi Rob,
Thanks for the reply. I will go look into custom metadata for 1).
However, for 2) & 3) I have tried doing what you suggested. It seems to only give me the option to import the modify images as new images instead of updating the existing one on the client's catalog. I think when I import the client's images on my catalog it import them as brand new images and when I pass my catalog back to them. The client's Lightroom doesn't recognise the importing images already exisited in their catalog and the image path is not referring to their local copy but to mine. What I want to export is only what I have done to the image (since LR is lossless) so the data transfer would be minimal.
Hope this make sense...
Thanks
Simon -
Lightroom hang when development modeule selected
I just installed lightroom 2 a few days ago. My window XP hung after select development module.
I have 3 gig of memory. I do not believe memory is the issue. I search the web and seems to be a known
issue of getting hung in lightroom 2.Is there any solution for this hang problem?I had the same issue several months ago (can't remember which version of LR2)
If you are using an Nvidia graphics card, disabling the Nview desktop manager may improve things.
Maybe you are looking for
-
JSP portlet built in Jdeveloper call stored procedure
Hi, I have a simple jsp portlet built with Jdeveloper, now I'm trying to execute a stored procedure from the jsp. How can one access database and call a proc, in a jsp which is developed in Jdeveloper? Is JSTL required for it or a normal jdbc calls w
-
Server-Side Include Issue - Please Help
I am having trouble using server-side includes in Dreamweaver. When I use the SSI to insert the header file, the header document shows up on the page in design view, but I cannot click anything. The cursor turns into a "no sign" no matter where it is
-
Change weather icon to show local Camp Hill, PA
The Weather icon shows 73 degrees for some location it came pre-set with and I want it to show the current Camp Hill, PA which is one of the sites I setup.
-
Photoshop CS3 Save and Save As Dialog box not working
I can't do a "save as" or "save for web" in photoshop cs3. The dialog box opens and I can't change anything but the file type pull down menu (and sometimes not even that). This problem happens sporadically.... but most of the time it doesn't work. I
-
Replacing PSU on Quicksilver G4
Hi there, I have a 10 year old Quicksilver G4, and have arrived at the conclusion that the power supply needs replacing. I have tried to follow the instructions on the apple web site http://docs.info.apple.com/article.html?artnum=58769 However, I can