LR Mobile syncing

I've created a collection in Lightroom to sync with LR mobile and on my iPad it says "uploading 1 pending". It's been at least an hour since I created the collection and it still says the same thing. Is there something with the new share feature that I need to do? I really don't want them to be public, I just want them on my iPad.

The images on the iPad do seem to match (at least as close as possible given the differences of viewing on a calibrated matte monitor versus a glossy Retina iPad). I notice that if I make a tint change in desktop Lr all values sync with matching values on Lr Mobile. It's the initial default develop settings that do not match. In fact, if I try the following I get more weirdness:
Import photo to desktop Lr applying develop defaults.
Sync to Lr Mobile. Values as explained in my first posting do not show identical values.
Make a dramatic tint adjustment (+150) on desktop.
Synced photo in Lr Mobile shows the change and shows identical values in both apps.
Click Reset in develop module on the desktop so image has default values.
Synced photo shows up on the iPad as visually similar to the desktop but the tint value on Lr Mobile remains as +150
By the way, I am running desktop Lr on a Windows 7 machine.
One more thing: the mobile app seems to quickly drain the iPad Air battery. My IPad is just one week old (only two recharges) and .5 hour of Lr Mobile testing has drained it by 10%.

Similar Messages

Mobile Sync Client does not save password properly

The Mobile Sync Client (simple_sync_android application provided with Oracle DMS) does not appear to save password correctly. When you select the checkbox to Save Password, my guess is that it stores an encrypted password but then does not return the decrypted version of the password. As a result login fails with the error
Encountered error: Server error, id = 2,001: "USER_INVALID in external auth; logon denied."
For details, check out the "My Experience" section at http://oracledms.blogspot.in/2012/08/sample-app-step-2-install-mobile-sync.html
Obvious workaround: Type in the password again and click Sync

Hi there,
You may find the troubleshooting article below helpful.
iTunes 10.5 and later: Troubleshooting iTunes Wi-Fi Syncing
http://support.apple.com/kb/TS4062
-Griff W.

Problems with relocating mobile sync folder - mac

Hi
This is directed solely towards mac users. I know that there is a similar thread which got somewhat swamped by windows users
Currently i have a intel core duo mac mini running SL with a LaCie external hard drive and I want to move my iPad back up the LaCie disk. Using the directions from various forum's I've done the folowingusing symbolic links to redirect the back up for mobile sync to my external hard drive
Copied and pasted the backup folder onto the external drive under the iTunes folder
Renamed the orginal back up folder as backup1
The command that i put in terminal was as follows
ln -s /Volumes/LaCie\Disk/iTunes\1/Backup Users/iain.christie/Library/Application\Support/MobileSync/Backup
All went well, a link appeared in the mobile sync folder on the C Drive. However when I went to do a back up I got the message that there was not enough space on the disk ( the iPad is 64gb, available disk space is 120 gb). Checking the back up folder on the external drive, a backup does seem to have been attempted, so the link did seem to be redirecting from the C Drive
Can anyone help?
One other thing, the mobile sync folder does not appear to be under the root directory and I had to go under user profile to find it. Would that have any bearing
Appreciate any advice

i have exactly the same problem, also iphone 5 and ios 8.1.3. it extremely irritating.

Lightroom Mobile Sync - Extremely High CPU Usage/Sync Process Causes LR To Lag

