Rebuild Aperture Periodically?

Should I rebuild Aperture Library periodically? Even if nothing is wrong?

Like all preventative maintenance procedures you are well advised to ensure a current back up, in Apertures case a current vault.
I am a big one for prevention of issues rather than waiting for a problem and then trying to fix it, both at a system level and within Aperture. I have not experienced problems after maintenance and use it regularly. This morning launched the application and it hung and then crashed as soon as it opened the last viewed album, I did a consistency check and it has been running smoothly all morning.
Remember, you are moving lots of bits of information around on your system, it only takes little to stuff up which can then compound.
Tony

Similar Messages

Images lost after rebuilding aperture database

Hi,
After updating to Yosemite, Aperture started to show problems/ freeze etc. I could not acces my photo's and after updating Aperture 'it' announced that the libraries had to be rebuild.
These are images stored on a external harddrive and we're talking about over 3000 images. (over 4 years of family holidays to be exact so they are very valuable)
I left it running day and night, and after 4 days it was still rebuilding, which is understandable for that many pictures.
Sadly a family member did not realize that the plugged in harddrive was running and unplugged it after 5 days......Naturally Aperture showed an error. When I plugged the drive back in Aperture asked to finish rebuilding the libraries. Yet when I said yes it was finished in 3seconds and Aperture won't start up nor will it show me the libraries.
While the harddrive contained 2tb of info before, it's now only 500MB. It seems like 1/4th of my images are just gone. nowhere to be found and Aperture won't start back up.
Did anyone else encounter this problem or are there any measures that can be taken to possibly resolve the images?
Any suggestions are greatly appreciated.

Do you have any vaults or other backups of the images? I think that's what you'll need to look into. If the space is free on the drive, the images are gone.
I haven't known Aperture to delete images. Is the Aperture library also stored on the external storage, or was it on an internal drive? It's most likely that something corrupted the external drive and lost the images, and also corrupted the Aperture library. I actually have had this happen to me once - in my case I also had some music files go missing from my iTunes library, which is why I think some external factor was at play.
Thankfully I had a backup (I have Aperture vaults, and a separate Time Machine backup, as well as an online backup with Backblaze). Hopefully you have at least one method of backup as you're going to need it.

Trying to rebuild aperture library using Masters

I have been having a problem with my photos for months now. Some have disapered and some have just gone crorupt. Made an appointment at the genuis bar and they told me i need to rebuild the library using the masters file on my back up drive. I attempted to do this and all it does is keeps on crashing. Does anyone have any tips as it is now doing my head in

then go in to my external hard drive and find the masters folder.
Is that a Time Machine backup or a copy of your Aperture library? Or a folder with the original master files?
If it is a Time Machine backup, did you restore the "Masters" folder from your backup or drag it over? A TimeMachine backup needs to be restored.
I have managed to import some photos into a newly created library but would like to get all my photos back.
I have then left it to move the Photos but nothing seems to happen and when you right click on the aperture icon on the desk top it says appliction not responing and has an option to force to quit.
This looks like something in the Masters folder cannot be processed.
If you have enough space on you internal drive, create two new Aperture libraries - one for testing and one as the final version.
Open the test version in iPhoto, if you have iPhoto, and the final version in Aperture, so you can have bth libraries open at the same time.
Import only small sets of images at once, 100 images or so.
First import the 100 images into the test library in iphoto, and if that succeeds without hanging, import them into your Aperture library.
Continue to test this way. If iPhoto starts to hang, try to identify the image or video that cannot be processed, and remove it.

Repair and Rebuild Aperture Library Failed

This is similar to an earlier discussion but following those suggestions didn't work, so am posting this Q == I have a library from 2009 that has 10G in it. It is a 3.4.5 Aplibrary and on trying to open it it says it has to be upgraded [not sure why] and then it comes back saying it can't = I tried to repair and also did a rebuild, and imported it into a new library == in all cases there is nothing there = no projects, no photos -- this is on an internal drive on my MacPro and all dries are extended/journaled.
I opened the package contents and find the following -- before I do anything else, what should I do next?

