Aperture 3 not usable - Constantly "processing"
I need some SERIOUS help PLEASE!!!! I have been using Aperture 2 and loved it. Seen the new Aperture 3 and thought hey great upgrades so I bought the upgrade version and installed. Everything seemed ok until I uploaded some images into a project. When I am in the project it freezes my computer (gets stuck on an image and says processing...can't do anything in this stage) and I have to force quit. I have tried everything....restarting, checking for software updates, googling it, leaving it stand for a bit and nothing has helped. I even uninstalled (moved to trash) and tried reinstalling. However I think I did something wrong as when I reinstalled all my original albums were in there still so it must not have uninstalled??? I am trying to edit some pictures and promised my client they would be done this weekend. I have been in many tears over this. Very frustrated. Any help would be appreciated HUGELY!!!
Problems for those who used Aperture 2.0 (like me) seem to be:
-- Problems in the AP2 database, which didn't bother AP2 but which prevent conversion to AP3. AP3's database appears to be very, very different and you will have to allow about 5 seconds per image for conversion. (My 10k images took about 3 hours.)
-- Inadequate disk space during the conversion process. There is a lot of reading and writing going on, you will need lots of free space. (I used an external drive with twice as much free space as the size of my Library.) After everything was back where I wanted it, I found that a "Quick" defrag, using iDefrag worked wonders for import and export speed. (Long sequential reads.)
-- Problem images, the following have been noted: Big TIFF, images with lots of spot and patch, some images with retouch.
-- Residual AP2 data and settings in the RAW default files, preference files, and cache files. Purging these files generally results in a huge speed increase, once they are rebuilt for AP3. (Appzapper might help cleaning all traces of AP2 from your machine.)
Finally a certain generation of iMacs with an NVIDIA graphics card seem to be simply broken for Aperture 3. This won't get fixed until Apple fixes it.
As always, make sure you have a safety copy of EVERYTHING before you do anything. This has been a most un-Apple like experience, but AP3 is a very nice upgrade and can really fly on a 4 GB machine; in my case, my Mini runs AP3 faster than my MacPro ever ran AP2.
Good luck!
Similar Messages
-
My son's ipad mini has become not usable because it asks for constantly asks for iCloud password. It says that it is not the correct password and the screen reappears. I know the password is correct because I can login to the website via another PC.
Part of the issue is that it appears not be connected to the network. It appears to be trying to then gets interuptted by the iCloud password request.
I tried to restore from iTunes when connected to PC, however, it says it cannot do this because Find My Phone has been activated on the ipad. To deactiviate I need to turn it off on the ipad which required my iCloud password (seems I am in a catch 22).
Any suggestions on how to proceed?
Thanks.Hopefully this will me get you back up.
http://support.apple.com/kb/HT1212 -
Hi, I've just downloaded Aperture 3.2 and transfered all my iPhoto Library but now when I use the Aperture program it runs at the slowest speed possible and is almost impossible to work with. It is constantly processing why is this?
You can click on the text that says 'processing' in the main windows and it will open (toggle) the Activity Window, (can also be accessed via the Window menu -> Show Activity.
It will tell you what Aperture is doing with more precision and perhaps even how many photos it still needs to process. It is generally best to wait until all that processing is done before you start working with the photos (well it is best to first turn of options what you dont want to use, perhaps Faces or Previews and then let it process the new photos). -
Aperture not building thumbnails
Having a problem right now with generating thumbnails in Aperture 3.5.1. Originally had another issue with iMovie seeing very few movies in my Aperture library. I was able to import all files from all cameras into iMovie, and can see them if I import a sampling of them into another library. Apple support suggested I rebuild my library, which revealed a few more, but still less than 5% of the total.
Apple then suggested I create a new library and import my existing library. I was watching the progress bar near the end when Aperture crashed at completion. I repaired the library and it began building thumbnails. The process has been slow, with Aperture running at 100% CPU (one core--single thread?) and very low I/O on the disk.
The status freezes on one image when Aperture processes roughly 1000 thumbnails. It says "Generating Thumbnails for [image]" "35,323 Remaining". At first I thought Aperture may still be processing in the background, seeing how Aperture's CPU utilization remained in the 100% range and disk usage continued. But when I quit Aperture and restart, it shows barely more progress than what was indicated in the status before quitting Aperture. The particular images listed are fine, and the thumbnails are generated when Aperture is launched.
At this point, Aperture will not quit cleanly, or with a Force Quit. Occasionally I've been able to use this suggestion:
https://discussions.apple.com/docs/DOC-3881
In other cases, Aperture seems to quit, but the entry remains in the Activity Monitor, with all accumulated stats, but 0% CPU. I'm unable to launch Aperture at this time and must restart. If I try to kill the process, the OS says it can't find it. Could this be a Mavericks eccentricity?
When restarting the OS and Aperture, thumbnail generation continues from where it left off, and processes another 1000 images or so. I did try repairing the database, and thumbnail generation continued, but eventually failed.
Occasionally, the com.apple.MediaLibraryService stops resonding in the Event Viewer. This had not always correlated with the frozen progress bar. In fact, thumbnails have continued to process when I've seen that hang in Event Viewer. But it always has meant I need to take Aperture down forcefully. Oddly, I do not have sharing previews enabled (set to never for now).
There are a few early articles, but they don't seem to offer any suggestions I have not tried, except to persist and restart Aperture each time this happens. Could take 2-3 weeks at this rate if I need to restart every time the progress bar stops. I have also tried clearing user and system cache a few times.
Apple second level support has been slow to respond, and I'm over 9 days into this process. Has anyone experienced anything similar, or can offer any suggestions?Is it only your current Aperture library, that is causing this trouble?
Or do you see the same problem, when working with a new test library?
Although otherwise operationally sound, some video in my original library was not viewable in the Media Browser (including iMovie), even after a repair and rebuild.
I created a new, empty library and imported my original library. I described that process. Aside from the crash near the end, it appears to have all my assets. The project and image counts are the same.
The issues described about building thumbnails is in this new library. Upon importing my original library, the new library began generating all new thumbnails.
If the thumbnail generation is only hanging for your current Aperture library, you may have imported corrupted media - image files, videos that cannot be processed, sound files.
I know exactly what you're talking about, and this was my first assumption as well. As an Aperture 3 early adopter, I saw this issue countless times from failed imports. But I have examined over 8 files that it has apparently hung on. The thumbnails are fine! I look at the assets, directly, and they are in perfect condition. I expected to find corrupted TIFF files or bad thumbnails. Neither were true. If I request to generate it again, it works just fine.
Have you tried to remove the images from your Apeture library, that are shown in the message? Inspect them in the Finder and check the media type - jpeg, raw, video and check, if other Applications can open it.
Yes.
I do not have previews generated for nearly 2/3 of the images in my library, although I haven't seen reports about how this could be a problem.
UPDATE
Since my first post, I found a suggestion to regenerate all new thumbnails. Days of time lost, but I restarted. Still had a crash after about 1000 thumbnails. com.apple.qtserver or something was hung. Seemed only to launch occasionally after I restarted. Thought this might be responsible for generating thumbnails for video. So I did a search for all video files and let Aperture build these as I browsed through, page by page.
Since that time, Aperture has been building thumbnails for 10 hours, the longest run yet. Thumbnails are still generating VERY slowly, but I haven't seen a crash since.
Could it be the back and forth between images and video as it's generating thumbnails? -
Aperture not syncing with iPhone, iLife, iTunes, etc
The problem: Aperture isn't syncing. I thought this was an iPhone problem, but apparently, it's a system wide thing. Let me explain:
I'm running Aperture 3.2, but I've had this problem for a while now - probably since upgrading to Lion.
In Aperture, I have a smart album that contains any photo I've rated five stars. Currently, there are 180 photos in it. In iTunes, I've selected to sync certain things from Aperture to my iPhone. If I click on that 5 Star smart album, it only shows that there are 21 photos. Huh? So, as a test, I opened iPhoto (which I never use). In the File menu, I clicked "Show Aperture Library" and I selected my 5 Star smart album. Sure enough, iPhoto only sees 21 photos in there. But if I click over to Aperture, I see that smart album contains 180 images.
What's going on here?
I should also note that a search of the forums here at Apple support show lots of people have been having similar problems, but most only notice they're missing photos when they sync their iPhone. Clearly, the problem is deeper than that. Aperture sees 180 photos in my 5 Star smart album. iTunes, iPhoto and my iPhone are only able to sync 21 of them?
And how weird is this? In Aperture, I have a smart album of shots that were taken with my iPhone and rated 3 stars or higher. There are 115 shots in that smart album. iTunes and iPhoto only see 38.
Somewhere, for whatever reason, Aperture is telling the rest of the system that it has far fewer images than it does. How do I figure out where the problem is and how do I fix it?Thanks to Jalpuna
Your workaround worked for me to until I started to use Aperture to adjust photos in several projects in Aperture. After that, Photos were missing again on my iOS devices etc., and I couldn't imagine the process on making new previews for all my 25.000 photos once again. My old MBP is just too slow.
I had to see if I could find a workaround to work with only the adjusted photos which looked as the ones missing after syncing to the iOS devices (or at least just the project in which the adjusted photos are).
This example works for me for the time being:
Usually a project (let's call it "XYZ") with newly imported photos have the same number of photos in Aperture and in the event with the same name XYZ on an iOS device.
If not all photos sync between Aperture and iOS (usually after adjusting photos in Aperture), I use this process, which I found out to use after adjusting several photos:
When I adjust a photo I let Aperture automatically make the adjustments in a new version and let the versions stay in a stack.
I make sure to change the rating for all the other photos in the stack to x (9) (i.e. except the version I want on my iOS devices - yes only one and the same versions goes to all the iOS devices, I sync via iTunes).
After rating be sure to use the pick function on the version you want on your device (the version rated higher than x (9) - which means that the wanted version "goes to the top of the stack".
Now view "unrated or better" (which means your x (9) rated photos won't show)
The process from here seems to work also if by any other reason photos won't show up on the iOS device.
Choose a project, all the photos in a project or just the photos missing in iOS, and delete the previews
Then generate thumbnails - this could take some time and for sure it takes time. At least if you need to do it with thousands of photos.
Close Aperture when all the new thumbnails and previews are generated.
Open iTunes and sync your iOS device. I think it works best (fastest) with the cable, but I think it should work via WiFi-sync too.
It is **** of a workaround, but it is the only way I can get all the right photos on my iOS devices after adjusting photos in Aperture.
The next coming up must be how to manage to sync back to Aperture the photos adjusted in iPhoto on the iOs devices:-)
Note: Any adjustments made to a version seems not to be deleted when deleting previews, but is kept and put back on a new generated preview. -
I would like to change my Visa card from the account but its not changing and the billing information is not changing and I can't purchase any thing from my account its now not usable please help me to solve the problem
You made a purchase and exhausted the credit on your card before it processed. All purchases are final. Contact iTunes Store support. You need to settle up before you can purchase or download anything else.
-
Aperture has started random "processing"
I have been idle in the Aperture community for a while, but I have not found the answer to this problem in my searches.
My Aperture (Still 3.2.2) is processing a large number (2000) of images. It's just "Processing". There is no explanation of what it is doing or why it started. My wife started Aperture the other day and said "The computer's running slow". She does not know of any stray keystroke or menu option she chose.
Now, I have this "Processing" paused. While it was paused, I plugged an iPhone into my Mac. Instead of presenting me with an "Import from iPhone" window, Aperture started a secong "processing" activity! Now I have two "Processing" activities, without any indication of what or why!
I tried plugging in a different iPhone. It's fishy -- I did not get the"Import" window. However, Aperture did not start a third "Processing" activity.
The selection of photos that are being processed have no rhyme or reason to me. They are from different cameras, different years, different projects! Some are managed, some are referenced.
Does anyone have a clue what might have started this and what exactly Aperture is processing?
nathanHi Kirby,
Have you tried letting it process overnight?
I don't doubt that the Processing activity will finish if I let it -- I'm just afraid of what it is doing! If I didn't ask Aperture to do any heavyweight processing on my photos with Places, is it doing something that I don't want it to? Is it messing something up?
And is there a reason you've not updated to 3.2.3?
I usually watch the scuttlebutt about problems with upgrades for a little while before I perform the upgrade. This time, my personal life got put on hold while I work crazy hours at work. Once I get a chance to think about things and make sure my library is sufficiently backed up, I will upgrade. I know Apple makes things easy, but I always take a good chunk of time to make sure my system is in a good state to perform an upgrade that is as important as Aperture.
nathan
(And yes, I sign "nathan" instead of "Nathan" just because I've been doing that for decades, since I was in college. ) -
When will Aperture 3 support RAW processing for the Canon 5D III?
When will Aperture 3 support RAW processing for the new Canon 5D III?
We are no phophets and also do not work for Apple - so we don't know.
See this thread to join into a discussion with others who also are waiting:
Canon 5D Mk III - RAW update?
Regards
Léonie -
Aperture not showing (just black) newly imported JPEG files
RE: Aperture not showing newly imported JPEG files.
In fact its just black instead of the actual image. (see attached screen shot)
When double clicking on this - i.e. to go to the edit mode, the image then appears.
If I return to the viewing screen without changing anything to that image it remains black.
If I make any kind of change to the image, the image will appear when returning to the viewing screen.
Aperture seems only to have started behaving like this after update to OS X 10.10 (Yosemite)
I have the latest Aperture 3.6
Latest Digital Camera Raw 6.00 Build 761.5 and Digital Camera Raw Support 6000 Build 131.1
RAW files (taken with same camera) are displayed without any issues.
JPEG image files have been taken with a Sony RX100
JPEG image files taken with the same device imported into Aperture before OSX update to 10.10 have appear to have no issues
I cannot say if JPEG files taken with a different device have similar issues.
All files have been been reprocessed to latest edition of aperture
I have had other issues of other types of files (i.e. TIFF output files 'unsupported image format' behaving oddly including inconsistent behaviour after having been processed by 3rd party aperture plug-in's - although this has now largely been solved.
I remember having similar issues of files behaving strangely in Aperture after last update to OS X (Mavericks) - forget how this was solved - but I'm pretty sure it was not an issue involving JPEGS
Many thanks...this sounds very similar to the problem I had on a previous aperture update and I had a similar issue - to that - with the .tiff files output from RAW files and an HDR plug-in.
In the first instance, I cannot remember for sure, but maybe it was something to do with not having the latest RAW File update for Aperture specific to that latest Aperture Update and specific to a Sony RX100 (or it could have been a Nikon d700).
I found the RAW file update - I'm not sure it was being made available from the App Store - and everything was fine.
With the more recent issue, I'm pretty sure this was resolved by updating to the latest Photomatix HDR plug-in.
So I'm just stuck on the issue with the JPEGs now. -
Lightroom 5 Spot Removal Tool Lags and is not usable (Temp Workaround?)
Lightroom 5 Spot Removal Tool Lags and is not usable. The Spot Removal Tool really is pretty essential to the usability and workflow of Lightroom 5. Checking the other tools alongside the Spot Removal Tool, it appears that the Red Eye Correction Tool is also affected. Might it have something to do with the Process Version? I noticed when working with some older image files (using the 2010 Process Version), the Spot Removal Tool worked as previously experienced. Current images that have been "upgraded" to the New Process Version (2012) are now incapable of utilizing the Spot Removal Tool due to its very laggy and sporadic response. I've never experienced an issue like this with Lightroom (LR user since LR2). Mac OSX 10.7.5, 3.4GHz i7, 8GB 1333MHz DDR3
I've also noticed that reprocessing an image can revert the Spot Removal Tool to "useful" again (reverting from 2012 to 2010, then back to 2012). Doesn't always work and doesn't always "stick", as closing and reopenling LR usually reinitiates the laggy Spot Removal Tool.
I haven't seen anyone mention the Process Version as a potential culprit, nor have I seen any reliable workarounds. Reprocessing an image (or set of images) at least works for me for a while, though it would sure be nice to not have continue reprocessing images every time I open/use Lightroom 5.
LR5 is great and is all I need for the majority of my images. Unfortunately for me, though, that usability also necessitates the Spot Removal Tool's unhindered functionality.For some reason, it's clear that not everyone is experiencing such a massive slowdown / bottleneck when it comes to the Spot Removal Tool. If all users experienced this issue to this degree, they would have been clamoring for Adobe to address and rectify it immediately.
With all due respect, Sean, to make a suggestion like that proves you do not experience / have not experienced this issue / don't understand the severity to which this issue can affect workflow; simply "turning off noise reduction and lens correction" is definitely not a fix. If 16GB of RAM doesn't fix the issue, do you really think simply turning off noise reduction will? And as Bert Nase points out, to do that to large volumes of images increases workflow in a program designed to streamline workflow for large volumes of images.
1- One option is to change the process version in your first photo (2003/2010), then copy-paste that develop setting to the rest of your images. This will get all of your images to the point in your workflow where you can use the Spot Removal Tool on each image. Once spot removal is done, reconvert each image back to the current process version (2012) then re-accomplish the spots that reconverting lost.
2- Configuring presets is one work-around option, though you will need at least couple of them tailored to your workflow.
3- Changing your import settings to an earlier Process Version is an option, then accomplishing Spot Removal on each photo, then updating the Process Version on one and copy/paste to the rest, then re-accomplishing for each photo the spots lost in the conversion and continuing your workflow from there.
Readers of this thread can use the link above, but it can introduce its own issues, too. As noted, switching back-and-forth between Process Versions can delete some of your already-corrected spots and you'll have to re-correct them. Worse, a window prompt asking to create a virtual copy or proof will occasionally begin popping up.. closing the window, clicking "cancel", or choosing any other option in that pop-up window won't be "remembered" and the window pops back up with any further "click" on the image. Lightroom has to be shut down and the computer restarted for the issue to reset.
Yes, it's very frustrating and time consuming to say the least. So, unfortunately there is no fix, still only work-arounds. Hopefully this issue will be addressed and remedied in either the coming release of 5.2 (doubtful) or the Cloud version of Photoshop + Lightroom. -
Hardwired LAN slow on 10.10.1 - not usable
Immediately upon upgrading to 10.10.1 I noticed my Hardwired LAN (cat5e) performance took a huge performance hit, so much it's not usable.
I've not seen reports of this, and under 10.10 base I had no problems with LAN speed.
I have multiple Aperture Libraries, these are "big" in size 30GB to close to 300GB.
I have a 6TB NAS (WD MyCloud EX2) and a 2TB via USB on the Airport Extreme. Both used to work no problem but now so slow
What took 3-4 hours to copy a 250GB file is now days....not acceptable, I even started the copy overnight and next morning still chugging away, pictures show what I mean
When I take that exact same 2TB drive, un-plug it from the Airport Extreme and directly plug it to the iMac it transfers files as expected, 3-4 hours for 250GB file.
snapshots shows the transfer speed progression from initial start to a few minute after
Help me ..
I can't use my NAS like this, and it worked perfect on 10.9.xAs more data points I took a single 2.1GB file (a iDVD file) and both uploaded it to the EX2 NAS and downloaded it from the EX2 NAS
Some image to share:
Upload from iMac to EX2 NAS
Download from EX2 NAS to iMac is quite fast
Device activity screen for that single 2.1GB upload/download file
Later I will duplicate the 5GB Aperture file to see the network performance graph for that, though I will probably have to cancel it because once it goes to hours gfor a 5GB file that kills using the iMac for other purposes -
Activity monitor is not showing any processes - why?
Hi there,
I have a new MBP which seems to get really hot for no reason. The CPU temperature is at 68-70°C constantly and I only have mail and firefox running. I opened the activity monitor to see what is taking so much effort and it is not showing me anything. Not a single process is listed. What am I doing wrong?
Thanks for your help!
ClaudiaHas this been the case since you bought the computer
or did it once work? Is the computer quite new?
Have you made any changes to the original installed
software such as updates, installation of
third-party software, etc.?
The computer is brand new (bought it in December) and I don't think it ever worked.
Here are two things you might try:
A. Boot into safe mode. Does Activity Monitor work?
Tried it, didn't work.
B. Create a new temporary user account. Log into
that account. Does Activity Monitor work?
Did that. The activity monitor wouldn't work in the test account either.
On the off chance your copy of Activity Monitor is
corrupted you can replace it with a fresh one as
follows:
Restoring Lost OS X
Files
If you erase or otherwise "lose" an OS X system
application or utility (such as Mail or Disk Utility,
for example) you can restore them without having to
reinstall OS X.
Download the shareware utility Pacifist.
Read the documentation. Use Pacifist to extract a
fresh copy of the missing application from the file
archives on your OS X Installer disc. The file
archives are usually found on the installer disc in
the /System/Installations/ folder.
After restoring the application you need to reinstall
the OS X Combo Updater for the version of OS X you
currently have installed. This assures the new copy
of the application is updated to the current
version.
Lastly, it's a good idea to repair permissions.
Well, I downloaded Pacifist and replaced activity monitor and that finally did it. Thank you so much for that suggestion. I spend nearly two hours on the phone with Apple support this morning and they gave up on it. The only useful thing they could contribute is that the problem was probably created when I migrated everything from my PB to the new MBP. Anyways, problem solved. Thank you thank you thank you!
Best wishes,
Claudia
MacBook Pro 2.33 GHz Mac OS X (10.4.8) -
I setup an ACER VM6620G (Win7x86) how I wanted, including disabling the administrator account and creating an administrator user "PVA"
Navigated to \\wds\DeploymentShare$\Scripts and ran the litetouch script. Chose my "Sysprep and Capture" task.
Everything went off without a hitch until I restarted the technician pc.
I got the dreaded
"Windows could not parse or process unattend answer file [C:\windows\Panther\unattend.xml] for pass [specialize]. A component or setting specified in the answer file does not exist"
I tried to deploy the captured image to the same computer and got the same error
I've scoured the internet for solutions (Shift+10 opens command prompt. Good to know!) with no luck.
I've saved the unattend.xml and looked for errors- going as far as to install an x86 Win7 virtual machine to validate the unattend.xml file in WISM
Other information that might be useful:
I never used WISM to create an unattend.xml nor did I attach one to the image.
I didn't try to copy user profiles/settings/migrate etc
I imported the captured image to WDT. Created a standard task and added 2 nodes
-Inject Drivers
-Install Application
As a side, I've got another image that I've already injected the drivers/installed the application as a test. Everything went smoothly.
+-----------------+
| Unattend.xml:
+-----------------+
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ImageInstall>
<OSImage>
<WillShowUI>OnError</WillShowUI>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>2</PartitionID>
</InstallTo>
<InstallFrom>
<Path>\\10.0.0.1\deploymentshare$\Operating Systems\ACER Win7 x86 Capture\ACER Win7 x86 Capture.wim</Path>
<MetaData>
<Key>/IMAGE/INDEX</Key>
<Value>1</Value>
</MetaData>
</InstallFrom>
</OSImage>
</ImageInstall>
<Display>
<ColorDepth>16</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<ComplianceCheck>
<DisplayReport>OnError</DisplayReport>
</ComplianceCheck>
<UserData>
<AcceptEula>true</AcceptEula>
</UserData>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="generalize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<Identification>
<JoinWorkgroup>WORKGROUP</JoinWorkgroup>
</Identification>
</component>
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<ComputerName>PVA-PC</ComputerName>
<RegisteredOrganization>PVA</RegisteredOrganization>
<RegisteredOwner>PVA</RegisteredOwner>
<TimeZone>"Eastern Standard Time"</TimeZone>
<DoNotCleanTaskBar>true</DoNotCleanTaskBar>
</component>
<component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Home_Page>about:blank</Home_Page>
<IEWelcomeMsg>false</IEWelcomeMsg>
</component>
<component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<RunSynchronous>
<RunSynchronousCommand wcm:action="add">
<Description>EnableAdmin</Description>
<Order>1</Order>
<Path>cmd /c net user Administrator /active:yes</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>UnfilterAdministratorToken</Description>
<Order>2</Order>
<Path>cmd /c reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System /v FilterAdministratorToken /t REG_DWORD /d 0 /f</Path>
</RunSynchronousCommand>
<RunSynchronousCommand wcm:action="add">
<Description>disable user account page</Description>
<Order>3</Order>
<Path>reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\OOBE /v UnattendCreatedUser /t REG_DWORD /d 1 /f</Path>
</RunSynchronousCommand>
</RunSynchronous>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
<component name="Microsoft-Windows-TapiSetup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<TapiConfigured>0</TapiConfigured>
<TapiUnattendLocation>
<AreaCode>""</AreaCode>
<CountryOrRegion>1</CountryOrRegion>
<LongDistanceAccess>9</LongDistanceAccess>
<OutsideAccess>9</OutsideAccess>
<PulseOrToneDialing>1</PulseOrToneDialing>
<DisableCallWaiting>""</DisableCallWaiting>
<InternationalCarrierCode>""</InternationalCarrierCode>
<LongDistanceCarrierCode>""</LongDistanceCarrierCode>
<Name>Default</Name>
</TapiUnattendLocation>
</component>
<component name="Microsoft-Windows-SystemRestore-Main" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DisableSR>1</DisableSR>
</component>
</settings>
<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State">
<UserAccounts>
<AdministratorPassword>
<Value></Value>
<PlainText>true</PlainText>
</AdministratorPassword>
</UserAccounts>
<AutoLogon>
<Enabled>true</Enabled>
<Username>Administrator</Username>
<Domain>.</Domain>
<Password>
<Value></Value>
<PlainText>true</PlainText>
</Password>
<LogonCount>999</LogonCount>
</AutoLogon>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1024</HorizontalResolution>
<RefreshRate>60</RefreshRate>
<VerticalResolution>768</VerticalResolution>
</Display>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>wscript.exe %SystemDrive%\LTIBootstrap.vbs</CommandLine>
<Description>Lite Touch new OS</Description>
<Order>1</Order>
</SynchronousCommand>
</FirstLogonCommands>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Work</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
</OOBE>
<RegisteredOrganization>PVA</RegisteredOrganization>
<RegisteredOwner>PVA</RegisteredOwner>
<TimeZone>"Eastern Standard Time"</TimeZone>
</component>
<component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<InputLocale>en-US</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
</settings>
<settings pass="offlineServicing">
<component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DriverPaths>
<PathAndCredentials wcm:keyValue="1" wcm:action="add">
<Path>\Drivers</Path>
</PathAndCredentials>
</DriverPaths>
</component>
</settings>
</unattend>https://skydrive.live.com/redir?resid=55C3109D61329D02!108&authkey=!AG793wDwQuFZa1s
Here's the end of the log file:
2013-03-27 17:39:05, Info CMI CBS_Core_Finalize:Calling cbs core finalize complete
2013-03-27 17:39:05, Info CMI Callback_CMI_ConfigInstall: CBS startup processing re-run complete.
2013-03-27 17:39:05, Info [0x030023] CMI Callback_CMI_ConfigInstall: Exit.
2013-03-27 17:39:05, Info [setup.exe] UnattendSearchExplicitPath: Found unattend file at [C:\windows\Panther\unattend.xml]; examining for applicability.
2013-03-27 17:39:05, Info [setup.exe] UnattendSearchExplicitPath: Found usable unattend file for pass [specialize] at [C:\windows\Panther\unattend.xml].
2013-03-27 17:39:06, Info IBS Callback_Unattend_InitEngine:Using unattend file found at [C:\windows\Panther\unattend.xml].
2013-03-27 17:39:06, Info [setup.exe] ValidateSMIPass: serialized settings stream; status 0x00000000
2013-03-27 17:39:06, Info [setup.exe] ValidateSMIPass: construct settings context; status 0x00000000
2013-03-27 17:39:06, Error [setup.exe] SMI data results dump: Source = Name: Microsoft-Windows-IE-InternetExplorer, Language: neutral, ProcessorArchitecture: x86, PublicKeyToken: 31bf3856ad364e35, VersionScope: nonSxS, /settings/IEWelcomeMsg
2013-03-27 17:39:06, Error [setup.exe] SMI data results dump: Description = Setting is not defined in this component.
2013-03-27 17:39:06, Info [setup.exe] ValidateSMIPass: load SMI settings; status 0x00000001
2013-03-27 17:39:06, Error [0x060432] IBS The provided unattend file is not valid; hrResult = 0x80220001
2013-03-27 17:39:06, Error [0x060565] IBS Callback_Unattend_InitEngine:The provided unattend file [C:\windows\Panther\unattend.xml] is not a valid unattended Setup answer file; hr = 0x1, hrSearched = 0x1, hrDeserialized = 0x0, hrImplicitCtx = 0x0, hrValidated = 0x1, hrResult = 0x80220001
2013-03-27 17:39:06, Info IBS UnattendErrorFromResults: Hit an unattend error; dumping any info we have about the failure...
2013-03-27 17:39:06, Info IBS UnattendDumpSetting: ------Unattend setting error / warning------
2013-03-27 17:39:06, Info IBS UnattendDumpSetting: Error code = 0x80220001
2013-03-27 17:39:06, Info IBS UnattendDumpSetting: Pass = specialize
2013-03-27 17:39:06, Info IBS UnattendDumpSetting: --------------------------------------------
2013-03-27 17:39:06, Info IBS UnattendErrorFromResults: Error text = Windows could not parse or process unattend answer file [C:\windows\Panther\unattend.xml] for pass [specialize]. A component or setting specified in the answer file does not exist.
2013-03-27 17:39:06, Error [0x0600c2] IBS Callback_Unattend_InitEngine:An error occurred while finding/loading the unattend file; hr = 0x1, hrResult = 0x80220001[gle=0x00000490]
2013-03-27 17:39:06, Info IBSLIB PublishCriticalError: Publishing blocked message [Windows could not parse or process unattend answer file [C:\windows\Panther\unattend.xml] for pass [specialize]. A component or setting specified in the answer file does not exist.]
2013-03-27 17:39:06, Info This installation is blocked from completing due to compliance failures or invalid input; this is not an internal error.
Also, here's my customsettings.ini as I think it changes the unattend?
[Settings]
Priority=Default
Properties=MyCustomProperty
[Default]
SkipDomainMembership=YES
DomainAdmin=Administrator
DomainAdminDomain=go.local
DomainAdminPassword=************
SkipTimeZone=YES
TimeZone="035"
TimeZoneName="Eastern Standard Time"
SkipLocaleSelection=YES
KeyboardLocale=en-US
UserLocale=en-US
UILanguage=en-US
Bootstrap.ini:
[Settings]
Priority=Default
[Default]
DeployRoot=\\10.0.0.1\DeploymentShare$
UserID=Administrator
UserDomain=go.local
UserPassword=***********
KeyboardLocale=en-US
SkipAdminPassword=YES
SkipProductKey=YES
SkipBitLocker=YES -
Repairing Library causes Aperture NOT RESPONDING
Upon the recent "update" from Apple concerning Aperture 3.4:
I installed the update on 9/20.
When I open my massive 1.16 TB Aperture library, I get this message:
Click Repair.
Then this message:
Then this message:
Since then, Aperture has been repairing my massive 1.16 TB library for ~ 5 hours until it gets to 77% and then "Aperture Not Responding".
I have to Force Quit.
Open Aperture again and then this message:
Click Restore Windows
Then this message:
Click Repair.
Then this message:
Then, the cycle begins again until it gets to 77% in about ~5 hours
Then "Aperture Not Responding".
I have to Force Quit.
And so on.
So, I deleted Aperture from hard drive
Re-Install Aperture 3.0 from cd/dvd
Open Aperture...with BRAND new library. Fine. Except it is not MY library.
Close Aperture.
Open Massive Aperture Library
Get this message:
Select Quit
Close Aperture
Update Aperture to 3.4
Open Aperture with massive library
This message: Aperture has detecteed inconsistincies in your library. Please click Repair to avoid any potential problems.
Click Repair
Then, the cycle begins again until it gets to 77% in about ~5 hours
Then "Aperture Not Responding".
I have to Force Quit.
Of course I send the Report to Apple. Every time.
And so on and on and on and on. For THREE DAYS already.
My Mac Pro has been a brick and unusable since it is hogging the cpu with this Aperture update.
Check back to the Apple Discussion Forums
Get this message:
We'll be back soon. We are busy updateing Apple Support Communities for you and will be back shortly.
Yeah.
Repeat all the steps above for 2-3 times per day for 3 days.
Tanja <><
That's my story and I'm sticking to it!Here is my crash log:
Date/Time: 2012-09-23 11:56:08 -0500
OS Version: 10.7.5 (Build 11G56)
Architecture: x86_64
Report Version: 9
Command: Aperture
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Version: 3.4 (3.4)
Build Version: 1
Project Name: Aperture
Source Version: 301036000000000
Parent: launchd [134]
PID: 1925
Event: hang
Duration: 1.81s
Steps: 19 (100ms sampling interval)
Pageins: 0
Pageouts: 0
Process: Aperture [1925]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Architecture: x86_64
UID: 501
Thread 0x3d6f7 DispatchQueue 438
User stack:
19 ??? (in Aperture) [0x107efa314]
19 ??? (in Aperture) [0x107efa9c2]
19 NSProApplicationMain + 387 (in ProKit) [0x109408be1]
19 -[NSApplication run] + 470 (in AppKit) [0x7fff915509b9]
19 ??? (in Aperture) [0x10835f00d]
19 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 135 (in AppKit) [0x7fff9155407d]
19 _DPSNextEvent + 1247 (in AppKit) [0x7fff915549c5]
19 AEProcessAppleEvent + 102 (in HIToolbox) [0x7fff95208b69]
19 aeProcessAppleEvent + 250 (in AE) [0x7fff8c9939f7]
19 _ZL25dispatchEventAndSendReplyPK6AEDescPS_ + 38 (in AE) [0x7fff8c993b03]
19 aeDispatchAppleEvent(AEDesc const*, AEDesc*, unsigned int, unsigned char*) + 200 (in AE) [0x7fff8c993c25]
19 _NSAppleEventManagerGenericHandler + 105 (in Foundation) [0x7fff9286f5dc]
19 -[NSAppleEventManager dispatchRawAppleEvent:withRawReply:handlerRefCon:] + 283 (in Foundation) [0x7fff9286f74e]
19 __-[NSAppleEventManager setEventHandler:andSelector:forEventClass:andEventID:]_block_invoke_1 + 101 (in Foundation) [0x7fff928707c7]
19 -[NSObject performSelector:withObject:withObject:] + 65 (in CoreFoundation) [0x7fff8d326541]
19 -[NSApplication(NSAppleEventHandling) _handleCoreEvent:withReplyEvent:] + 307 (in AppKit) [0x7fff915575a2]
19 -[NSApplication(NSAppleEventHandling) _handleAEOpenDocumentsForURLs:] + 325 (in AppKit) [0x7fff91796bac]
19 -[NSApplication _sendFinishLaunchingNotification] + 78 (in AppKit) [0x7fff91558b91]
19 -[NSApplication _postDidFinishNotification] + 212 (in AppKit) [0x7fff91558e2b]
19 -[NSNotificationCenter postNotificationName:object:userInfo:] + 65 (in Foundation) [0x7fff92839fc3]
19 _CFXNotificationPost + 2634 (in CoreFoundation) [0x7fff8d2dc7ba]
19 __-[NSNotificationCenter addObserver:selector:name:object:]_block_invoke_1 + 47 (in Foundation) [0x7fff9284dd0e]
19 ??? (in Aperture) [0x107f4686c]
19 ??? (in Aperture) [0x107f45ae8]
19 -[RKDatabaseComponent openDatabaseForLibraryPath:options:] + 367 (in RedRock) [0x1088ec868]
19 -[RKDatabase openDatabaseWithOptions:] + 8421 (in RedRock) [0x1088efa7a]
19 +[RKRecoverMgr repairDatabaseOnThisThread:] + 76 (in RedRock) [0x108a7c8d0]
19 -[RKRecoverMgr repairDatabaseOnThisThread] + 1479 (in RedRock) [0x108a7cf31]
19 -[RKRecoverMgr rebuildVersions] + 2436 (in RedRock) [0x108a6b968]
19 -[RKRecoverMgr repairVersions] + 120 (in RedRock) [0x108a734b1]
19 -[RKRecoverMgr ensureAllManagedFilesHaveMasters] + 4003 (in RedRock) [0x108a7033b]
19 +[HgModel modelsFromDatabase:where:] + 195 (in iLifeSQLAccess) [0x10a1f9660]
19 -[HgEntity modelsFromQuery:] + 617 (in iLifeSQLAccess) [0x10a2248fa]
19 -[HgEntity _dispatch_sync_if_needed_suspend:withBlock:] + 226 (in iLifeSQLAccess) [0x10a222f69]
19 _dispatch_barrier_sync_f_slow + 226 (in libdispatch.dylib) [0x7fff93915fd3]
19 __55-[HgEntity _dispatch_sync_if_needed_suspend:withBlock:]_block_invoke_0 + 19 (in iLifeSQLAccess) [0x10a222faf]
19 __28-[HgEntity modelsFromQuery:]_block_invoke_0 + 165 (in iLifeSQLAccess) [0x10a224b08]
19 -[HgEntity loadModelsFromResultSet:limit:] + 124 (in iLifeSQLAccess) [0x10a1f4f12]
19 -[HgKResultSet next] + 262 (in iLifeSQLAccess) [0x10a1f0e0b]
19 sqlite3_step + 2420 (in iLifeSQLAccess) [0x10a1c8bea]
17 sqlite3VdbeExec + 34145 (in iLifeSQLAccess) [0x10a1d1445]
17 sqlite3VdbeCursorMoveto + 43 (in iLifeSQLAccess) [0x10a1e2805]
11 sqlite3BtreeMovetoUnpacked + 698 (in iLifeSQLAccess) [0x10a1f151a]
11 moveToChild + 68 (in iLifeSQLAccess) [0x10a1e2763]
11 getAndInitPage + 66 (in iLifeSQLAccess) [0x10a1e2351]
11 btreeGetPage + 30 (in iLifeSQLAccess) [0x10a1d496b]
11 sqlite3PagerAcquire + 111 (in iLifeSQLAccess) [0x10a1d4a18]
11 sqlite3PcacheFetch + 193 (in iLifeSQLAccess) [0x10a1d4c0d]
9 pcache1Fetch + 46 (in iLifeSQLAccess) [0x10a1d4f38]
9 __psynch_mutexwait + 10 (in libsystem_kernel.dylib) [0x7fff9518cbf2]
2 pcache1Fetch + 798 (in iLifeSQLAccess) [0x10a1d5228]
2 __psynch_mutexdrop + 10 (in libsystem_kernel.dylib) [0x7fff9518cbde]
6 sqlite3BtreeMovetoUnpacked + 122 (in iLifeSQLAccess) [0x10a1f12da]
6 moveToRoot + 102 (in iLifeSQLAccess) [0x10a1e21b9]
6 sqlite3PagerUnref + 20 (in iLifeSQLAccess) [0x10a1e4edb]
4 __psynch_mutexdrop + 10 (in libsystem_kernel.dylib) [0x7fff9518cbde]
2 pcache1Unpin + 37 (in iLifeSQLAccess) [0x10a1e4f9f]
2 __psynch_mutexwait + 10 (in libsystem_kernel.dylib) [0x7fff9518cbf2]
1 sqlite3VdbeExec + 32076 (in iLifeSQLAccess) [0x10a1d0c30]
1 sqlite3VdbeExec + 26640 (in iLifeSQLAccess) [0x10a1cf6f4]
1 sqlite3VdbeMemRelease + 13 (in iLifeSQLAccess) [0x10a1e2ce1]
Kernel stack:
15 hndl_unix_scall64 + 19 (in mach_kernel) [0xffffff80002daea3]
14 unix_syscall64 + 507 (in mach_kernel) [0xffffff80005ce4cb]
8 psynch_mutexwait + 1404 (in mach_kernel) [0xffffff80005a3f5c]
8 ksyn_block_thread_locked + 90 (in mach_kernel) [0xffffff800059dfda]
4 thread_block_reason + 275 (in mach_kernel) [0xffffff800022f413]
4 thread_go + 608 (in mach_kernel) [0xffffff800022e060]
4 processor_idle + 149 (in mach_kernel) [0xffffff800022d375]
4 machine_idle + 289 (in mach_kernel) [0xffffff80002c6461]
4 thread_block_reason + 299 (in mach_kernel) [0xffffff800022f42b]
4 thread_continue + 1435 (in mach_kernel) [0xffffff800022f0cb]
4 ml_set_interrupts_enabled + 23 (in mach_kernel) [0xffffff80002be337]
4 psynch_mutexdrop + 91 (in mach_kernel) [0xffffff80005a39cb]
2 psynch_mutexdrop_internal + 837 (in mach_kernel) [0xffffff800059f015]
2 wait_queue_wakeup_one + 293 (in mach_kernel) [0xffffff80002402d5]
2 ml_set_interrupts_enabled + 23 (in mach_kernel) [0xffffff80002be337]
1 psynch_mutexdrop_internal + 151 (in mach_kernel) [0xffffff800059ed67]
1 lck_mtx_lock + 10 (in mach_kernel) [0xffffff80002b51da]
1 psynch_mutexdrop_internal + 1992 (in mach_kernel) [0xffffff800059f498]
1 lck_mtx_unlock + 169 (in mach_kernel) [0xffffff80002b5869]
1 psynch_mutexwait + 284 (in mach_kernel) [0xffffff80005a3afc]
1 ksyn_wqfind + 1422 (in mach_kernel) [0xffffff800059fa9e]
1 lck_mtx_unlock + 169 (in mach_kernel) [0xffffff80002b5869]
1 psynch_mutexdrop + 69 (in mach_kernel) [0xffffff80005a39b5]
1 ksyn_wqfind + 90 (in mach_kernel) [0xffffff800059f56a]
1 current_thread + 0 (in mach_kernel) [0xffffff80002be1c0]
1 unix_syscall64 + 236 (in mach_kernel) [0xffffff80005ce3bc]
2 hndl_allintrs + 290 (in mach_kernel) [0xffffff80002da712]
2 interrupt + 192 (in mach_kernel) [0xffffff80002c48d0]
2 lapic_interrupt + 121 (in mach_kernel) [0xffffff80002c9ab9]
2 cpu_signal_handler + 172 (in mach_kernel) [0xffffff80002cb9ac]
2 sync_iss_to_iks + 118 (in mach_kernel) [0xffffff80002c3c76]
2 call_continuation + 23 (in mach_kernel) [0xffffff8000820057]
2 psynch_mtxcontinue + 345 (in mach_kernel) [0xffffff800059ec79]
1 ksyn_wqrelease + 43 (in mach_kernel) [0xffffff800059e67b]
1 lck_mtx_lock + 44 (in mach_kernel) [0xffffff80002b51fc]
1 ksyn_wqrelease + 672 (in mach_kernel) [0xffffff800059e8f0]
1 zfree + 1134 (in mach_kernel) [0xffffff80002435ee]
1 lck_mtx_unlock + 169 (in mach_kernel) [0xffffff80002b5869]
Thread 0x3d711 DispatchQueue 2
User stack:
19 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff93914316]
19 kevent + 10 (in libsystem_kernel.dylib) [0x7fff9518d7e6]
Kernel stack:
18 kqueue_scan + 416 (in mach_kernel) [0xffffff800053b4d0]
1 hndl_unix_scall64 + 19 (in mach_kernel) [0xffffff80002daea3]
1 unix_syscall64 + 507 (in mach_kernel) [0xffffff80005ce4cb]
1 kevent + 54 (in mach_kernel) [0xffffff800053cbe6]
1 kevent_description + 1528 (in mach_kernel) [0xffffff800053cac8]
1 kqueue_scan + 208 (in mach_kernel) [0xffffff800053b400]
1 thread_block_reason + 275 (in mach_kernel) [0xffffff800022f413]
1 thread_go + 608 (in mach_kernel) [0xffffff800022e060]
1 processor_idle + 149 (in mach_kernel) [0xffffff800022d375]
1 machine_idle + 289 (in mach_kernel) [0xffffff80002c6461]
Thread 0x480eb DispatchQueue 630
User stack:
19 start_wqthread + 13 (in libsystem_c.dylib) [0x7fff8c5b3b85]
19 _pthread_wqthread + 316 (in libsystem_c.dylib) [0x7fff8c5b23da]
19 _dispatch_worker_thread2 + 198 (in libdispatch.dylib) [0x7fff93914928]
19 _dispatch_queue_invoke + 54 (in libdispatch.dylib) [0x7fff9391512e]
19 _dispatch_queue_drain + 264 (in libdispatch.dylib) [0x7fff939152d2]
19 _dispatch_call_block_and_release + 18 (in libdispatch.dylib) [0x7fff93913a82]
19 __46-[HgEntity _dispatch_async_suspend:withBlock:]_block_invoke_0 + 19 (in iLifeSQLAccess) [0x10a223151]
19 __35-[HgEntity executeUpdate:withArgs:]_block_invoke_0 + 36 (in iLifeSQLAccess) [0x10a221a20]
19 -[HgKPreparedSql updateWithArgs:] + 230 (in iLifeSQLAccess) [0x10a1e8d29]
19 sqlite3_step + 2420 (in iLifeSQLAccess) [0x10a1c8bea]
19 sqlite3VdbeExec + 34145 (in iLifeSQLAccess) [0x10a1d1445]
19 sqlite3VdbeCursorMoveto + 43 (in iLifeSQLAccess) [0x10a1e2805]
10 sqlite3BtreeMovetoUnpacked + 698 (in iLifeSQLAccess) [0x10a1f151a]
10 moveToChild + 68 (in iLifeSQLAccess) [0x10a1e2763]
10 getAndInitPage + 66 (in iLifeSQLAccess) [0x10a1e2351]
10 btreeGetPage + 30 (in iLifeSQLAccess) [0x10a1d496b]
10 sqlite3PagerAcquire + 111 (in iLifeSQLAccess) [0x10a1d4a18]
10 sqlite3PcacheFetch + 193 (in iLifeSQLAccess) [0x10a1d4c0d]
9 pcache1Fetch + 46 (in iLifeSQLAccess) [0x10a1d4f38]
9 __psynch_mutexwait + 10 (in libsystem_kernel.dylib) [0x7fff9518cbf2]
1 pcache1Fetch + 798 (in iLifeSQLAccess) [0x10a1d5228]
1 __psynch_mutexdrop + 10 (in libsystem_kernel.dylib) [0x7fff9518cbde]
9 sqlite3BtreeMovetoUnpacked + 122 (in iLifeSQLAccess) [0x10a1f12da]
9 moveToRoot + 102 (in iLifeSQLAccess) [0x10a1e21b9]
9 sqlite3PagerUnref + 20 (in iLifeSQLAccess) [0x10a1e4edb]
6 pcache1Unpin + 37 (in iLifeSQLAccess) [0x10a1e4f9f]
6 __psynch_mutexwait + 10 (in libsystem_kernel.dylib) [0x7fff9518cbf2]
2 __psynch_mutexdrop + 10 (in libsystem_kernel.dylib) [0x7fff9518cbde]
1 pthread_mutex_unlock + 280 (in libsystem_c.dylib) [0x7fff8c5af6b7]
Kernel stack:
18 hndl_unix_scall64 + 19 (in mach_kernel) [0xffffff80002daea3]
18 unix_syscall64 + 507 (in mach_kernel) [0xffffff80005ce4cb]
13 psynch_mutexwait + 1404 (in mach_kernel) [0xffffff80005a3f5c]
11 ksyn_block_thread_locked + 90 (in mach_kernel) [0xffffff800059dfda]
9 thread_block_reason + 275 (in mach_kernel) [0xffffff800022f413]
7 thread_go + 597 (in mach_kernel) [0xffffff800022e055]
7 ml_set_interrupts_enabled + 23 (in mach_kernel) [0xffffff80002be337]
2 thread_go + 608 (in mach_kernel) [0xffffff800022e060]
2 processor_idle + 149 (in mach_kernel) [0xffffff800022d375]
2 machine_idle + 289 (in mach_kernel) [0xffffff80002c6461]
2 thread_block_reason + 299 (in mach_kernel) [0xffffff800022f42b]
2 thread_continue + 1435 (in mach_kernel) [0xffffff800022f0cb]
1 ml_set_interrupts_enabled + 43 (in mach_kernel) [0xffffff80002be34b]
1 ml_set_interrupts_enabled + 23 (in mach_kernel) [0xffffff80002be337]
2 ksyn_block_thread_locked + 50 (in mach_kernel) [0xffffff800059dfb2]
2 assert_wait_deadline + 460 (in mach_kernel) [0xffffff800022fb0c]
2 ml_set_interrupts_enabled + 23 (in mach_kernel) [0xffffff80002be337]
3 psynch_mutexdrop + 91 (in mach_kernel) [0xffffff80005a39cb]
2 psynch_mutexdrop_internal + 837 (in mach_kernel) [0xffffff800059f015]
2 wait_queue_wakeup_one + 293 (in mach_kernel) [0xffffff80002402d5]
2 ml_set_interrupts_enabled + 23 (in mach_kernel) [0xffffff80002be337]
1 psynch_mutexdrop_internal + 1992 (in mach_kernel) [0xffffff800059f498]
1 lck_mtx_unlock + 71 (in mach_kernel) [0xffffff80002b5807]
2 psynch_mutexwait + 284 (in mach_kernel) [0xffffff80005a3afc]
2 ksyn_wqfind + 1367 (in mach_kernel) [0xffffff800059fa67]
1 lck_mtx_lock + 44 (in mach_kernel) [0xffffff80002b51fc]
1 lck_mtx_lock + 453 (in mach_kernel) [0xffffff80002b5395]
1 _rtc_nanotime_read + 24 (in mach_kernel) [0xffffff80002beb48]
1 hndl_allintrs + 290 (in mach_kernel) [0xffffff80002da712]
1 interrupt + 192 (in mach_kernel) [0xffffff80002c48d0]
1 lapic_interrupt + 121 (in mach_kernel) [0xffffff80002c9ab9]
1 cpu_signal_handler + 172 (in mach_kernel) [0xffffff80002cb9ac]
1 sync_iss_to_iks + 118 (in mach_kernel) [0xffffff80002c3c76]
Thread 0x3d71a
User stack:
19 thread_start + 13 (in libsystem_c.dylib) [0x7fff8c5b3b75]
19 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8c5b08bf]
19 __NSThread__main__ + 1575 (in Foundation) [0x7fff928916a2]
19 -[NSThread main] + 68 (in Foundation) [0x7fff9289172a]
19 -[XTThread run:] + 329 (in ProXTCore) [0x10a0d5282]
19 -[XTMsgQueue waitForMessage] + 47 (in ProXTCore) [0x10a0d603a]
19 -[NSConditionLock lockWhenCondition:beforeDate:] + 251 (in Foundation) [0x7fff9288a22e]
19 -[NSCondition waitUntilDate:] + 371 (in Foundation) [0x7fff928c0a5c]
19 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x7fff9518cbca]
Kernel stack:
19 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059e920]
Thread 0x3d71b
User stack:
19 thread_start + 13 (in libsystem_c.dylib) [0x7fff8c5b3b75]
19 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8c5b08bf]
19 __NSThread__main__ + 1575 (in Foundation) [0x7fff928916a2]
19 -[NSThread main] + 68 (in Foundation) [0x7fff9289172a]
19 -[XTThread run:] + 329 (in ProXTCore) [0x10a0d5282]
19 -[XTMsgQueue waitForMessage] + 47 (in ProXTCore) [0x10a0d603a]
19 -[NSConditionLock lockWhenCondition:beforeDate:] + 251 (in Foundation) [0x7fff9288a22e]
19 -[NSCondition waitUntilDate:] + 371 (in Foundation) [0x7fff928c0a5c]
19 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x7fff9518cbca]
Kernel stack:
19 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059e920]
Thread 0x3d71c
User stack:
19 thread_start + 13 (in libsystem_c.dylib) [0x7fff8c5b3b75]
19 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8c5b08bf]
19 __NSThread__main__ + 1575 (in Foundation) [0x7fff928916a2]
19 -[NSThread main] + 68 (in Foundation) [0x7fff9289172a]
19 -[XTThread run:] + 329 (in ProXTCore) [0x10a0d5282]
19 -[XTMsgQueue waitForMessage] + 47 (in ProXTCore) [0x10a0d603a]
19 -[NSConditionLock lockWhenCondition:beforeDate:] + 251 (in Foundation) [0x7fff9288a22e]
19 -[NSCondition waitUntilDate:] + 371 (in Foundation) [0x7fff928c0a5c]
19 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x7fff9518cbca]
Kernel stack:
19 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059e920]
Thread 0x3d71d
User stack:
19 thread_start + 13 (in libsystem_c.dylib) [0x7fff8c5b3b75]
19 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8c5b08bf]
19 __NSThread__main__ + 1575 (in Foundation) [0x7fff928916a2]
19 -[NSThread main] + 68 (in Foundation) [0x7fff9289172a]
19 -[XTThread run:] + 329 (in ProXTCore) [0x10a0d5282]
19 -[XTMsgQueue waitForMessage] + 47 (in ProXTCore) [0x10a0d603a]
19 -[NSConditionLock lockWhenCondition:beforeDate:] + 251 (in Foundation) [0x7fff9288a22e]
19 -[NSCondition waitUntilDate:] + 371 (in Foundation) [0x7fff928c0a5c]
19 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x7fff9518cbca]
Kernel stack:
19 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059e920]
Thread 0x3d71e
User stack:
19 thread_start + 13 (in libsystem_c.dylib) [0x7fff8c5b3b75]
19 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8c5b08bf]
19 __NSThread__main__ + 1575 (in Foundation) [0x7fff928916a2]
19 -[NSThread main] + 68 (in Foundation) [0x7fff9289172a]
19 -[XTThread run:] + 329 (in ProXTCore) [0x10a0d5282]
19 -[XTMsgQueue waitForMessage] + 47 (in ProXTCore) [0x10a0d603a]
19 -[NSConditionLock lockWhenCondition:beforeDate:] + 251 (in Foundation) [0x7fff9288a22e]
19 -[NSCondition waitUntilDate:] + 371 (in Foundation) [0x7fff928c0a5c]
19 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x7fff9518cbca]
Kernel stack:
19 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059e920]
Thread 0x3d71f
User stack:
19 thread_start + 13 (in libsystem_c.dylib) [0x7fff8c5b3b75]
19 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8c5b08bf]
19 __NSThread__main__ + 1575 (in Foundation) [0x7fff928916a2]
19 -[NSThread main] + 68 (in Foundation) [0x7fff9289172a]
19 -[XTThread run:] + 329 (in ProXTCore) [0x10a0d5282]
19 -[XTMsgQueue waitForMessage] + 47 (in ProXTCore) [0x10a0d603a]
19 -[NSConditionLock lockWhenCondition:beforeDate:] + 251 (in Foundation) [0x7fff9288a22e]
19 -[NSCondition waitUntilDate:] + 371 (in Foundation) [0x7fff928c0a5c]
19 __psynch_cvwait + 10 (in libsystem_kernel.dylib) [0x7fff9518cbca]
Kernel stack:
19 psynch_cvcontinue + 0 (in mach_kernel) [0xffffff800059e920]
Thread 0x3e0b7
User stack:
19 thread_start + 13 (in libsystem_c.dylib) [0x7fff8c5b3b75]
19 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8c5b08bf]
19 __NSThread__main__ + 1575 (in Foundation) [0x7fff928916a2]
19 -[NSThread main] + 68 (in Foundation) [0x7fff9289172a]
16 -[NSUIHeartBeat _heartBeatThread:] + 1727 (in AppKit) [0x7fff9178911b]
16 usleep + 53 (in libsystem_c.dylib) [0x7fff8c566bb5]
16 __semwait_signal + 10 (in libsystem_kernel.dylib) [0x7fff9518ce42]
2 -[NSUIHeartBeat _heartBeatThread:] + 1311 (in AppKit) [0x7fff91788f7b]
2 -[NSProProgressIndicator heartBeat:] + 1791 (in ProKit) [0x109439244]
2 -[NSProProgressIndicator drawRect:] + 116 (in ProKit) [0x10943976d]
1 -[NSProgressIndicator drawRect:] + 1710 (in AppKit) [0x7fff91787133]
1 -[NSProProgressIndicator _drawThemeProgressArea:] + 386 (in ProKit) [0x10943a31c]
1 -[NSProProgressIndicator progressBarFillFacet] + 62 (in ProKit) [0x109438869]
1 +[NSProThemeFacet facetWithElement:part:fromTheme:] + 32 (in ProKit) [0x109517fdf]
1 +[NSProThemeFacet facetWithElement:part:dimension1:dimension2:fromTheme:] + 163 (in ProKit) [0x109517fb0]
1 +[NSProThemeFacet _facetWithKeyList:andRenditionKeyClass:orRenditionKey:fromTheme:] + 296 (in ProKit) [0x109517ba6]
1 calloc + 48 (in libsystem_c.dylib) [0x7fff8c60315d]
1 malloc_zone_calloc + 81 (in libsystem_c.dylib) [0x7fff8c602346]
1 szone_malloc_should_clear + 1115 (in libsystem_c.dylib) [0x7fff8c5cd00e]
1 tiny_malloc_from_free_list + 1073 (in libsystem_c.dylib) [0x7fff8c5cc72c]
1 -[NSProgressIndicator drawRect:] + 1693 (in AppKit) [0x7fff91787122]
1 -[NSProProgressIndicator _drawThemeBackground] + 97 (in ProKit) [0x10943a45e]
1 -[NSProThemeFacet drawInFrame:owner:userInfo:] + 63 (in ProKit) [0x10951bbe1]
1 -[NSProThemeFacet drawInFrame:alpha:owner:userInfo:] + 80 (in ProKit) [0x10951b641]
1 -[NSProThemeFacet drawInFrame:alpha:operation:owner:userInfo:] + 254 (in ProKit) [0x10951b311]
1 -[NSProThemeFacet _drawSpecificRenditionKey:inFrame:alpha:operation:isFocused:isFlipped:] + 416 (in ProKit) [0x109519edb]
1 DrawThreePartElementFromRenditionWithOperation + 307 (in ProKit) [0x1093f315b]
1 DrawThreePartImageWithOperationWithFocusVariant + 3031 (in ProKit) [0x1093f2c2f]
1 -[NSImage drawInRect:fromRect:operation:fraction:respectFlipped:hints:] + 1841 (in AppKit) [0x7fff915a6be7]
1 -[NSImage _usingBestRepresentationForRect:context:hints:body:] + 170 (in AppKit) [0x7fff915a70e9]
1 __-[NSImage drawInRect:fromRect:operation:fraction:respectFlipped:hints:]_block_invoke_1 + 1543 (in AppKit) [0x7fff915a8186]
1 -[NSImageRep drawInRect:fromRect:operation:fraction:respectFlipped:hints:] + 1212 (in AppKit) [0x7fff915a87ff]
1 __-[NSImageRep drawInRect:fromRect:operation:fraction:respectFlipped:hints:]_block_invoke_1 + 1525 (in AppKit) [0x7fff915a8fa9]
1 CGContextDrawImage + 434 (in CoreGraphics) [0x7fff8fe54e4e]
1 ripc_DrawImage + 1187 (in libRIP.A.dylib) [0x7fff9259f607]
1 ripc_RenderImage + 319 (in libRIP.A.dylib) [0x7fff92597d67]
1 ripl_BltImage + 1561 (in libRIP.A.dylib) [0x7fff925985c3]
1 ripl_Mark + 23 (in libRIP.A.dylib) [0x7fff9259860c]
1 argb32_image + 7521 (in CoreGraphics) [0x7fff8fdcdbe1]
1 argb32_image_mark + 1036 (in CoreGraphics) [0x7fff8fe5a0c3]
1 argb32_sample_ARGB32 + 1791 (in CoreGraphics) [0x7fff8fe68603]
1 -[NSUIHeartBeat _heartBeatThread:] + 1444 (in AppKit) [0x7fff91789000]
1 -[NSSurface flushWithOptions:] + 253 (in AppKit) [0x7fff91619943]
1 CGSFlushSurfaceWithOptions + 346 (in CoreGraphics) [0x7fff8fec7229]
1 _CGSGetSurfaceBinding + 144 (in CoreGraphics) [0x7fff8fec7349]
1 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff9518b67a]
Kernel stack:
13 semaphore_wait_continue + 0 (in mach_kernel) [0xffffff8000234650]
3 hndl_unix_scall64 + 19 (in mach_kernel) [0xffffff80002daea3]
3 unix_syscall64 + 507 (in mach_kernel) [0xffffff80005ce4cb]
3 __semwait_signal_nocancel + 155 (in mach_kernel) [0xffffff80005545cb]
3 semaphore_timedwait_trap_internal + 135 (in mach_kernel) [0xffffff8000234f27]
3 semaphore_signal_internal + 944 (in mach_kernel) [0xffffff8000234b10]
3 thread_block_reason + 275 (in mach_kernel) [0xffffff800022f413]
3 thread_go + 608 (in mach_kernel) [0xffffff800022e060]
3 processor_idle + 149 (in mach_kernel) [0xffffff800022d375]
3 machine_idle + 289 (in mach_kernel) [0xffffff80002c6461]
2 hndl_allintrs + 290 (in mach_kernel) [0xffffff80002da712]
2 interrupt + 192 (in mach_kernel) [0xffffff80002c48d0]
2 lapic_interrupt + 121 (in mach_kernel) [0xffffff80002c9ab9]
2 cpu_signal_handler + 172 (in mach_kernel) [0xffffff80002cb9ac]
2 sync_iss_to_iks + 118 (in mach_kernel) [0xffffff80002c3c76]
1 hndl_mach_scall64 + 19 (in mach_kernel) [0xffffff80002daec3]
1 thread_set_child + 336 (in mach_kernel) [0xffffff80002aef10]
1 mach_msg_overwrite_trap + 442 (in mach_kernel) [0xffffff800021bcda]
1 ipc_mqueue_receive + 63 (in mach_kernel) [0xffffff800021587f]
1 thread_block_reason + 275 (in mach_kernel) [0xffffff800022f413]
1 thread_go + 608 (in mach_kernel) [0xffffff800022e060]
1 processor_idle + 149 (in mach_kernel) [0xffffff800022d375]
1 machine_idle + 289 (in mach_kernel) [0xffffff80002c6461]
Thread 0x4a361
User stack:
19 start_wqthread + 13 (in libsystem_c.dylib) [0x7fff8c5b3b85]
19 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x7fff9518d192]
Kernel stack:
18 workqueue_mark_exiting + 1408 (in mach_kernel) [0xffffff80005a50b0]
1 hndl_unix_scall64 + 19 (in mach_kernel) [0xffffff80002daea3]
1 unix_syscall64 + 507 (in mach_kernel) [0xffffff80005ce4cb]
1 workq_kernreturn + 695 (in mach_kernel) [0xffffff80005a61f7]
1 workqueue_mark_exiting + 5124 (in mach_kernel) [0xffffff80005a5f34]
1 thread_block_reason + 275 (in mach_kernel) [0xffffff800022f413]
1 thread_go + 608 (in mach_kernel) [0xffffff800022e060]
1 processor_idle + 149 (in mach_kernel) [0xffffff800022d375]
1 machine_idle + 289 (in mach_kernel) [0xffffff80002c6461]
Thread 0x4a4c3
User stack:
19 start_wqthread + 13 (in libsystem_c.dylib) [0x7fff8c5b3b85]
19 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x7fff9518d192]
Kernel stack:
19 workqueue_mark_exiting + 1408 (in mach_kernel) [0xffffff80005a50b0]
Thread 0x4a536
User stack:
19 start_wqthread + 13 (in libsystem_c.dylib) [0x7fff8c5b3b85]
19 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x7fff9518d192]
Kernel stack:
19 workqueue_mark_exiting + 1408 (in mach_kernel) [0xffffff80005a50b0]
Thread 0x4a505
User stack:
12 start_wqthread + 13 (in libsystem_c.dylib) [0x7fff8c5b3b85]
12 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x7fff9518d192]
Kernel stack:
12 workqueue_mark_exiting + 1408 (in mach_kernel) [0xffffff80005a50b0]
Thread 0x4a507
User stack:
12 start_wqthread + 13 (in libsystem_c.dylib) [0x7fff8c5b3b85]
12 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x7fff9518d192]
Kernel stack:
12 workqueue_mark_exiting + 1408 (in mach_kernel) [0xffffff80005a50b0]
Thread 0x4a537
User stack:
12 start_wqthread + 13 (in libsystem_c.dylib) [0x7fff8c5b3b85]
12 __workq_kernreturn + 10 (in libsystem_kernel.dylib) [0x7fff9518d192]
Kernel stack:
12 workqueue_mark_exiting + 1408 (in mach_kernel) [0xffffff80005a50b0]
Binary Images:
0x107eeb000 - 0x10863cfff com.apple.Aperture 3.4 (3.4) <F66E6C13-82C8-3C10-91D2-6A749047429F> /Applications/Aperture.app/Contents/MacOS/Aperture
0x1088e2000 - 0x108dfefff com.apple.RedRock 1.9.4 (301.35) <6425F20F-6955-3997-9AEC-4E7198FC6111> /Applications/Aperture.app/Contents/Frameworks/RedRock.framework/Versions/A/Red Rock
0x1093ea000 - 0x109665ff7 com.apple.prokit 7.2.3 (1823) <0D6BA804-8262-3942-B84D-B4886082242F> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
0x10a0d2000 - 0x10a14cff7 com.apple.proxtcore 1.4.1 (250.56) <3EE2E877-CBED-3842-8927-00E0805AB8A7> /Applications/Aperture.app/Contents/Frameworks/ProXTCore.framework/Versions/A/P roXTCore
0x10a1b3000 - 0x10a2cdff7 com.apple.iLifeSQLAccess 1.7.1 (50.76) <9E4066EE-C678-31FA-946A-6EC615446067> /Applications/Aperture.app/Contents/Frameworks/iLifeSQLAccess.framework/Version s/A/iLifeSQLAccess
0x7fff8c562000 - 0x7fff8c63ffef libsystem_c.dylib ??? (???) <41B43515-2806-3FBC-ACF1-A16F35B7E290> /usr/lib/system/libsystem_c.dylib
0x7fff8c990000 - 0x7fff8c9cffff com.apple.AE 527.7 (527.7) <B82F7ABC-AC8B-3507-B029-969DD5CA813D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
0x7fff8d290000 - 0x7fff8d464ff7 com.apple.CoreFoundation 6.7.2 (635.21) <62A3402E-A4E7-391F-AD20-1EF20236CE1B> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff8fd34000 - 0x7fff906d2a27 com.apple.CoreGraphics 1.600.0 (???) <576777EA-921B-3D94-98C3-40A9CF8EBD18> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
0x7fff9154c000 - 0x7fff92152fff com.apple.AppKit 6.7.5 (1138.51) <44417D02-6123-3FC3-A119-CE51BB4C3006> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff9258a000 - 0x7fff925ceff7 libRIP.A.dylib ??? (???) <B2A38D2C-7E82-34C5-8896-48C37B0E64A3> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
0x7fff92837000 - 0x7fff92b50fff com.apple.Foundation 6.7.2 (833.25) <22AAC369-B63C-3C55-8AC6-C3ECBA44DA7B> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff93912000 - 0x7fff93920fff libdispatch.dylib ??? (???) <8E03C652-922A-3399-93DE-9EA0CBFA0039> /usr/lib/system/libdispatch.dylib
0x7fff95176000 - 0x7fff95196fff libsystem_kernel.dylib ??? (???) <66C9F9BD-C7B3-30D4-B1A0-03C8A6392351> /usr/lib/system/libsystem_kernel.dylib
0x7fff951f8000 - 0x7fff95524fff com.apple.HIToolbox 1.9 (???) <CCB32DEA-D0CA-35D1-8019-E599C8007AB6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
Process: aadvantage-helper [185]
Path: /Users/USER/Library/Application Support/AAdvantage eShopping assistant/*/aadvantage-helper.app/Contents/MacOS/aadvantage-helper
Architecture: x86_64
UID: 501
Process: AELWriter [613]
Path: /usr/sbin/AELWriter
Architecture: x86_64
UID: 0
Thread 0xef9e DispatchQueue 1
User stack:
19 ??? (in AELWriter) [0x1000010e4]
19 ??? (in AELWriter) [0x1000011b4]
19 -[NSRunLoop(NSRunLoop) run] + 62 (in Foundation) [0x7fff92842e67]
19 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 267 (in Foundation) [0x7fff92842f7b]
19 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff8d2c8486]
19 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff8d2c8c74]
19 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff8d2c050c]
19 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff9518b67a]
Kernel stack:
19 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0xef9f DispatchQueue 2
User stack:
19 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff93914316]
19 kevent + 10 (in libsystem_kernel.dylib) [0x7fff9518d7e6]
Kernel stack:
19 kqueue_scan + 416 (in mach_kernel) [0xffffff800053b4d0]
Binary Images:
0x100000000 - 0x100001fff AELWriter ??? (???) <D67CD5C5-FFFF-7F2B-92B9-3D1CEC441D45> /usr/sbin/AELWriter
0x7fff8d290000 - 0x7fff8d464ff7 com.apple.CoreFoundation 6.7.2 (635.21) <62A3402E-A4E7-391F-AD20-1EF20236CE1B> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff92837000 - 0x7fff92b50fff com.apple.Foundation 6.7.2 (833.25) <22AAC369-B63C-3C55-8AC6-C3ECBA44DA7B> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff93912000 - 0x7fff93920fff libdispatch.dylib ??? (???) <8E03C652-922A-3399-93DE-9EA0CBFA0039> /usr/lib/system/libdispatch.dylib
0x7fff95176000 - 0x7fff95196fff libsystem_kernel.dylib ??? (???) <66C9F9BD-C7B3-30D4-B1A0-03C8A6392351> /usr/lib/system/libsystem_kernel.dylib
Process: AirPort Base Station Agent [177]
Path: /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent
Architecture: x86_64
UID: 501
Thread 0x503 DispatchQueue 1
User stack:
19 ??? (in AirPort Base Station Agent) [0x10ef8e654]
19 ??? (in AirPort Base Station Agent) [0x10ef9f353]
19 CFRunLoopRun + 95 (in CoreFoundation) [0x7fff8d2d819f]
19 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff8d2c8486]
19 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff8d2c8c74]
19 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff8d2c050c]
19 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff9518b67a]
Kernel stack:
19 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x50d DispatchQueue 2
User stack:
19 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff93914316]
19 kevent + 10 (in libsystem_kernel.dylib) [0x7fff9518d7e6]
Kernel stack:
19 kqueue_scan + 416 (in mach_kernel) [0xffffff800053b4d0]
Thread 0x518
User stack:
19 thread_start + 13 (in libsystem_c.dylib) [0x7fff8c5b3b75]
19 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8c5b08bf]
19 __select + 10 (in libsystem_kernel.dylib) [0x7fff9518cdf2]
Kernel stack:
19 wakeup + 992 (in mach_kernel) [0xffffff8000555e90]
Binary Images:
0x10ef8d000 - 0x10efa4fff com.apple.AirPortBaseStationAgent 1.5.5 (155.7) <0D37CC05-D1C6-3C6C-BACD-A88D4BD4C3CD> /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent
0x7fff8c562000 - 0x7fff8c63ffef libsystem_c.dylib ??? (???) <41B43515-2806-3FBC-ACF1-A16F35B7E290> /usr/lib/system/libsystem_c.dylib
0x7fff8d290000 - 0x7fff8d464ff7 com.apple.CoreFoundation 6.7.2 (635.21) <62A3402E-A4E7-391F-AD20-1EF20236CE1B> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff93912000 - 0x7fff93920fff libdispatch.dylib ??? (???) <8E03C652-922A-3399-93DE-9EA0CBFA0039> /usr/lib/system/libdispatch.dylib
0x7fff95176000 - 0x7fff95196fff libsystem_kernel.dylib ??? (???) <66C9F9BD-C7B3-30D4-B1A0-03C8A6392351> /usr/lib/system/libsystem_kernel.dylib
Process: aosnotifyd [54]
Path: /usr/sbin/aosnotifyd
Architecture: x86_64
UID: 0
Thread 0x18f DispatchQueue 1
User stack:
19 start + 52 (in aosnotifyd) [0x10940c0b4]
19 main + 74 (in aosnotifyd) [0x1094139ec]
19 -[AOSNotificationDaemon startup] + 1294 (in aosnotifyd) [0x1094137b3]
19 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 267 (in Foundation) [0x7fff92842f7b]
19 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff8d2c8486]
19 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff8d2c8c74]
19 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff8d2c050c]
19 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff9518b67a]
Kernel stack:
19 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x351 DispatchQueue 2
User stack:
19 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff93914316]
19 kevent + 10 (in libsystem_kernel.dylib) [0x7fff9518d7e6]
Kernel stack:
19 kqueue_scan + 416 (in mach_kernel) [0xffffff800053b4d0]
Thread 0x4f3
User stack:
19 thread_start + 13 (in libsystem_c.dylib) [0x7fff8c5b3b75]
19 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8c5b08bf]
19 __NSThread__main__ + 1575 (in Foundation) [0x7fff928916a2]
19 -[NSThread main] + 68 (in Foundation) [0x7fff9289172a]
19 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 335 (in Foundation) [0x7fff9289cfd7]
19 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff8d2c8486]
19 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff8d2c8c74]
19 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff8d2c050c]
19 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff9518b67a]
Kernel stack:
19 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x519
User stack:
19 thread_start + 13 (in libsystem_c.dylib) [0x7fff8c5b3b75]
19 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8c5b08bf]
19 __select + 10 (in libsystem_kernel.dylib) [0x7fff9518cdf2]
Kernel stack:
19 wakeup + 992 (in mach_kernel) [0xffffff8000555e90]
Binary Images:
0x10940a000 - 0x10944bfff aosnotifyd ??? (???) <5287944C-EDF3-3175-81A3-CC1BEF4E43F7> /usr/sbin/aosnotifyd
0x7fff8c562000 - 0x7fff8c63ffef libsystem_c.dylib ??? (???) <41B43515-2806-3FBC-ACF1-A16F35B7E290> /usr/lib/system/libsystem_c.dylib
0x7fff8d290000 - 0x7fff8d464ff7 com.apple.CoreFoundation 6.7.2 (635.21) <62A3402E-A4E7-391F-AD20-1EF20236CE1B> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff92837000 - 0x7fff92b50fff com.apple.Foundation 6.7.2 (833.25) <22AAC369-B63C-3C55-8AC6-C3ECBA44DA7B> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
0x7fff93912000 - 0x7fff93920fff libdispatch.dylib ??? (???) <8E03C652-922A-3399-93DE-9EA0CBFA0039> /usr/lib/system/libdispatch.dylib
0x7fff95176000 - 0x7fff95196fff libsystem_kernel.dylib ??? (???) <66C9F9BD-C7B3-30D4-B1A0-03C8A6392351> /usr/lib/system/libsystem_kernel.dylib
Process: AppleMobileDeviceHelper [401]
Path: /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/Current/Apple MobileDeviceHelper.app/Contents/MacOS/AppleMobileDeviceHelper
Architecture: x86_64
UID: 501
Thread 0xb59b DispatchQueue 1
User stack:
19 ??? (in AppleMobileDeviceHelper) [0x100001678]
19 ??? (in AppleMobileDeviceHelper) [0x10000243d]
19 ??? (in AppleMobileDeviceHelper) [0x10000afb0]
19 __select + 10 (in libsystem_kernel.dylib) [0x7fff9518cdf2]
Kernel stack:
19 wakeup + 992 (in mach_kernel) [0xffffff8000555e90]
Thread 0xb59f DispatchQueue 2
User stack:
19 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff93914316]
19 kevent + 10 (in libsystem_kernel.dylib) [0x7fff9518d7e6]
Kernel stack:
19 kqueue_scan + 416 (in mach_kernel) [0xffffff800053b4d0]
Thread 0xb5ab
User stack:
19 thread_start + 13 (in libsystem_c.dylib) [0x7fff8c5b3b75]
19 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8c5b08bf]
19 __select + 10 (in libsystem_kernel.dylib) [0x7fff9518cdf2]
Kernel stack:
19 wakeup + 992 (in mach_kernel) [0xffffff8000555e90]
Binary Images:
0x100000000 - 0x100017ff7 com.apple.SyncServices.AppleMobileDeviceHelper 5.0 (889) <7B6B311D-2C94-3368-BA3F-48E449EF6A1C> /System/Library/PrivateFrameworks/MobileDevice.framework/Versions/Current/Apple MobileDeviceHelper.app/Contents/MacOS/AppleMobileDeviceHelper
0x7fff8c562000 - 0x7fff8c63ffef libsystem_c.dylib ??? (???) <41B43515-2806-3FBC-ACF1-A16F35B7E290> /usr/lib/system/libsystem_c.dylib
0x7fff93912000 - 0x7fff93920fff libdispatch.dylib ??? (???) <8E03C652-922A-3399-93DE-9EA0CBFA0039> /usr/lib/system/libdispatch.dylib
0x7fff95176000 - 0x7fff95196fff libsystem_kernel.dylib ??? (???) <66C9F9BD-C7B3-30D4-B1A0-03C8A6392351> /usr/lib/system/libsystem_kernel.dylib
Process: applepushserviced [53]
Path: /System/Library/PrivateFrameworks/ApplePushService.framework/applepushserviced
Architecture: x86_64
UID: 0
Thread 0x18e DispatchQueue 1
User stack:
19 ??? (in applepushserviced) [0x10f57b8d4]
19 ??? (in applepushserviced) [0x10f57b9b8]
19 -[NSRunLoop(NSRunLoop) run] + 62 (in Foundation) [0x7fff92842e67]
19 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 267 (in Foundation) [0x7fff92842f7b]
19 CFRunLoopRunSpecific + 230 (in CoreFoundation) [0x7fff8d2c8486]
19 __CFRunLoopRun + 1204 (in CoreFoundation) [0x7fff8d2c8c74]
19 __CFRunLoopServiceMachPort + 188 (in CoreFoundation) [0x7fff8d2c050c]
19 mach_msg_trap + 10 (in libsystem_kernel.dylib) [0x7fff9518b67a]
Kernel stack:
19 ipc_mqueue_receive_continue + 0 (in mach_kernel) [0xffffff8000215930]
Thread 0x1b0 DispatchQueue 2
User stack:
19 _dispatch_mgr_thread + 54 (in libdispatch.dylib) [0x7fff93914316]
19 kevent + 10 (in libsystem_kernel.dylib) [0x7fff9518d7e6]
Kernel stack:
19 kqueue_scan + 416 (in mach_kernel) [0xffffff800053b4d0]
Thread 0x4f4
User stack:
19 thread_start + 13 (in libsystem_c.dylib) [0x7fff8c5b3b75]
19 _pthread_start + 335 (in libsystem_c.dylib) [0x7fff8c5b08bf]
19 __select + 10 (in libsystem_kernel.dylib) [0x7fff9518cdf2]
Kernel stack: -
after I submit my book to the Apple store in I photo, it shows that it assembles and uploads, but does not finish the process. I cannot use the cancel button and have to force quit IPhoto to get out of the process.
Assuming you're referring to iPhoto on your Mac here are some potential fixes you can try:
1 -
Go to the System/Sharing preference pane and make sure Remote Apple Events is checked. If it is, uncheck it and then recheck and try ordering again.
2 -
Quit iPhoto.
From the Finder menu bar, choose Go > Utilities to access your Utilities folder (or press Shift-Command-U).
In your Utilities folder, open Keychain Access.
Find the "NetServices" entry in your Keychain Access window.
Select the "NetServices" entry and press the delete key.
Reopen iPhoto and attempt to place your order again.
You should be prompted to enter your account information if you deleted the Keychain entry successfully.
After entering your account information, you should be able to complete your order.
3 -
Boot into Safe Mode, Mac OS X: Starting up in Safe Mode, and try ordering from there.
Note: Create a proof pdf file of the book as described in this Apple document, iPhoto, Aperture: Previewing an order in iPhoto or Aperture, before ordering the book and keep the pdf file to compare with the printed copy when it arrives.
Maybe you are looking for
-
Problem saving .dv file to external hard drive
Hello - I'm trying to copy an old VHS tape to DVD. VCR to camcorder to iMovie 4.0.1 and edits all went smoothly. To create the .dv file I did File > Share > QuickTime tab > compress for Full Quality DV and created a 5.68 GB file movie1.dv - all OK. I
-
UTL_SMTP - Error while using Cc
Hi All, I have got a issue regarding sending mails via pl/sql. Unable to add an mail id using Cc. The procedure looks something like this. CREATE OR REPLACE PROCEDURE test_mail is mailhost VARCHAR2(100) := 'GASVREXC01'; conn UTL_SMTP.CONNECTION; crlf
-
Lync Server 2010 control panel - Server Error in '/cscp' Application
Hi everyone, Recently i have installed Lync 2010 with no problem at all. But when i try to open de control panel it sends me this error: Server Error in '/cscp' Application. Could not load type 'System.ServiceModel.Activation.HttpModule' from assembl
-
Smbclient wants to connect to TCP port 139
On my Powerbook, using Little Snitch under certain conditions (undetermined) I get the following message repeatedly, I am not connected to a network (except for Airport) or printer: The application "smbclient" wants to connect to 192.168.131.65 on TC
-
ITunes cant sync music. Third party applications can.
So i posted a discussion ages ago about iTunes not being able to sync my music. I have tried 5 PC's with different Windows OS's and even some Mac Machines. Before iOS7 it worked fine, then the beta was used and it did not work since even having wiped