This discussion is archived
6989 Views 61 Replies Latest reply: Dec 13, 2007 7:18 PM by HOS
Currently Being ModeratedOct 27, 2007 8:40 PM (in response to Markson)sorry dude, mine is working fine. i did see, however, that if you're running aperture, you shouldn't use Time Machine... i wonder if that's the issue.iMac Core 2 Duo, Mac OS X (10.4.9), 2gb RAM; 256mb VRAM
Currently Being ModeratedOct 28, 2007 7:21 AM (in response to Markson)Yes, I'm having a similar problem. Aperture opens and crashes within about 20 seconds after upgrading to Leopard. I haven't disabled Time Machine but I also haven't used it. It began yesterday afternoon after I had been using Aperture all morning with no problems. It stabilized later in the afternoon enough to finish processing the images that I had been working on and export them. This morning it has begun to crash again.
Currently Being ModeratedOct 28, 2007 7:33 AM (in response to Steve Caicco)
Steve Caicco wrote:
Yes, I'm having a similar problem. Aperture opens and crashes within about 20 seconds after upgrading to Leopard. I haven't disabled Time Machine but I also haven't used it. It began yesterday afternoon after I had been using Aperture all morning with no problems. It stabilized later in the afternoon enough to finish processing the images that I had been working on and export them. This morning it has begun to crash again.
If you haven't disabled Time Machine (turned it off), if you specify a HD for Time Machine to use and if you didn't opt for it to run manually, then it's running. It's setup to backup and run every hour or so in the background. That could be the source of the problem.
I'v got Aperture running fine on Leopard on a test computer. I worked in it yesterday for a good four hours to process an assignment and it is running great. There even seems to be a speed increase of 20% or so and many of the controls within Aperture seem to be more responsive.
Currently Being ModeratedOct 28, 2007 11:55 AM (in response to Markson)You may be having a problem trying to auto-generate a preview for one of your images ( after an adjustment you made). Do you use previews? And had you been making a change to an image before the problem?
If so, do you see a small spinning circle in Aperture's interface after you launch?, clicking on that brings up the task list and it will tell you what Aperture is working on and if you are in the middle of making previews. It may be there is an image being processed that isn't good? What kind of images are you working with? which G5 machine? ( btw - If you hold down the shift key when you launch the previews will not be auto-generated. That might help you isolate the offending image/project? )1.3 Ghz AlBook // DP2.5 G5 //, Mac OS X (10.4.6)
Currently Being ModeratedOct 28, 2007 1:09 PM (in response to Clem)I've reverted back to Tiger and things are working properly again. Didn't even restore the library - same library. This strongly suggests to me that Time Machine did not corrupt the Library but that this is some kind of Leopard bug.
I think Clem is right that the system is trying to auto-generate a preview when it fails but I don't have the patience to try and figure out which one.Powermac G5 Quad, Mac OS X (10.4.5)
Currently Being ModeratedOct 28, 2007 2:38 PM (in response to Markson)It can be useful to restart your computer while holding the shift key. This causes a "clean" boot, without third-party frameworks, preference panes or other system hacks, which is a useful diagnostic tool. After upgrading to Leopard, Aperture crashed on my machine when I adjusted levels in the adjustment HUD. Upon investigation, I found preference panes in the system such as Microsoft Intellimouse, USB Overdrive and Better Finder Attributes that pre-dated Leopard. After removing them, Aperture stopped crashing during adjustments. USB Overdrive and Better Finder Attributes now have Leopard-compatible versions.MacPro, Mac OS X (10.5)
Currently Being ModeratedOct 28, 2007 2:56 PM (in response to Markson)it just started happening to me! I edited a few images without problems. Was running fine for about an hour. Then suddenly crashed after changing exposure on one of my 40D RAW images. Restarted Aperture and it promptly crashed again.PowerBook G4 1.5GHz, Mac OS X (10.4.10), 2GB RAM
Currently Being ModeratedOct 29, 2007 12:35 PM (in response to Clem)I think that this might have been my problem. I had been making an image just before the problem. After about 12 unsuccessful tries to open Aperature, each with a crash after about 20 seconds, it finally opened. I didn't do anything - no keystrokes at all - and when I could hear the hard drive stop spinning, I started using it with no problems.
I was afraid to exit it - kept it open for the last 24 hours - until I read this post which gave me the courage to shut it down (I'm working on a presentation for Thursday and can't afford to be without it). It opened up with no problems, so maybe it was just busy generating a preview?
Curious that this never happened before I upgraded, but I'm hoping my problem is solved.
Thanks, Clem. I'll keep the tip about holding down the shift key in mind.
Currently Being ModeratedOct 29, 2007 2:38 PM (in response to Markson)I was having this problem but I did a software update and they had an aperture update for Leopard which seemed to fix the problem. I had it crash like 10 times in an hour and then it hasn't happened since....Macbook Pro 2.16 GHz Intel Core Duo, Mac OS X (10.5)
Currently Being ModeratedOct 29, 2007 9:19 PM (in response to Markson)Same thing is happening to me since I installed Leopard on my iMac intel. It "Quits Unexpectedly" after a few seconds of trying to upload images. I uninstalled it & reinstalled & upgraded to 1.5.6 but it didn't make any difference. I can't use it at all.imac, Mac OS X (10.5)
Currently Being ModeratedOct 29, 2007 11:05 PM (in response to Markson)Jband, did you reinstall Leopard then upgrade, or did you upgrade to 1.5.6 then reinstalled Leopard?
I wonder if that would make a difference?
I was just getting ready to purchase Leopard, but I think I'll wait awhile until this bug is repaired. I can't afford Aperture being down or loosing my images.MacBookPro, MacProDualQuad, Mac OS X (10.4.10)
Currently Being ModeratedOct 30, 2007 12:32 PM (in response to AngeloM)FYI: When I did my install (which started this thread), I updated Aperture to 1.5.6, then upgraded Tiger to Leopard and started having the problem discussed. I then turned off Time Machine, wiped my Library and restored it from a vault and the problem continued (making me believe it was not a Time Machine/Aperture issue). I think I deleted Aperture next and reinstalled to 1.5.6. Same problem.
Finally, I archive & installed Tiger and I don't remember if I cold installed Aperture or not. But I did not wipe out the library and Aperture under Tiger just worked again.Quad G5, Mac OS X (10.4.5)
Currently Being ModeratedOct 30, 2007 6:28 PM (in response to Markson)I can consistently crash Aperture 1.5.6 by simply selecting a Smart Album. All other operations, viewing projects, adjustments, etc. appear to be working fine and actually more robustly than they did under Tiger and 1.5.
I've tried deleting the Smart Albums but can't stay on them long enough without a crash. Created new ones using the same criteria and sure enough, the system crashes usually before displaying all the images that meet the filter criteria.
Anyone else have a similar issue?
Lee's Summit, MO24" 2.16 Mhz Core 2 Duo iMac/12" 867 Mhz PB/15" 800 Mhz G4 iMac, Mac OS X (10.5), Aperture