Looking at your screen shot it does not appear promising. The Masters folder as well as the Previews, Thumbnails and others are reporting there size as 0 bytes, basically empty. Were the masters in this library referenced?
You say this is a library from 2009 but that it was a 3.4.5 library, how can that be? 3.4.5 is a fairly recent release. Did you open and upgrade this library at some point before trying to open it now?
Message was edited by: Frank Caggiano - BTW is this related to your other thread on the library size discrepancy between copied Aperture libraries?

Formatted disk drive: How to rebuild Aperture library?

Last night I thought I was formatting a USB drive, and instead formatted my Drobo containing my entire Aperture library. Even now, 24 hours later, I break into a cold sweat thinking about it. 1.5Tb of images, my life's work, wiped.
I am going to Drive Savers on Monday, and believe based on my initial experiments that they will be able to recover at least some of the files. But I think that the drive structure is lost...
If this is the case, is there any way to reconstruct my Aperture data from the component files absent the directory structure and file names?
Please?

"Your life's work" in only one place without a backup? 'nuf said, now you know better. *Even redundant storage is no replacement for a proper backup!*
IF Drive Savers can salvage your data, they may also be able to save the structure (Aperture database). Hopefully, your initial experiments didn't write to the drive in question much. Once you noticed the foul-up, you should have ceased all writing to that disk immediately to preserve any chance of forensic salvage. If you can get enough of the Aperture database restored, you will likely need to rebuild the database (command-option and launch) on Aperture startup of your library.
Supposing that Drive Savers can't restore the Aperture database, you'll only likely be able to reconstruct your data by manually reverse-engineering the salvaged photos and available data elements (structure and extended attributes).
Do you happen to have a Time Machine backup anywhere?
I HIGHLY recommend investment into some online storage or other legitimate backup scheme when you have so much value in your data. NEVER in only one place, no matter how redundant. With a Mac Pro, you can fit up to FOUR hard drives internally, at least one should have had an Aperture vault or copy of the library.
HTH.

Aperture 3.5 issue syncing to iPad & iPhone vs. Apple TV

Hi. Longtime user of Aperture, since v 1.5, and iOS, since the very first iPhone. I'm currently on the latest versions of all software, for Aperture, Mavericks, iOS and AppleTV.
I have several hundred projects and several hundred smart albums in my Aperture library, and I've always enjoyed being abe to display my photography by syncing to my iPhone, my iPad and AppleTV. I have never found the iPhone and iPad syncing to work to my satisfaction, but ultimately I've been able to get it to pretty much work. I'm now struggling with an issue that I cannot resolve.
Everything syncs fine with Apple TV.
However, when syncing via iTunes to both my iPhone 5 and my iPad 2, I get all sorts of issues - in that many pictures simply don't sync. For instance, I have a smart album called "Favorites - People" - but only 125 of 162 pictures in the Aperture smart album appears in the iPad album. For my "Favorites - Great Outdoors" smart album, only 42 of 53 appear in the iPad. I'm having these kinds of problems in many, many of my smart albums.
I've done the following to try to resolve the problem:
-rebuild Aperture library
-repair Aperture library
-update all Previews
-delete iPod Photo Cache
-completely restore iPad and iPhone to factory settings and start again.
No luck. Any suggestions?

