iPhoto hanging whole system during import

Discussion in 'Mac Apps and Mac App Store' started by shumster, Jun 24, 2004.

  1. shumster macrumors member

    Aug 15, 2001
    Got my Powerbook G4, 1.5ghz, 512MB RAM a couple of weeks ago, and just got round to beginning the import of my photos into iPhoto. Selected the folder that I wanted to import from (Pictures), and sat back and waited. Have about 6000+ photos.

    At about 5500 photos remaining the whole systems locks up. No response, nothing. Not even Force Quit. Had to press and hold the power button to restart. (Sidebar: In the event of this, what should I do to ensure file integrity upon restart? fsck?)

    I tried again today, this time importing photos from selected folders, and that seemed to work, until one folder that had pictures from Canada (not that location should have anything to do with it, especially Canada - I love the place :) ), about 400 photos in that folder. Thought it might be the folder size, but I previously imported a 1000+ picture folder of my wedding.

    Any ideas what might be going on? I have tried leaving for about 1/2 hour, as it might be a large file (but surely not that large), but no success. Lack of RAM? Or will I just have to import from sub-folders and cross my fingers that iPhoto doesn't lock up the system during the import?

    Thanks for any help/advice given
  2. jxyama macrumors 68040


    Apr 3, 2003
    not sure how big the pics are, but 5000+ is a lot. (5 GB at 1 MB each?)

    just to be safe and steady, i'd import them small chunks at a time...
  3. osprey76 macrumors 6502

    May 3, 2004
    Oklahoma City, OK
    Just to make sure, you're running iPhoto '04, right?
  4. shumster thread starter macrumors member

    Aug 15, 2001
    Yes, I am. Since my post, I've imported each subfolder separately, and it seems to be working.

    With regards to my sidebar - when I run fsck I add the -y option (as advised in MacAddict). I get some message saying that the disk volume is journaled or something like that, and that I should use the -f(?) to force check. If I do this, is there any chance of damage being done to the drive?

  5. jxyama macrumors 68040


    Apr 3, 2003
    no, but if you have your disk already journaled, there's no real need to fsck...

Share This Page