Since my other thread doesn't seem to be getting any responses, I'm pasting what I've found here. Please keep in mind I am not a beginner with Lightroom and consider myself very familiar with Lightroom's features excluding the new mobile sync.
1st message:
I'm on Lr 5.5 and using the 30 day trial of Adobe CC to try syncing one collection of slight more than 1000 images. Despite already having generated the Smart Previews, I can see my CPU crunching through image after image (the rolling hills pattern in the task manager) while doing the sync. I was assuming, since I already created the Smart Previews, that the sync of this collection would begin immediately and be done by simply uploading all of the existing Smart Previews. The Smart Previews folder of the catalog is 871MB and has stayed the same despite the CPU obviously doing *something*. As it is now, the sync progress is incredibly slow, almost at a pace like it's actually exporting full-res JPGs from the RAW images (as a comparison only, I know this should not be what it's actually doing).
Another side effect of this is that I'm basically unable to use my computer for other tasks due to the high CPU utilization.
Win 7 x64 / Lightroom 5.5
Intel i5 2500k OC'd 4.5GHz
16GB RAM
SSD for OS, separate SSD for working catalog and files
2nd message:
As a follow up, now Lightroom thinks all 1026 photos are synced (as shown in "All Sync Photographs" portion of the Catalog though all images after the 832nd image show the sync icon per image stuck at "Building Previews for Lightroom Mobile" and the status at the top left corner has been stuck at "Syncing 194 photos" for over 12 hours. Is there no option to force another sync via Lightroom Desktop and also force the iOS app to manually refresh (perhaps by pulling down on the collections view, like refreshing via the Mail app)?
3rd message:
One more update, I went into Preferences and deleted all mobile data, which automatically signed me out of Adobe CC and then I signed back in. Please keep in mind the Smart Previews were long generated before even starting the trial, and I also manually generated them again (it ran through quickly since it found they were already generated) many times. Now that I'm re-syncing my collection of 1026 images, I can clearly see Lightroom using the CPU to regenerate the Smart Previews which already exist. I have no idea why it's doing this except that it's making the process of uploading the Smart Previews extremely slow. I hope this time around it will at least sync all 1026 images to the cloud.
4th message:
All 1026 images synced just fine and I could run through my culling workflow on the iPad/iPhone perfectly. Now I'm on a new catalog (my current workflow unfortunately uses one catalog per event) and I see the same problem: Smart Previews already generated but when syncing, Lightroom seems to re-generate them again anyway (or take up a lot of CPU simply to upload the existing Smart Previews). Can anyone else chime in on what their CPU utilization is like during the sync process when Smart Previews are already created?
New information:
Now I'm editing a catalog of images that is synced to Lightroom Mobile and notice that my workflow has gotten even slower between photos (relative to what it was before, this is not a discussion about how fast/slow LR should perform). Obviously Lightroom is syncing the edited settings to the cloud, but I can see my CPU running intensively (all 4 cores) on every image I edit and the CPU utilization graph looks different than before I started using LR mobile sync. It still feels like every change isn't simply syncing an SQLite database change but re-generating a Smart Preview to go with it (I'm not saying this is definitely what's happening, but something is intensively using the CPU that wasn't prior to using LR Mobile).
For example: I only update the tint +5 on an image. I see the CPU spike up to around 30-40%, then falls back down, then back up to 100%, then back down to another smaller spike while Lightroom says "Syncing 1 photo". I've attached a screenshot of my CPU graph when doing this edit on just one image. During this entire time, if I try to move onto edit another image, the program is noticeably slower to respond than it was prior to using LR mobile, due to the fact that there appear to be much more CPU intensive tasks running to sync the previous edit. This is proven by un-syncing the collection and immediately the lag goes away.
I'd be happy to test/try anything you have in mind, because it's my understanding that re-syncing photos that are edited that are already in the cloud should be simply updating the database file rather than require regenerating any Smart Previews or other image data. If indeed that's what it should be doing, then some other portion of LR is causing massive CPU usage. If this continues, I will probably not choose to proceed with a subscription despite the fact that i think LR mobile adds a lot of value and boosts my workflow significantly if it wasn't causing the program to lag so badly in the process.
I know this message was incredibly long and probably tedious to read through so thanks in advance to anyone who gets through it
-Jeff

Thanks for reporting. Just passed along your info to some of our devs. One of the things that needs to be created (beside smart previews) during an initial sync are thumbnails + previews for the LrM app - Guido
Hi Guido,
Thanks for pointing this out. I realized the same thing when I tried syncing a collection for offline mode and found out the required space sounded more like Previews + Smart Previews rather than just the Smart Previews.
greule wrote:
Hi Jeff, are your images particularly large or do you make a lot of changes which you save to the original file as part of your workflow?
The CPU usage is almost certainly from us uploading JPEG previews not the Smart Previews - particularly during develop edits as these force new JPEG previews to be sent from Lightroom desktop, but would not force new Smart Previews (unless the develop edits are modifying the original file making us think the Smart Preview is out of date) to be sent.
Guido
My images are full-resolution ~22mp Canon 5D Mark III RAW files so they're fairly large. Even if I only make one basic change such as exposure changes, I saw the issue. By "save to the original file" I'm assuming metadata changes such as timestamps, otherwise edits to the images aren't actually written to the original file. I'm only doing develop module edits so I shouldn't be touching the original file at all at this point in my workflow.
I think it makes sense now that you mention that new JPEG previews need to be generated and sent to the cloud due to updated develop edits. My concern is that this seems to be done in real-time as opposed to how Lightroom Desktop works (which is to render a new Standard Preview or 1:1 Preview on demand, which means only one is being rendered at any given time while viewing it in Loupe View or possibly 2 in Compare View). If I edit, for example, 10 images quickly in a row, once the sync kicks in a few seconds later, editing the 11th image is severely hindered due to the previous 10 images' JPEG previews being rendered and sync'd to the cloud (I'm assuming the upload portion doesn't take much CPU, but the JPEG render will utilize CPU resources to the fullest if it can). Rendering Standard/1:1 Previews locally and being able to walk away while the process finishes works because it is at the start of my workflow, but having to deal with on-the-fly preview rendering while I'm editing greatly impacts my ability to edit. Perhaps there can be a way to limit max CPU utilization for background sync tasks?
It may help to know that I'm running a dual-monitor setup, with Lightroom on a 27" 2560x1440 display maximized to fit the display (2nd display not running LR's 2nd monitor). Since I'm using a retina iPad, the optimal Standard Previews resolution should be the same at 2880 pixels.
Thanks again for the help!

Mobile sync "Server is shutting down"

Ever since the upgrade to Yosemite and Server 4.0, my mobile sync is not working properly. After three months, I have a backlog of accounts on multiple computers that aren't in sync; it is a nightmare.
During the upgrade, mobile sync stopped working, so during the rebuild of the Open Directory I made the change from afp to smb Home directory service; as long as I was rebuilding anyway, which seems to be required at every major upgrade. Everything set up fine, looked fine, the DNS is fine, but after a few weeks it clearly wasn't working. The consistent message for all File Sharing directories, including the home directory for mobile sync, is "Server shutting down; the file server "Kingkrool" is shutting down". Mobile sync then hangs, the Profiles aren't updated properly and it is a complete mess. In the console, it looks like a Kerberos error; the Open Directory was freshly rebuilt under Yosemite, the clients were re-bound, the certificates transferred.
It looks weird to me that it is looking for krbtgt at 0.1.2; The server is at 10.0.1.2. Where is it getting the truncated number and why?
1/25/15 10:50:25.277 AM opendirectoryd[54]: GSSAPI Error: Miscellaneous failure (see text (Server (krbtgt/[email protected]) unknown while looking up 'ldap/[email protected]' (cached result, timeout in 1166 sec) (negative cache))
1/25/15 10:50:25.422 AM opendirectoryd[54]: GSSAPI Error: Miscellaneous failure (see text (Server (krbtgt/[email protected]) unknown while looking up 'ldap/[email protected]' (cached result, timeout in 1166 sec) (negative cache))
1/25/15 10:50:25.617 AM com.apple.xpc.launchd[1]: (com.apple.imdmessageservices.IMDMessageServicesAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
1/25/15 10:50:25.617 AM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
1/25/15 10:50:25.810 AM mount_url[519]: TUAMHandler::SetUAMType setting UAMType to 1
1/25/15 10:50:25.958 AM mount_url[519]: ERROR: AFP_Mount - theEnumerator->Mount failed 2
1/25/15 10:50:25.961 AM automountd[518]: mount of /Network/Servers/kingkrool.reorg.private/Volumes/Klapaucius/NetworkUsers failed: No such file or directory
1/25/15 10:50:25.991 AM mount_url[522]: TUAMHandler::SetUAMType setting UAMType to 1
1/25/15 10:50:26.009 AM mount_url[522]: ERROR: AFP_Mount - theEnumerator->Mount failed 2
1/25/15 10:50:26.045 AM mount_url[523]: TUAMHandler::SetUAMType setting UAMType to 1
1/25/15 10:50:26.065 AM mount_url[523]: ERROR: AFP_Mount - theEnumerator->Mount failed 2

Hi Martin
Thank you for your answer. We only need to run reports using URLs (rwservlet).
After the installation, we find the problem that DISPLAY was not set. We solve it and run the demo reports ok. Then we restarted the server (shutdown and restart including AIX), everything restarted well but we were unable to run the reports again, with the messages I described before.
I did not see any post-installation procedure for reports and AIX, does this procedure exists? where can I find it?
Thank you for the help,
Jose

What are the storage limits for LR Mobile Sync?

I'm trying to find a definitive answer on whether there are limits to the amount of data that can be synced to Lightroom Mobile. I know my CC subscription gets me 20GB but I have also heard suggestions that LR Mobile sync data is outside of that.
I have a 128GB iPad, so it wouldn't be terribly hard for me to blow a 20GB limit.
Thanks,
Fraser

Fraser, Mobile only has lossy Smart Previews and camera roll files so you can have plenty of files on your iPad from Lightroom. They are outside the 20GB of CC AFAIK.

HT4137 i can't find my iPhone name when i right click to backup. but i see my backup folder in the mobile sync. how do i get that folder to go into itunes

i can't find my iPhone name when i right click to backup. but i see my backup folder in the mobile sync. how do i get that folder to go into itunes

"Where do I find my hundreds of dollars of downloads I have done since 2005?"
They will only be where you put them If you are doing the very basics, then they will be on your computer and they will be in your backup copy of your computer.
The itunes store is not global at all, never has been. You cannot redownload your content from another country. You can only use the countrys itunes store for the country that you are physically located.

Mobile synced to cloud but not iPad

I Can't figure out what's wrong. Since the update to Lightroom 5.5, my mobile sync has quit working. It was working perfectly fine before.
ive not changed catalogs.
ive done the delete all mobile data in Lightroom preferences. (Which at least allowed photos to sync to the cloud when it wasn't before that)
it deleted old collections from iPad that we're no longer synced.
now iPad says no collections available.
Ive reinstalled the app on the iPad mini.
nothing works.

Could you please try to re-sign-in to the Lr Mobile app. There was a misconfiguration at the back-end of your account. Should be fixed now.
Guido

Lightroom Mobile Sync Problems

Hi
My Lightroom Mobile syncing process is running very slow. I deleted the sync.lrdata file and started a new sync of approx 9500 images. Currently I have around 2100 images to sync, however the process has almost stopped. Any help or guidance would be appreciated.

Hi Trev,
Have you tried Syncing in Safe mode on the Mac? This would be to eliminate any processes that might be active in normal mode that might interfeer with the upload. Does you screen has a Retina Display? I have seen some topics where this might create a longer time for generating Smart previews to a smaller size
(iPad/iPhone screen size, compared to the Retina display)
Did you verify a Speedtest for your connection, just to make sure this is not influencing the sync behavior
This you can check for instance with Speedtest.net by Ookla - The Global Broadband Speed Test
There are some more topics on the forum where people experience problems using the Sync with a high amount of images in the Catalog.
- Re: Lightroom 5.4 to Lightroom Mobile sync is soooo slow - why no local sync?
- Lightroom Sync Issues
Hope this helps

What does Apple Mobile Sync do for me?

I frequently get a little thing popping up on my screen, saying Apple Mobile Sync wants access to my several e-mail account passwords.
I have never used and am not likely ever to use MobileMe. I do use an iPhone.
Does Apple Mobile Sync participate in keeping my iPhone and Mail accounts synced, such that I should be giving it access to those keychains? Or is it a MobileMe-only, otherwise-useless appendage?

HI,
From your Apple menu click System Preferences. If you see an icon like this: in the System Preferences pane, then you have a MobileMe account. If you choose not sync via MobileMe, click the MobileMe icon in the System Preferences pane. Select the Sync tab.
Deselect: Synchronize with MobileMe
If necessary, you can cancel the MobileMe account. Click here: http://www.apple.com/support/mobileme/
Click: Account and Billing / Cancel
Does Apple Mobile Sync participate in keeping my iPhone and Mail accounts synced, such that I should be giving it access to those keychains?
Only if you have a MobileMe account.
Carolyn

I keep getting Lightroom 64 bit has stopped woring on my computer. It was working fine till I signed in and turn mobile sync on in collections

Does anyone now what to do ?
-Soumya

If indeed LR Mobile sync is causing the problem, you can turn off the sync by opening another LR catalog and signing out of LR Mobile. Details:
1. Hold down the Alt key (I assume you're on Windows) and then click "Lightroom" from the Start menu or click its icon (however you normally start it). This should open the Select Catalog window.
2. Select another catalog and open it. If you don't have another catalog, create a new test one and open that.
3. Go to Edit > Preferences > Lightroom Mobile.
4. Click Sign In and sign in.
5. If you're asked to Change Sync Catalog, click Switch To Syncing This Catalog.
6. Go to Edit > Preferences > Lightroom Mobile.
7. Click Sign Out.
8. Do File > Open Recent to open your original catalog.
9. If you're asked again to Change Sync Catalog, click Don't Sync.
10. Go to Edit > Preferences > Lightroom Mobile.
11. Click Sign Out.

Mobile Sync Issue

When I go to sync a collection or multiple collections, if there is more then 100 photos LR5.4 crashes.
Report:
Process:
Adobe Photoshop Lightroom 5 [485]
Path:
/Applications/Adobe Photoshop Lightroom 5.app/Contents/MacOS/Adobe Photoshop Lightroom 5
Identifier:
com.adobe.Lightroom5
Version:
Adobe Photoshop Lightroom 5.4 [955652] (5.4)
Code Type:
X86-64 (Native)
Parent Process: launchd [153]
Responsible:
Adobe Photoshop Lightroom 5 [485]
User ID:
501
Date/Time:
2014-04-10 22:32:51.493 -0500
OS Version:
Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID: 686A0E9A-3C71-FFC4-ADC0-9374F6417AC9
Crashed Thread: 25 Worker Thread
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: 0x000000000000000a, 0x0000000120aef000
VM Regions Near 0x120aef000:
MALLOC_LARGE
000000011fc20000-000000011ffef000 [ 3900K] rw-/rwx SM=PRV
--> mapped file
000000011ffef000-0000000121c3a000 [ 28.3M] r--/rwx SM=COW /Users/USER/Pictures/*/*.CR2
CG shared images
00000001c0003000-00000001c000b000 [   32K] r--/r-- SM=SHM
Thread 0:: Dispatch queue: com.apple.main-thread
0   com.adobe.ag.kernel
0x000000010fbe5b27 0x10fbce000 + 97063
1   com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
2   com.adobe.ag.kernel
0x000000010fbd7fb1 lua_resume + 112
3   com.adobe.ag.kernel
0x000000010fbd1988 0x10fbce000 + 14728
4   com.adobe.ag.kernel
0x000000010fbd1798 0x10fbce000 + 14232
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
7   com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
8   com.adobe.ag.kernel
0x000000010fbd7fb1 lua_resume + 112
9   com.adobe.ag.kernel
0x000000010fbd1988 0x10fbce000 + 14728
10 com.adobe.ag.kernel
0x000000010fbd1798 0x10fbce000 + 14232
11 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
12 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
13 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
14 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
15 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
16 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
17 com.adobe.ag.substrate
0x000000010fd42c37 0x10fd31000 + 72759
18 com.apple.Foundation
0x00007fff83fae13e __NSThreadPerformPerform + 229
19 com.apple.CoreFoundation
0x00007fff848cb731 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17
20 com.apple.CoreFoundation
0x00007fff848bcea2 __CFRunLoopDoSources0 + 242
21 com.apple.CoreFoundation
0x00007fff848bc62f __CFRunLoopRun + 831
22 com.apple.CoreFoundation
0x00007fff848bc0b5 CFRunLoopRunSpecific + 309
23 com.apple.HIToolbox
0x00007fff8a43ca0d RunCurrentEventLoopInMode + 226
24 com.apple.HIToolbox
0x00007fff8a43c7b7 ReceiveNextEventCommon + 479
25 com.apple.HIToolbox
0x00007fff8a43c5bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
26 com.apple.AppKit
0x00007fff876bb3de _DPSNextEvent + 1434
27 com.apple.AppKit
0x00007fff876baa2b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
28 com.apple.AppKit
0x00007fff876aeb2c -[NSApplication run] + 553
29 com.apple.AppKit
0x00007fff87699913 NSApplicationMain + 940
30 com.adobe.Lightroom5
0x000000010fbb5613 main + 1107
31 com.adobe.Lightroom5
0x000000010fbb51b8 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib
0x00007fff8fe99662 kevent64 + 10
1   libdispatch.dylib
0x00007fff90e6743d _dispatch_mgr_invoke + 239
2   libdispatch.dylib
0x00007fff90e67152 _dispatch_mgr_thread + 52
Thread 2:
0   libsystem_kernel.dylib
0x00007fff8fe98e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib
0x00007fff83daef08 _pthread_wqthread + 330
2   libsystem_pthread.dylib
0x00007fff83db1fb9 start_wqthread + 13
Thread 3:: Worker Thread Dispatcher
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.kernel
0x000000010fbf45cc AgConditionLock_wait + 43
3   com.adobe.ag.kernel
0x000000010fbee1a7 AgTransitQueue_dequeueToLuaState + 92
4   com.adobe.ag.kernel
0x000000010fbef0a8 0x10fbce000 + 135336
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
7   com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
8   com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
9   com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
10 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
11 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
12 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
13 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
14 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
15 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
16 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
17 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
18 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
19 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
20 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 4:: ace
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.apple.CoreServices.CarbonCore
0x00007fff8e6eb800 TSWaitOnCondition + 108
3   com.apple.CoreServices.CarbonCore
0x00007fff8e6eb9ff TSWaitOnConditionTimedRelative + 172
4   com.apple.CoreServices.CarbonCore
0x00007fff8e6bc145 MPWaitOnQueue + 192
5   com.adobe.ag.AgImageIO
0x00000001148bb1a6 0x1146bd000 + 2089382
6   com.adobe.ag.AgImageIO
0x00000001148baed3 0x1146bd000 + 2088659
7   com.apple.CoreServices.CarbonCore
0x00007fff8e6bc6c3 PrivateMPEntryPoint + 58
8   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
9   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
10 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 5:: ace
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.apple.CoreServices.CarbonCore
0x00007fff8e6eb800 TSWaitOnCondition + 108
3   com.apple.CoreServices.CarbonCore
0x00007fff8e6eb9ff TSWaitOnConditionTimedRelative + 172
4   com.apple.CoreServices.CarbonCore
0x00007fff8e6bc145 MPWaitOnQueue + 192
5   com.adobe.ag.AgImageIO
0x00000001148bb1a6 0x1146bd000 + 2089382
6   com.adobe.ag.AgImageIO
0x00000001148baed3 0x1146bd000 + 2088659
7   com.apple.CoreServices.CarbonCore
0x00007fff8e6bc6c3 PrivateMPEntryPoint + 58
8   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
9   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
10 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 6:: ace
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.apple.CoreServices.CarbonCore
0x00007fff8e6eb800 TSWaitOnCondition + 108
3   com.apple.CoreServices.CarbonCore
0x00007fff8e6eb9ff TSWaitOnConditionTimedRelative + 172
4   com.apple.CoreServices.CarbonCore
0x00007fff8e6bc145 MPWaitOnQueue + 192
5   com.adobe.ag.AgImageIO
0x00000001148bb1a6 0x1146bd000 + 2089382
6   com.adobe.ag.AgImageIO
0x00000001148baed3 0x1146bd000 + 2088659
7   com.apple.CoreServices.CarbonCore
0x00007fff8e6bc6c3 PrivateMPEntryPoint + 58
8   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
9   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
10 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 7:: cr_scratch
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.AgImageIO
0x00000001147cb2b1 0x1146bd000 + 1106609
3   com.adobe.ag.AgImageIO
0x000000011498ab6b 0x1146bd000 + 2939755
4   com.adobe.ag.AgImageIO
0x00000001147951a1 0x1146bd000 + 885153
5   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
6   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
7   libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 8:: Queue Processor - AgPhotoAvailability
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.kernel
0x000000010fbf45cc AgConditionLock_wait + 43
3   com.adobe.ag.kernel
0x000000010fbee1a7 AgTransitQueue_dequeueToLuaState + 92
4   com.adobe.ag.kernel
0x000000010fbef0a8 0x10fbce000 + 135336
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
7   com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
8   com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
9   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
10 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
11 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
12 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
13 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
14 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
15 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
16 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
17 com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
18 com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
19 com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
21 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
22 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
23 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
24 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
25 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
26 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
27 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
28 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
29 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
30 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 9:: AsyncDataServer
0   libsystem_kernel.dylib
0x00007fff8fe999f2 read + 10
1   com.adobe.wichitafoundation
0x000000010fe2de57 0x10fd9b000 + 601687
2   com.adobe.wichitafoundation
0x000000010fe29900 0x10fd9b000 + 583936
3   com.adobe.wichitafoundation
0x000000010fddd0dd 0x10fd9b000 + 270557
4   com.adobe.wichitafoundation
0x000000010fdcd746 0x10fd9b000 + 206662
5   com.adobe.wichitafoundation
0x000000010fe12230 0x10fd9b000 + 487984
6   com.adobe.wichitafoundation
0x000000010fe121d9 0x10fd9b000 + 487897
7   com.adobe.wichitafoundation
0x000000010fe12063 0x10fd9b000 + 487523
8   com.adobe.wichitafoundation
0x000000010fe1281f 0x10fd9b000 + 489503
9   com.adobe.wichitafoundation
0x000000010fe18ab9 0x10fd9b000 + 514745
10 com.adobe.wichitafoundation
0x000000010fdcf851 0x10fd9b000 + 215121
11 com.adobe.wichitafoundation
0x000000010fdc7642 0x10fd9b000 + 181826
12 com.adobe.wichitafoundation
0x000000010fdc830c 0x10fd9b000 + 185100
13 com.adobe.wichitafoundation
0x000000010fdc8211 0x10fd9b000 + 184849
14 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
15 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
16 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
17 com.adobe.ag.kernel
0x000000010fbe52c8 0x10fbce000 + 94920
18 com.adobe.ag.kernel
0x000000010fbe65c2 0x10fbce000 + 99778
19 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
20 com.adobe.ag.kernel
0x000000010fbe52c8 0x10fbce000 + 94920
21 com.adobe.ag.kernel
0x000000010fbe65c2 0x10fbce000 + 99778
22 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
23 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
24 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
25 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
26 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
27 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
28 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
29 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
30 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
31 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
32 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
33 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
34 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
35 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
36 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
37 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
38 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
39 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
40 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
41 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
42 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
43 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
44 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
45 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
46 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
47 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
48 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
49 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
50 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
51 com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
52 com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
53 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
54 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
55 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
56 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
57 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
58 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
59 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
60 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
61 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
62 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
63 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 10:: Dispatch queue: AgWFCatalogIndexDefinitions.lua :: /Users/johnwatt/Library/Caches/Adobe/Lightroom/Sync Data/Sync.lrdata/6e60720763c00637a5cde2c
0   libsystem_kernel.dylib
0x00007fff8fe99f92 write + 10
1   com.adobe.wichitafoundation
0x000000010fe2b235 0x10fd9b000 + 590389
2   com.adobe.wichitafoundation
0x000000010fe299c2 0x10fd9b000 + 584130
3   com.adobe.wichitafoundation
0x000000010fddfd28 0x10fd9b000 + 281896
4   com.adobe.wichitafoundation
0x000000010fddf22f 0x10fd9b000 + 279087
5   com.adobe.wichitafoundation
0x000000010fdcdf65 0x10fd9b000 + 208741
6   com.adobe.wichitafoundation
0x000000010fdce52c 0x10fd9b000 + 210220
7   com.adobe.wichitafoundation
0x000000010fe20be9 0x10fd9b000 + 547817
8   com.adobe.wichitafoundation
0x000000010fe19945 0x10fd9b000 + 518469
9   com.adobe.wichitafoundation
0x000000010fdcf851 0x10fd9b000 + 215121
10 com.adobe.wichitafoundation
0x000000010fdc7642 0x10fd9b000 + 181826
11 com.adobe.wichitafoundation
0x000000010fdc830c 0x10fd9b000 + 185100
12 com.adobe.wichitafoundation
0x000000010fdc8211 0x10fd9b000 + 184849
13 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
14 com.adobe.ag.kernel
0x000000010fbe61a9 0x10fbce000 + 98729
15 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
16 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
17 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
18 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
19 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
20 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
21 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
22 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
23 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
24 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
25 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
26 com.adobe.wichitafoundation
0x000000010fda3e41 0x10fd9b000 + 36417
27 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
28 com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
29 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
30 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
31 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
32 com.adobe.wichitafoundation
0x000000010fda3cb1 0x10fd9b000 + 36017
33 com.adobe.wichitafoundation
0x000000010fda39f2 0x10fd9b000 + 35314
34 com.adobe.wichitafoundation
0x000000010fdacf4f 0x10fd9b000 + 73551
35 libdispatch.dylib
0x00007fff90e652ad _dispatch_client_callout + 8
36 libdispatch.dylib
0x00007fff90e6d443 _dispatch_after_timer_callback + 77
37 libdispatch.dylib
0x00007fff90e652ad _dispatch_client_callout + 8
38 libdispatch.dylib
0x00007fff90e678a1 _dispatch_source_invoke + 413
39 libdispatch.dylib
0x00007fff90e67633 _dispatch_queue_drain + 359
40 libdispatch.dylib
0x00007fff90e689dd _dispatch_queue_invoke + 110
41 libdispatch.dylib
0x00007fff90e66fa3 _dispatch_root_queue_drain + 75
42 libdispatch.dylib
0x00007fff90e68193 _dispatch_worker_thread2 + 40
43 libsystem_pthread.dylib
0x00007fff83daeef8 _pthread_wqthread + 314
44 libsystem_pthread.dylib
0x00007fff83db1fb9 start_wqthread + 13
Thread 11:
0   libsystem_kernel.dylib
0x00007fff8fe98e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib
0x00007fff83daef08 _pthread_wqthread + 330
2   libsystem_pthread.dylib
0x00007fff83db1fb9 start_wqthread + 13
Thread 12:
0   libsystem_kernel.dylib
0x00007fff8fe98e6a __workq_kernreturn + 10
1   libsystem_pthread.dylib
0x00007fff83daef08 _pthread_wqthread + 330
2   libsystem_pthread.dylib
0x00007fff83db1fb9 start_wqthread + 13
Thread 13:
0   libsystem_kernel.dylib
0x00007fff8fe94a1a mach_msg_trap + 10
1   libsystem_kernel.dylib
0x00007fff8fe93d18 mach_msg + 64
2   com.apple.CoreFoundation
0x00007fff848bd155 __CFRunLoopServiceMachPort + 181
3   com.apple.CoreFoundation
0x00007fff848bc779 __CFRunLoopRun + 1161
4   com.apple.CoreFoundation
0x00007fff848bc0b5 CFRunLoopRunSpecific + 309
5   com.apple.Foundation
0x00007fff83fb3adc -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 253
6   com.adobe.wichitafoundation
0x000000010fe2e3ea 0x10fd9b000 + 603114
7   com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
8   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
9   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
10 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 14:: com.apple.NSURLConnectionLoader
0   libsystem_kernel.dylib
0x00007fff8fe94a1a mach_msg_trap + 10
1   libsystem_kernel.dylib
0x00007fff8fe93d18 mach_msg + 64
2   com.apple.CoreFoundation
0x00007fff848bd155 __CFRunLoopServiceMachPort + 181
3   com.apple.CoreFoundation
0x00007fff848bc779 __CFRunLoopRun + 1161
4   com.apple.CoreFoundation
0x00007fff848bc0b5 CFRunLoopRunSpecific + 309
5   com.apple.Foundation
0x00007fff83fb1967 +[NSURLConnection(Loader) _resourceLoadLoop:] + 348
6   com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
7   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
8   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
9   libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 15:
0   libsystem_kernel.dylib
0x00007fff8fe94a1a mach_msg_trap + 10
1   libsystem_kernel.dylib
0x00007fff8fe93d18 mach_msg + 64
2   com.apple.CoreFoundation
0x00007fff848bd155 __CFRunLoopServiceMachPort + 181
3   com.apple.CoreFoundation
0x00007fff848bc779 __CFRunLoopRun + 1161
4   com.apple.CoreFoundation
0x00007fff848bc0b5 CFRunLoopRunSpecific + 309
5   com.apple.AppKit
0x00007fff8785b16e _NSEventThread + 144
6   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
7   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
8   libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 16:: Preview Server
0   libsystem_kernel.dylib
0x00007fff8fe99f92 write + 10
1   com.adobe.wichitafoundation
0x000000010fe2b235 0x10fd9b000 + 590389
2   com.adobe.wichitafoundation
0x000000010fe299c2 0x10fd9b000 + 584130
3   com.adobe.wichitafoundation
0x000000010fddf939 0x10fd9b000 + 280889
4   com.adobe.wichitafoundation
0x000000010fdce16f 0x10fd9b000 + 209263
5   com.adobe.wichitafoundation
0x000000010fdce52c 0x10fd9b000 + 210220
6   com.adobe.wichitafoundation
0x000000010fe20be9 0x10fd9b000 + 547817
7   com.adobe.wichitafoundation
0x000000010fe19945 0x10fd9b000 + 518469
8   com.adobe.wichitafoundation
0x000000010fdcf851 0x10fd9b000 + 215121
9   com.adobe.wichitafoundation
0x000000010fdd2b98 0x10fd9b000 + 228248
10 com.adobe.wichitafoundation
0x000000010fdc690b 0x10fd9b000 + 178443
11 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
12 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
13 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
14 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
15 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
16 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
17 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
18 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
19 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
20 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
21 com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
22 com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
23 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
24 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
25 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
26 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
27 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
28 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
29 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
30 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
31 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
32 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
33 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 17:: com.apple.CFSocket.private
0   libsystem_kernel.dylib
0x00007fff8fe989aa __select + 10
1   com.apple.CoreFoundation
0x00007fff84908b83 __CFSocketManager + 867
2   libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
3   libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
4   libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 18:: Queue Processor - PreviewFileStore
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.kernel
0x000000010fbf45cc AgConditionLock_wait + 43
3   com.adobe.ag.kernel
0x000000010fbee1a7 AgTransitQueue_dequeueToLuaState + 92
4   com.adobe.ag.kernel
0x000000010fbef0a8 0x10fbce000 + 135336
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
7   com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
8   com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
9   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
10 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
11 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
12 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
13 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
14 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
15 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
16 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
17 com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
18 com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
19 com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
21 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
22 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
23 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
24 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
25 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
26 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
27 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
28 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
29 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
30 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 19:: Queue Processor - NegativeQueue
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.kernel
0x000000010fbf45cc AgConditionLock_wait + 43
3   com.adobe.ag.kernel
0x000000010fbee1a7 AgTransitQueue_dequeueToLuaState + 92
4   com.adobe.ag.kernel
0x000000010fbef0a8 0x10fbce000 + 135336
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
7   com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
8   com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
9   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
10 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
11 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
12 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
13 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
14 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
15 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
16 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
17 com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
18 com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
19 com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
21 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
22 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
23 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
24 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
25 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
26 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
27 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
28 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
29 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
30 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 20:: Queue Processor - HistogramQueue
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.kernel
0x000000010fbf45cc AgConditionLock_wait + 43
3   com.adobe.ag.kernel
0x000000010fbee1a7 AgTransitQueue_dequeueToLuaState + 92
4   com.adobe.ag.kernel
0x000000010fbef0a8 0x10fbce000 + 135336
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
7   com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
8   com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
9   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
10 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
11 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
12 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
13 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
14 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
15 com.adobe.ag.kernel
0x000000010fbd2149 0x10fbce000 + 16713
16 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
17 com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
18 com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
19 com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
20 com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
21 com.adobe.ag.kernel
0x000000010fbe614f 0x10fbce000 + 98639
22 com.adobe.ag.kernel
0x000000010fbd7f12 0x10fbce000 + 40722
23 com.adobe.ag.kernel
0x000000010fbd759d 0x10fbce000 + 38301
24 com.adobe.ag.kernel
0x000000010fbd816a 0x10fbce000 + 41322
25 com.adobe.ag.kernel
0x000000010fbcffeb lua_pcall + 101
26 com.adobe.ag.substrate
0x000000010fd4361b 0x10fd31000 + 75291
27 com.apple.Foundation
0x00007fff83fb176b __NSThread__main__ + 1318
28 libsystem_pthread.dylib
0x00007fff83dad899 _pthread_body + 138
29 libsystem_pthread.dylib
0x00007fff83dad72a _pthread_start + 137
30 libsystem_pthread.dylib
0x00007fff83db1fc9 thread_start + 13
Thread 21:: Queue Processor - RenderQueue_Render
0   libsystem_kernel.dylib
0x00007fff8fe98716 __psynch_cvwait + 10
1   libsystem_pthread.dylib
0x00007fff83dafc3b _pthread_cond_wait + 727
2   com.adobe.ag.kernel
0x000000010fbf45cc AgConditionLock_wait + 43
3   com.adobe.ag.kernel
0x000000010fbee1a7 AgTransitQueue_dequeueToLuaState + 92
4   com.adobe.ag.kernel
0x000000010fbef0a8 0x10fbce000 + 135336
5   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
6   com.adobe.ag.kernel
0x000000010fbd7f01 0x10fbce000 + 40705
7   com.adobe.ag.kernel
0x000000010fbcff69 lua_call + 36
8   com.adobe.ag.substrate
0x000000010fd4f610 AgLua_callWithAutoReleasePool + 84
9   com.adobe.ag.kernel
0x000000010fbd7c3f 0x10fbce000 + 39999
10 com.adobe.ag.kernel
0x000000

Scott, you mention in your message 'the next time I logged in.' Did you explicitly sign out of Lightroom Mobile sync on the desktop after syncing the first time? Or were you forced to sign in again on launch. If it's the latter this should not be happening and could be another indication that the catalog you signed in with before is not the same (i.e. a backup or a copy that is not at the same state you were when you were last signed in). Is this catalog shared between two machines in any way?
If you are seeing this and you are definitely not in a backup catalog you should be able to do the following with Lightroom shut down. This will work better if you've already done Delete All Data though it isn't required. If you haven't, after relaunching Lr we will rebuild your sync status which can take a while depending on how much you have synced. I would not recommend doing this for any other situation...
On OSX: In Finder go to /Users/<username>/Library/Caches/Adobe/Lightroom/Sync Data/Sync.lrdata and delete it.
On Windows: In Explorer go to C:\Users\<username>\AppData\Local\Adobe\Lightroom\Caches\Sync Data\Sync.lrdata and delete it

Mobile sync not working for groups

Hello guys,
i've been playing with Mavericks Server and so far everything is working smoothly except for the mobility sync...
i successfully created a Local Network Account and was able to successfully sync it to the Server using AFP and a specific folder...
This is working awesome, but here comes the issue:
i setup another Local Network Account and assigned it to a Group and used Workgroup Manager (on the same server) to setup the mobility sync for the group...
Now, when i try to login, the mobile profile gets created on the computer but does not sync to the server, it syncs locally instead or i get the error "The sync could not complete because your network home at "(null)" does not allow writing...
if i try Profile Manager websiteit does not work either...
i know this works for a single user, but if i want to sync it using groups it fails....
I've tried finding a possible answer and so far nothing...
Im using OS X Server 3.1.2 and Workgroup Manager 10.9 (421)
Can you please help me out?
Thanks in advance...

Anyone?

What is mobile sync backup?

What does Library/Application Support/Mobile Sync/Backup do for me? Mine takes over 8Gb and has files dating back to 2011. Is it safe to delete these? I have no idea why I need them.
Any help appreciated as I try and slim down my MBP.
James

These backups are from your mobile devices.
You can delete those backups to free up storage space.
But make sure that you sync your mobile devices soon after deleting those backups to create a new backup for your devices.
http://support.apple.com/kb/HT4946?viewlocale=en_US&locale=en_US

Update 9.1.0.79 Mobile Sync and Yahoo Go Sync error when sync iphone 3G

Every time I synce I get the two errors - Mobile Sync and Yahoo go Sync stop working. iPhone has 3.1.3 version. Also, backup takes longer. Please advise.

notice how under diagnostics readout it shows "most recent device not currently connected"
mine does same thing and i have iphone connected when i do it.
my problems also started with this update and i show 4 errors in event viewer which is under adminastrative tools in control panel.
MY problem is super slow backups for a 16gb 3Gs with 12gbs free. a backup used to be done in like 30-45 seconds now takes about 5 minutes and looks as if it stals at a few points when looking at bar at top of itunes.
my iphone shows up in itunes and shows all pages etc. i do everything manually although i do sync apps.
everytime i connect iphone and open itunes i get 4 errors thats show up only in event viewer (but anyone who maintains computers should be aware of all tools available to them to see whats going on in the background) that show up for "BONJOUR" i have posted this here and under bonjour forum. i turned off bonjour services the proper way again thrru adminastrative tools>services double click bonjour and change for "automatic to "disabled". don't do it through msconfig as some would tell you to do if it's a bonjour issue.
but checking out event viewer can give you valuable info so you don't do the apple nonsense wasting hours to clean up their messy installation only to have it do exact same thing again. it's obvoius they have a conflict.... now we can only hope for a resolution ie UPDATE if enough complain by sending them all this.
i don't have a jailbreak phone nor am i rebuilding anything i'll live with it till they fix it as my event viewer log isn't getting filled up with bonjour errors anymore nor do i need all this bloated crap apple sends our way... i do have quicktime pro.

Mobile Sync stopped working...a fix I think!

Hi folks. My head has many briuses from banning it on the desk but I may have a fix that will restore some of the calendar probs we have had with update 9.1.79
I have a Ph.D (poke and hope diploma) in computing, but I made this work.
I have got my calendar to re-sync and lost the message of "Mobile Sync has stopped working" by doing the following.
I called support and they gave me a link to remove ALL contents that i-tunes installs and there are many including Bonjour etc..
http://support.apple.com/kb/HT1925
Do exactrly as it says and remove everything. I had to restert my PC in safe mode (press F8 at start up) to get at a couple of files that needed the administrators permission to delete.
I then restarted and had to delete the file itunes library.itl (I actually dragged it to my desk top from the directory C:/my name/Music/itunes
This was because I installed the earlier version of itunes (9.0.1) and it could not read this file so i removed it.
I then downloaded itunes version 9.0.1 and installed it.
Started up itunes and did a sync and it worked!!!
I hope this works for some one else. If so, go into settings and dissable Get automatic updates until Uncle Mac fixes the bug!!
Good luck,
J.

jedison wrote:
I recommend (and have tested) a slightly different solution then the one proposed here (and in numerous other threads) for the iTunes 9.1 "sync no longer works" for calendar, bookmarks and contacts.
There are several threads which recommend different solutions:
1) Downgrading to iTunes 9.0 --> fine, but I want to keep up-to-date with recent iTunes versions, and I do not want to have to find an old iTunes library to get iTunes running nor create a new library from scratch.
2) Extracting the "Mobile Device Support" (MDS) from iTunes 9.0 installation, uninstalling MDS (installed with iTunes 9.1) and installating MDS from iTunes 9.0. --> iTunes 9.1 will not accept this and refuses to use this version of MDS
3) Changing the System Environment variable PATH --> this did not solve the sync problem for me (error messages stop occurring, but sync does not start working).
4) Copying all DLLs from Apple Application Support (under Common Files) to Mobile Device Support --> this made things much worse for me with tons of error messages.
5) Deleting (renaming) DLLs from System32 (however it is called on your version of Windows) and putting in place new ones --> risky; I don't like unnecessarily changing DLLs under Windows.
My solution (no promises that this will work on all versions of Windows, but ti worked for me) is to get the "correct" version of the DLLs which are causing the sync to fail.
I will not post those here as they are referenced in several other threads (e.g. http://discussions.info.apple.com/thread.jspa?threadID=2394471), but there is a link below.
* Here is where my recommendation differs from others. *
Do not update the DLLs under Windows System32 -- update the bad versions installed under Apple Mobile Device Support (on WinXP default location is: C:\Program Files\Common Files\Apple\Mobile Device Support).
1) I suggest renaming the bad (non-working DLLs) so that you can rollback in case of problems, e.g.:
ssleay32.dllcould_bebad
libeay32.dllcould_bebad
2) Save the DLLs which are at the depositfiles link (http://depositfiles.com/files/92eig2pii) into your Apple MDS directory.
WHY?
In this way, you have not potentially corrupted other programs which make use of these DLLs (the versions under Windows system32), you have only corrected the versions used by Apple Mobile Device Support.
(And it is easy to undo this change if it does not work for you.)
Good luck!
I've tried a number of other solutions, and two previous ones (running diagnostics and copying the depositfiles DLLs to system32) worked for a one-time sync only. When I tried to resync following a successful sync, the calendar failed to update changes made on either side.
This solution (dropping the depositfiles DLLs to the common folder:
C:\Program Files\Common Files\Apple\Mobile Device Support
worked with repeat attempts.
(I too think that this getting ridiculous for Apple to say nothing about this problem. I mean, it's not like we're complaining about some hardly-used feature, or an uncommon application: it's Outlook calendar sync!)

LR Mobile syncing

Similar Messages

Maybe you are looking for