Don't have any solutions to offer, but I sympathize, because I have had that occur in the past. A few images simply refused to sync from Smart Albums, for reasons which completely eluded me. Very frustrating!
The problem seemed to have resolved itself, but I always suspected the problem was mainly with the system-wide media browser (whatever it's called).

HT203156 iTunes no longer syncs Aperture pictures with iPad & iPhone despite emptying iPod Photo cache in my Aperture library

Tried to repair and even rebuild Aperture database as suggested in Help with iTunes Sync - Stuck on importing photos . . . and it does not help.
I also have followed https://photoapps.expert/help/faqs/common-aperture-questions-issues-and-rep/aper ture-photos-arent-syncing-to-my-ipadiphoneipod-correctly.html#.VTVQ3s41TA4
looks like this issue arose with OS X 10.3 and the new Photos app

Just two edits
1/ Sync works with the new Photos app.
2/ iTunes does display Apertures folder / project tree in the photos sync section (allowing you to pick what to sync) yet does NOT display the corresponding number of pictures

Aperture keeps crashing on startup!

I recently moved my library with all referenced master to another 2TB drive. After doing that I imported a dozen of weddings and that took all the night.
After the import was done Aperture just crashes everytime on startup.
I tried with both repairing permission and database with no success, the REBUILD database seems to fix the problem for a while, but then it keeps crashing again just every time.
I don't think it's a drive problem, I run disk utility and at first there was some little problem with the disk which was soon fixed, now the disk is ok and I rebuilt the database several times already... what should I do now?
Anyone has the same problem?
ps. After database rebuild aperture keeps processing files on startup and crashes, what is that processing?
Thank you for your help.
Guido

Hi Frank,
I have a Mac Pro 8 intel core with 16 gig ram, OSX 10.6.8, Aperture 3.1.3.
The problem started presumably after the last import, was roughly 10,000 raw images from a DsmkIII and a mkIV.
No new software or hw installed but the HD which is an hitachi deskstar 7K3000.
After copying the lib and the masters from another drive i normally ran aperture so I guess importing all those images could have caused the problem, but Aperture is supposed to manage great amount of data...
If I create a new library everything works fine. The old library (the one I copied before importing) still works fine.
I get a crash report, never read it but the error code is something like BAD_ACCESS_ and other things..

TS3946 Aperture Book: images look fine in Aperture but not in PDF preview. OS 10.9, Aperture 3.4.5

Aperture 3.4.5, OS 10.9. When making a PDF prior to ordering a book, I note that images look fine within Aperture book module, but about 10 out of 100 images look terrible in the PDF. Shall I ignore this and go ahead and order the book?

Hi,
Strangely I'm now having exactly the same problem all of a sudden. I've been building the book for about a month now (I've made about 6 before without any trouble) and along the way have been producing a pdf of the book to see how it will look. Yesterday I noticed some of the images seemed to have lost colour when looking at the pdf version and then today, many pictures all of a sudden look exactly like the example you've supplied above.
I've tried shutting down my imac and restarting thinking it was a memory issue, have checked if I had any filters activated (which I don't and I haven't used filters in books before either), have tried repairing then rebuilding aperture, copying the book to a new library, new location, opening on a different mac and then printing again but none of this had any positive effect.
So from what I understand from your last post, the workaround you came up with was to revert to the original of each image that had the problem and then make the adjustments again?

Major Aperture failures...again.

After using Aperture for the last six months and mistakenly putting my faith in it, it appears that I have now lost my entire library of almost 280,000 images.
The backup vaults (4 of them) are all failing when attempting to restore the library. They crash the computer (G5 Dual Core) with no errors, just a freeze and then the fans rev up.
The computer has been back to Apple three times in six months and they refuse to do anything to resolve the issue after failing to replicate the crashing at the apple store. Of course, their idea of testing is to fire up a fractal generator and let it run and see if it crashes. Today, I have had 24 crashes in 5.5 hours just working in Aperture, or should I say, just trying to recover my images.
If I had only backed up to one vault, I could understand it but all FOUR of my vaults are failing to recover the images. I am a full time working photographer and this mistake of a system is on the verge of putting me out of business.
The really sad part about this is that I have a three year old PC running XP that I use for accounting that NEVER crashes!
I'm ready to take this G5 out back, load up some 00 in the 12 gauge and put it out of it's misery. After spending twenty years as a dedicated Mac user, I am through with it. I am ready to buy a PC and a copy of Lightroom and get some work done.
And what is this I hear about apple firing the entire Aperture development group? Is this true? If so, Apple needs to go public and warn people to stop using this software until it gets past beta stage. Apple is starting to follow in the footsteps of SGI, and we know where they are going.
I am open to any suggestions.

This may sound silly, but I have to ask and suggest
it, as it has been documented and it also affected my
system.
I have a G5 dual core. When I first received the
machine, it was crashing all the time and the fans
rev'd up exactly the same as you described. The
machine was seriously flawed and I also was ready to
send it back to Apple, until........
I read that there is/was a problem with the energy
saver portion of OS X and the G5. Once I turned off
the energy saver options in OS X and did all the
usual zapping and rebuilding of stuff, my machine has
run flawlessly.
I hope that this is the case in your situation, as it
is easy to fix.
Should this fail, I would simply take the entire
machine back and demand a replacement. Don't leave
the store without one. If necessary, demonstrate the
crashing for Apple. Video tape it, do it in person,
show a log file from the computer, do whatever you
need to do.
Thanks for the info on the energy saver...I'll try that and see what happens.
As for Apple and their response to my claims of a bad computer...they refuse to do anything unless they can replicate the problem in the store. The flaw in their testing is that they load a fractal generator, launch it and walk away. If it doesn't crash, there isn't a problem. They do not put the computer under any real world testing.
I brought up the video taping idea and they just kind of laughed. I asked if they reviewed the logfiles and they said that they wouldn't be able to tell anything from a logfile. Sure glad the computer is generating a logfile since it's so useful.
Here's my crash log for the last three + weeks...tell me that there isn't a problem with this computer.
Date Time Details
5-Jul 11:21AM Photoshop Action
5-Jul 1-40PM Firefox browsing while iTunes playing
5-Jul 5:07PM Yahoo IM/Firefox
6-Jul 12:05PM Photoshop - text layers edit - lost all work
6-Jul 1:47PM Aperture - Emailing Images
7-Jul 4:20PM Firefox - clicked back button
7-Jul 4:30PM Firefox - IDLE
8-Jul 3:09AM IDLE
8-Jul 10:45AM Crashed on Startup
8-Jul 10:47AM Crashed on Startup
9-Jul 6:50PM Crashed launching Aperture
10-Jul 3:45PM INSTALLED NEW HARD DRIVE & Installed OSX
10-Jul 3:50PM Crashed during OS install
10-Jul 3:55PM Crashed at "Wilkommen" screen
10-Jul 3:57PM Crashed at "Wilkommen" screen
10-Jul 4:02PM Crashed at "Chinese" screen
10-Jul 4:06PM Crashed at "Chinese" screen
10-Jul Second OSX Re-Install
10-Jul 4:54PM Crashed at "Valkommen" screen
10-Jul 5:35PM Crashed at "Select your keyboard"
10-Jul 6:15PM Crash launching Safari
10-Jul 6:22PM Crash closing Safari
10-Jul 6:25PM Crash - opening applications directory
10-Jul 6:30PM Crash - Launching Firefox
10-Jul 6:35PM Crash - moved mouse
10-Jul 6:38PM Crash - Loading mozilla.org in Firefox
10-Jul 6:45PM Crash on boot
10-Jul 6:46PM Crash on boot
10-Jul 6:50PM Crash on software update
10-Jul 6:55PM Crash on software update - Java 1.3.1 8MB downloaded
10-Jul 7:02PM Crash on software update - Java 1.3.1
10-Jul 7:07PM Crash on software update - Quicktime 7.1.2 4MB downloaded
10-Jul 8:37PM Crash on software update - OSX Update 16.6MB downloaded
10-Jul 8:45PM Crash on software update - OSX Update ?MB downloaded
11-Jul In Corpus Christi all day - Did not use computer
12-Jul 2:47PM Crash - Scrolling in Firefox and backing up Aperture vault
12-Jul 5:15PM Crash - Updating Aperture Vault
12-Jul 5:20PM Crash - Updating Aperture Vault
13-Jul 3:30PM Crash - Aperture
13-Jul 3:45PM Crash - Aperture
14-Jul 11:40AM Crash - Opening folder in home directory
14-Jul 11:00PM CRASH - IMPORTING IMAGES INTO APERTURE
14-Jul 11:05PM CRASH - IMPORTING IMAGES INTO APERTURE
14-Jul 11:10PM CRASH - IMPORTING IMAGES INTO APERTURE
15-Jul 5:00AM Crash - IDLE
15-Jul 5:59PM Crash - Google Earth
16-Jul 6:50PM Crash - Opening Dashboard
18-Jul 4:00PM Crash - IDLE
18-Jul 5:10PM Crash - Google Earth
18-Jul 5:20PM Crash - Google Earth
18-Jul 5:40PM Crash - Idle
19-Jul 10:42AM Crash - Firefox
22-Jul 9:51AM Crash - Firefox
22-Jul 12:14PM Crash - Windows Media Player
22-Jul 12:22PM Crash - Firefox
22-Jul 8:00PM Crash - Idle
22-Jul 9:25AM Crash - IDLE
24-Jul 9:31AM Crash - Firefox loading page
24-Jul 7:30PM Crash - Software update
26-Jul 11:10AM Crash - Apple Mail - Responding to email
26-Jul 12:25PM Crash - Photoshop - Clone tool - Lost all work, again!!!!!
26-Jul 12:32PM Crash - Photoshop - Clone tool
26-Jul 12:57PM Crash - Photoshop - Clone tool
26-Jul 1:04PM Crash - Photoshop - Clone tool
26-Jul 8:10PM Crash - Firefox loading page
27-Jul 10:35AM Crash - Opening Dashboard
27-Jul 10:57AM Crash - Dashboard
27-Jul 11:40AM Crash - IDLE
28-Jul 12:45PM Crash - Firefox
Ran Diskwarrior
28-Jul 5:30PM Crash - Aperture backup
29-Jul 8:45AM Crash - IDLE
30-Jul 12:30PM Crash - IDLE
31-Jul 5:09PM Crash - Updating Aperture Vault
31-Jul 5:15PM Crash - Updating Aperture Vault
31-Jul 5:30PM Crash - Recovering Aperture Library
31-Jul 5:45PM Crash - Recovering Aperture Library
31-Jul 5:50PM Crash - Recovering Aperture Library
31-Jul 5:56PM Crash - Recovering Aperture Library
31-Jul 6:01PM Crash - Recovering Aperture Library
31-Jul 6:07PM Crash - Recovering Aperture Library
31-Jul 6:11PM Crash - Recovering Aperture Library
31-Jul 6:19PM Crash - Recovering Aperture Library
31-Jul 6:24PM Crash - Aperture - Checking projects
31-Jul 6:35PM Crash - Aperture - Checking projects
31-Jul 6:39PM Crash - Replying to an email in Mail.app
31-Jul 6:47PM Crash - Aperture - Checking projects
31-Jul 6:58PM Crash - Aperture - Checking projects
31-Jul 7:32PM Crash - Aperture - Deleting duplicates from library
31-Jul 7:38PM Crash - Aperture - Checking projects
31-Jul 7:40PM Crash - Aperture - Checking projects
31-Jul 8:34PM Crash - Exporting images from Aperture
31-Jul 8:40PM Crash - Aperture
31-Jul 9:02PM Crash - Aperture - Trying to export Masters
31-Jul 9:11PM Crash - Restoring Aperture library
31-Jul 9:17PM Crash - Restoring Aperture library
31-Jul 9:22PM Crash - Restoring Aperture library
31-Jul 10:23PM Crash - Restoring Aperture library
31-Jul 11:32PM Crash - Restoring Aperture library
31-Jul 11:43PM Crash - Restoring Aperture library
Reinstalled Aperture 1.0
1-Aug 12:04AM Crash - Restoring Aperture library
Applied Aperture 1.0.1 Update
1-Aug 12:22AM Crash - Restoring Aperture library
Applied Aperture 1.1 Update
1-Aug 12:34AM Crash - Restoring Aperture library
Applied Aperture 1.1.1 Update
1-Aug 12:40AM Crash - Restoring Aperture library
Applied Aperture 1.1.2 Update
1-Aug 12:49AM Crash - Restoring Aperture library
1-Aug 8:44AM Crash - Restoring Aperture library
1-Aug 9:12AM Crash - Rebuilding Aperture library
1-Aug 9:50AM Crash - Rebuilding Aperture library
1-Aug 10:14AM Crash - Rebuilding Aperture library
1-Aug 10:24AM Crash - Rebuilding Aperture library
1-Aug 10:32AM Crash - Rebuilding Aperture library
1-Aug 11:00AM Crash - Rebuilding Aperture library
1-Aug 11:19AM Crash - Rebuilding Aperture library
1-Aug 11:33AM Crash - Rebuilding Aperture library

Stability and Performance Issue With Aperture 3

I'm running Aperture 3.0.3 on my iMac. This is a switch from Adobe products and I'm having a ton of stability and performance problems.
Environment:
* My library is about 32,000 images, about 1/3 of which are 21 megapixel, the remainder are 10 megapixels or smaller.
* I have no smart albums.
* All images are referenced and live on an external FW800-connected RAID5 array. The library lives on my internal drive.
* I have an Apple Cinema display connected through the mini-DVI port.
Here's what's happening. Initially, Aperture starts up fine and things are peachy. After a few adjustments -- particularly cloning or patching, rendering becomes slow. It becomes slow as in a minute or more. On a 21 megapixel file, this is an incredible productivity killer. Here is what I've tried to make Aperture go faster (not all at the same time):
- Log in holding the shift key to make sure nothing but core system stuff is running
- Rebuild Aperture library
- Defragment internal hard disk using iDefrag
- Export a subset of images to a separate library and work on them there
None of these has had the desired effect. Worse, if I switch to full-screen mode, the whole interface becomes balky and can become unresponsive to the point where the only way out is to cold reboot the computer. Cmd+TAB doesn't even work.
I can't imagine this is an experience shared by many users of the screaming would be deafening. Lightroom and Photoshop are insanely fast by comparison so it can be done -- and on this computer.
What are the best practices for speeding up Aperture?
Thanks,
Steve
Message was edited by: films-so-last-year

Have you tried the Bergsma BAsh?
Many of us who have upgraded our library's over time have cleaned out caches using a technique discovered by Matthew Bergsma . It cleans out some obsolete files that significantly slow aperture 3 down.
Here's what you should do:
Quit aperture
Navigate to your aperture library.
Ctrl click library and select show package contents
Open the thumbnails folder and drag contents to trash.
Then delete the entire contents of the following cache folders:
Hard Drive/Library/Caches
Hard Drive/System/Library/Caches
Hard Drive/Users/Your username/Library/Caches
You may also like to delete the preferences file but that's up to you.
~/Preferences/Library/com.apple.aperture.plist
Open Aperture:
Rebuild Thumbnails click library - photos
Then select one photo and apple(command) A to select all.
Then go to the photo menu and choose generate thumbnails.
It'll take a while to go through them all but once it's all done Aperture 3 should zip along
You can read Matthew's original post:
here http://discussions.apple.com/thread.jspa?threadID=2359859&start=0&tstart=0
Hope this is of help!
M.

Merged iPhoto and Aperture Libraries - Faces Didn't Transfer

I merged my iPhoto library into my Aperture library and non of the Faces or Keywords from my iPhoto library transfered.
Any suggestions?
(There was an error when I merged the two and it said it had to repair the database when Aperture reopened. Should I try to merge the two again?)
Thanks!

I have a similar problem with my Aperture library after the 3.3.2 update, see:
Re: Aperture 3.3.2 Update: All faces are gone from my main Aperture library
Repair Library did not help; What brought the faces back for me was to rebuild the Aperture library, not repair. But before you try a rebuild, back up the Aperture library and test, if the backup is in working condition.
After rebuilding, Aperture may hang, when rebuilding the faces.db. Give it plenty of time to finish, best over night. If you have to force quit, you will need to run a repair afterwards.
As to missing keywords - my keywords were still there, but the keywords HUD stopped working - the keywords were not found, when being entered into the search field. This was solved after rebuilding.
One big problem with keywords in the unified library format is, that iPhoto does not support nested, hierarchical keywords. If your Aperture library contains hierarchichal keywords, say "Animals > Birds > Sparrow" and your iPhoto library has keywords "Birds" and "Sparrow", you will end up with duplicate keywords for "Birds" and "Sparrow" at different levels of the hierarchie and any smart album and keyword control set using these keywords will no longer work. You will have to delete your keyword sets, and to merge the duplicate keywords again in the Keywords HUD. Then apply at least one keyword new, to force writing of the keywords to the library, quit Aperture, log off and on again, if you are using MacOS X Lion, relaunch Aperture. Then redefine your keyword control sets and smart albums that are using keywords.
Regards
Léonie

Aperture runs out of memory generating previews

Aperture 3.2.3
65K photos in library
OSX 10.7.3
Model Identifier:          MacPro1,1
Processor Name:          Dual-Core Intel Xeon
Processor Speed:          2.66 GHz
Total Number of Cores:          4
L2 Cache (per Processor):          4 MB
Memory:          10 GB
After moving my photoes to an external drive as referenced images, and a library rebuild, Aperture is attempting to recreatea all of my previews. After generateing a couple of hunderd previews, it runs out of memory and I can see the following errors in the system console:
5/11/12 6:03:09.040 PM [0x0-0xfe0fe].com.apple.Aperture: Aperture(37843,0xb071b000) malloc: *** mmap(size=1464881152) failed (error code=12)
5/11/12 6:03:09.040 PM [0x0-0xfe0fe].com.apple.Aperture: *** error: can't allocate region
5/11/12 6:03:09.040 PM [0x0-0xfe0fe].com.apple.Aperture: *** set a breakpoint in malloc_error_break to debug
5/11/12 6:03:09.040 PM [0x0-0xfe0fe].com.apple.Aperture: Aperture(37843,0xb071b000) malloc: *** mmap(size=1464881152) failed (error code=12)
5/11/12 6:03:09.040 PM [0x0-0xfe0fe].com.apple.Aperture: *** error: can't allocate region
5/11/12 6:03:09.040 PM [0x0-0xfe0fe].com.apple.Aperture: *** set a breakpoint in malloc_error_break to debug
5/11/12 6:03:09.041 PM [0x0-0xfe0fe].com.apple.Aperture: Aperture(37843,0xb071b000) malloc: *** mmap(size=1464881152) failed (error code=12)
5/11/12 6:03:09.041 PM [0x0-0xfe0fe].com.apple.Aperture: *** error: can't allocate region
5/11/12 6:03:09.041 PM [0x0-0xfe0fe].com.apple.Aperture: *** set a breakpoint in malloc_error_break to debug
Inactive memory quickly uses up all available memory and is not released. Quitting Aperture only releases half of the inactive memory.
Any ideas on how to get previews generated without running out of memory? I've tried running aperture in 32-bit mode, with no difference in behavior.

Are Previews being generated as you import, or later? I am asking because I can identify with memory issues when editing numerous images from my D800 in succession (which are huge), but i am not seeing it while importing.
Ernie

Aperture 3 won't export at all: images held hostage

Complaining about Aperture 3 is almost pointless now with the mess the program is obviously in, but I encountered a rather distressing problem I hadn't seen reported yet.
I can't export anything. All of my photos are locked into Aperture. If I select any export option (say, Jpeg 50%) Aperture will start exporting it and never finish. It will sit there for hours if I let it. The file will never export. Activity viewer just shows Aperture attempting to export the image and never finishing. Basically, it's holding my images hostage.
The crashing and hangups I can deal with (for now), but if I can't export a photo the program is literally useless to me. If anybody knows a way to fix this issue, please help.
Message was edited by: Padriac

I have now solved my problem, and it only cost me a day :-|
I had a few corrupted master files. Aperture was running a task to process a lot of pictures, and whenever it was reaching such a corrupted file, the task would hang, and it would not be possible to start other tasks like exporting pictures.
That rebuilding the library helped temporarily was just because after a rebuild Aperture would spend some time updating Places information, before it would start the processing task that would then eventually hang.
I identified and deleted the corrupted pictures, which solved my problem. Finding the pictures was something that I had to do by hand, though.
Since the problem is usually not with the pictures that one is working with at the moment, but with completely unrelated pictures, one possibility is to export the current project as a library and then work with just that library.
So the problem was with corrupted files that I had in my library. Still I think that Aperture should handle a situation like this more gracefully. If a task hangs, it should be possible to learn which picture it is currently working on and to kill the task.

This just in: Aperture 3.0.3 update

Described as having the following:
This update improves overall stability and fixes issues in a number of areas in Aperture 3. The key areas addressed include:
Applying adjustments such as Retouch or Chromatic Aberration
Creating and using Raw Fine Tuning presets
Viewing, adding and removing detected faces
Switching target printers and paper sizes when printing
Duplicating Smart Albums
Repairing and rebuilding Aperture libraries
Reconnecting referenced files
Working with GPS track files in Places
Searching for keywords in the Query HUD or Keyword Controls
The update is recommended for all users of Aperture 3.
Message was edited by: Tim Campbell1

lol - my Mac is set to check updates "Daily". I just happened to be in discussion forums when the Software Update window popped. I checked the forum page and hadn't noticed any posts about it, so I threw it out there.
Oh well... I tried. =)
Regards,
Tim

Rebuild Aperture Periodically?

Similar Messages

Maybe you are looking for