iPhoto hangs while trying to quit

Question

Level 1

70 points

iPhoto hangs while trying to quit

I just tried to clean up my iPhoto library by running duplicate annihilator and 2400 pictures out of 14,000 or 8 gigs were identified as duplicates. They have been moved to the trash but iPhoto will not quit.

I have had this issue before whenever I make many changes to iPhoto (merge events etc). It seems that if I am doing a lot of changes it is wise to quit iPhoto every 5 minutes or so so it doesn't hang during the quit.

At this point, iPhoto has been trying to quit for about 15 minutes, but if I try to force quit it tells me that doing so will not save any changes. This would undo all the work of finding all the duplicates.

This is getting ridiculous. I have seen countless threads on the slowness of iPhoto but not many work arounds other than a rebuild etc.

Under my activity monitor iPhoto shows to be using 0.01% of my processor.

What is the deal!?

Message was edited by: Cult Hero

iMac 20 inch, Mac OS X (10.6.2)

Posted on Nov 25, 2009 1:41 PM

Reply

Answer 1

Old Toad

Level 10

207,439 points

Nov 25, 2009 4:36 PM in response to Cult Hero

You have the duplicates moved to iPhoto's trash, right. Did you try to empty the trash? If you did and that's why you can't close iPhoto it's because iPhoto gags when deleting more than about 100 pics at a time.

You'll probably have to force quit iPhoto but there's a very good chance that the dups will still be in the trash. Did you use use option to add "duplicate" to the comments of the photos? If so they probably will be written to the dB file so will be there when you relaunch iPhoto.

If that's the case you can put the photos marked as dups into an album and then delete about 100 at a time.

Reply

Answer 2

Cult Hero Author

Level 1

70 points

Nov 25, 2009 4:38 PM in response to Old Toad

ya, I had to force quit and none of the changes were saved. I am running it again and will be deleting them in batches. It is gonna take a while as I think there are about 2000 dup's. What is the deal with iPhoto hanging up like this. I know I have a big library but nothing compared to my iTunes.

Reply

Answer 3

Cult Hero Author

Level 1

70 points

Nov 25, 2009 11:57 PM in response to Cult Hero

so this is getting really lame. I had to force quit iPhoto and run duplicate annihilator again this time marking instead of deleting the duplicates.

It only came up with 7 duplicates this time instead of 2000. That is because I had about 2000 ghost thumbnails.

I am trying to delete the thumbnails in batches of less than 10 at a time but even that is hanging iPhoto when I try and quit it.

I checked my activity monitor and it is maxing out the CPU trying to quit iPhoto to make the changes to 7 - 10 deleted ghost thumbnails?

this is ridiculous. I like all the features of iPhoto but its practicality is severely impacted if it won't let me manage the library.

In the middle of a more invasive rebuild to see if that shakes loose the cobwebs but any suggestions and I am all ears.

At this point iPhoto is becoming pretty much unusable for me.

Reply

Answer 4

Yer_Man

Level 10

162,308 points

Nov 26, 2009 12:02 AM in response to Cult Hero

I would guess that the database file has been damaged.

Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.

If that fails:

Option 2
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords, faces and places back.

Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.

Regards

TD

Reply

Answer 5

Cult Hero Author

Level 1

70 points

Nov 26, 2009 11:17 AM in response to Yer_Man

how would the database become corrupted? I am currently trying the second option and rebuilding the library as a backup library.

I am hoping that it wont' bring over the ghosts but if it does do I have any other options at that point?

With my original library, I can't even delete the ghosts anymore, they just hang up iPhoto every time.

Reply

Answer 6

Yer_Man

Level 10

162,308 points

Nov 26, 2009 11:36 AM in response to Cult Hero

The usual reason the db is corrupted is because the app is interrupted by while writing to it by a crash, hang, force quit. It can also occur when the Library is stored in a disk formatted other than Mac OS Extended (Journaled)

Regards

TD

Reply

Answer 7

Cult Hero Author

Level 1

70 points

Nov 28, 2009 12:35 PM in response to Yer_Man

so I have rebuilt the library using iPhoto Manager. It took close to 3 days. It appears that a lot of the ghost images have been removed yet I can't really tell as iPhoto takes about 5 minutes to open and then chooses to beachball and not respond everytime I try and use it. This *****.

Reply

Answer 8

Yer_Man

Level 10

162,308 points

Nov 28, 2009 12:44 PM in response to Cult Hero

Then you have another issue in there somewhere.

Any messages in the Console? And is your Library on the Start Up disk?

Regards

TD

Reply

Answer 9

Cult Hero Author

Level 1

70 points

Nov 28, 2009 12:48 PM in response to Yer_Man

library runs off a drobo as does my iTunes which performs flawlessly.

I have rebooted since the rebuild and repaired the permissions. I am completely at a loss here. This program has worked fine for long enough (since snow leopard) and now is completely hosed. Everything is in there, it just take close to 5 minutes to open, 5 minutes to quit, 5 minutes to open a picture etc etc etc.

Reply

Answer 10

Old Toad

Level 10

207,439 points

Nov 28, 2009 1:42 PM in response to Cult Hero

Try creating a new library as follows:

Creating a new library while preserving the Events from the original library.

1 - Move the existing library folder to the desktop
2 - Open the library package like this.
3 - Launch iPhoto and, when asked, select the option to create a new library.
4 - Drag the Originals folder from the iPhoto Library on the desktop into the open iPhoto window.

This will create a new library with the same Events as your current library which will be left untouched for further testing. This way you'll get a working library until you find a fix for what's ailing your current library.

Reply

Answer 11

Yer_Man

Level 10

162,308 points

Nov 28, 2009 1:50 PM in response to Cult Hero

library runs off a drobo as does my iTunes which performs flawlessly.

There's your problem then. It's not formatted Mac OS Extended (Journaled) is it?

iPhoto needs to have the Library sitting on disk formatted Mac OS Extended (Journaled). Users with the Library sitting on disks otherwise formatted regularly report issues including, but not limited to, importing, saving edits and sharing the photos.

Regards

TD

Reply

Answer 12

Cult Hero Author

Level 1

70 points

Nov 28, 2009 2:48 PM in response to Yer_Man

no, it has been on the drobo for about 2 years now. It has never had any problems up until the last week or so.

When I open iPhoto it says not responding in the activity monitor. I have to fix this.

Reply

Answer 13

Cult Hero Author

Level 1

70 points

Nov 28, 2009 3:00 PM in response to Cult Hero

here is what it says when I force quit it, there is more, but I just can't post it all

Date/Time: 2009-11-28 14:48:17 -0800
OS Version: 10.6.2 (Build 10C540)
Architecture: x86_64
Report Version: 6

Command: iPhoto
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Version: 8.1.1 (8.1.1)
Build Version: 4
Project Name: iPhotoProject
Source Version: 4190000
Parent: launchd [80]

PID: 135
Event: hang
Duration: 3.18s (sampling started after 2 seconds)
Steps: 12 (100ms sampling interval)

Pageins: 45
Pageouts: 0

Process: iPhoto [135]
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
UID: 501

Thread 6d6db7c DispatchQueue 100
User stack:
12 ??? (in iPhoto + 8426) [0x30ea]
12 ??? (in iPhoto + 1190600) [0x123ac8]
12 NSApplicationMain + 574 (in AppKit) [0x91102535]
12 -[NSApplication run] + 821 (in AppKit) [0x9110a49f]
12 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156 (in AppKit) [0x91148306]
12 _DPSNextEvent + 847 (in AppKit) [0x91148ac5]
12 BlockUntilNextEventMatchingListInMode + 81 (in HIToolbox) [0x91c1fb48]
12 ReceiveNextEventCommon + 354 (in HIToolbox) [0x91c1fcc3]
12 RunCurrentEventLoopInMode + 392 (in HIToolbox) [0x91c1ff0c]
12 CFRunLoopRunInMode + 97 (in CoreFoundation) [0x96a7b691]
12 CFRunLoopRunSpecific + 452 (in CoreFoundation) [0x96a7b864]
12 __CFRunLoopRun + 8059 (in CoreFoundation) [0x96a7dedb]
12 __NSFireTimer + 141 (in Foundation) [0x9819596c]
12 ??? (in iPhoto + 386161) [0x5f471]
12 ??? (in iPhoto + 1816632) [0x1bc838]
12 ??? (in iPhoto + 698411) [0xab82b]
12 ??? (in iPhoto + 7161636) [0x6d5724]
12 ??? (in iPhoto + 6993568) [0x6ac6a0]
12 sqlite3_step + 1639 (in libsqlite3.dylib) [0x97e24857]
12 sqlite3VdbeExec + 34017 (in libsqlite3.dylib) [0x97e20321]
12 sqlite3BtreeNext + 826 (in libsqlite3.dylib) [0x97dc2cda]
12 sqlite3BtreeNext + 650 (in libsqlite3.dylib) [0x97dc2c2a]
12 getAndInitPage + 128 (in libsqlite3.dylib) [0x97da7f80]
12 sqlite3PagerAcquire + 1760 (in libsqlite3.dylib) [0x97da7730]
12 pread$UNIX2003 + 10 (in libSystem.B.dylib) [0x9771a58e]
Kernel stack:
12 lo unixscall + 280 [0x29deb8]
12 unix_syscall + 579 [0x4ee5dc]
12 pread_nocancel + 167 [0x4969a0]
12 write + 312 [0x49634d]
12 utf8_encodelen + 3711 [0x2eea08]
12 VNOP_READ + 157 [0x2f99b9]
12 com.apple.filesystems.afpfs 9.6 + 52154 [0x520eabba]
12 com.apple.filesystems.afpfs 9.6 + 47229 [0x520e987d]
12 com.apple.filesystems.afpfs 9.6 + 76884 [0x520f0c54]
12 com.apple.filesystems.afpfs 9.6 + 65087 [0x520ede3f]
12 sock_ioctl + 40 [0x4c4738]
12 soo_select + 1176 [0x498979]
12 com.apple.nke.asp_tcp 5.0 + 14478 [0x51fd788e]
12 com.apple.nke.asp_tcp 5.0 + 11736 [0x51fd6dd8]
12 msleep + 157 [0x4882d6]
12 wakeup + 286 [0x487bb3]
12 lck mtx_sleepdeadline + 104 [0x2211a8]
12 thread_block + 33 [0x226fb5]
12 thread blockreason + 331 [0x226f27]
12 thread_dispatch + 1950 [0x226c88]
12 machine switchcontext + 753 [0x2a5a37]

Thread 6cf23d4 DispatchQueue 1634545000
User stack:
12 start_wqthread + 30 (in libSystem.B.dylib) [0x97711336]
12 pthreadwqthread + 390 (in libSystem.B.dylib) [0x977114f1]
12 dispatch_workerthread2 + 234 (in libSystem.B.dylib) [0x97711a68]
12 dispatch_queueinvoke + 163 (in libSystem.B.dylib) [0x97711cc3]
12 kevent + 10 (in libSystem.B.dylib) [0x977120ea]
Kernel stack:
12 kevent + 97 [0x471745]

Thread 64087a8
User stack:
12 thread_start + 34 (in libSystem.B.dylib) [0x97718e42]
12 pthreadstart + 345 (in libSystem.B.dylib) [0x97718fbd]
12 _NSThread__main_ + 1499 (in Foundation) [0x98167888]
12 -[NSThread main] + 45 (in Foundation) [0x981678d8]
12 -[XTRunLoopThread run:] + 421 (in ProXTCore) [0xf598a5]
12 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 279 (in Foundation) [0x981a137c]
12 CFRunLoopRunInMode + 97 (in CoreFoundation) [0x96a7b691]
12 CFRunLoopRunSpecific + 452 (in CoreFoundation) [0x96a7b864]
12 __CFRunLoopRun + 2079 (in CoreFoundation) [0x96a7c77f]
12 mach msgtrap + 10 (in libSystem.B.dylib) [0x976eb8da]
Kernel stack:
12 ipc mqueue_receivecontinue + 0 [0x210aa3]

Thread 6cf2000
User stack:
12 thread_start + 34 (in libSystem.B.dylib) [0x97718e42]
12 pthreadstart + 345 (in libSystem.B.dylib) [0x97718fbd]
12 select$DARWIN_EXTSN + 10 (in libSystem.B.dylib) [0x9770a856]
Kernel stack:
12 sleep + 52 [0x487f93]

Thread 6d6d000
User stack:
12 thread_start + 34 (in libSystem.B.dylib) [0x97718e42]
12 pthreadstart + 345 (in libSystem.B.dylib) [0x97718fbd]
12 _NSThread__main_ + 1499 (in Foundation) [0x98167888]
12 -[NSThread main] + 45 (in Foundation) [0x981678d8]
12 ??? (in iPhoto + 5307088) [0x510ad0]
12 ??? (in iPhoto + 5309106) [0x5112b2]
12 -[NSCondition wait] + 316 (in Foundation) [0x9818faef]
12 pthread condwait$UNIX2003 + 73 (in libSystem.B.dylib) [0x9771b158]
12 _semwaitsignal + 10 (in libSystem.B.dylib) [0x97719806]
Kernel stack:
12 semaphore waitcontinue + 0 [0x22a0a5]

Thread 6d6d7a8
User stack:
12 thread_start + 34 (in libSystem.B.dylib) [0x97718e42]
12 pthreadstart + 345 (in libSystem.B.dylib) [0x97718fbd]
12 _NSThread__main_ + 1499 (in Foundation) [0x98167888]
12 -[NSThread main] + 45 (in Foundation) [0x981678d8]
12 -[XTThread run:] + 387 (in ProXTCore) [0xf58363]
12 -[XTMsgQueue waitForMessage] + 49 (in ProXTCore) [0xf6a201]
12 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x9815c6d8]
12 -[NSConditionLock lockWhenCondition:beforeDate:] + 279 (in Foundation) [0x9815c7f5]
12 -[NSCondition waitUntilDate:] + 453 (in Foundation) [0x981a3a84]
12 pthread cond_timedwait_relativenp + 47 (in libSystem.B.dylib) [0x97748028]
12 semaphore timedwait_signaltrap + 10 (in libSystem.B.dylib) [0x976eb93a]
Kernel stack:
12 semaphore waitcontinue + 0 [0x22a0a5]

Thread 6d75000
User stack:
12 start_wqthread + 30 (in libSystem.B.dylib) [0x97711336]
12 _workqkernreturn + 10 (in libSystem.B.dylib) [0x97711182]
Kernel stack:
12 workqueue threadyielded + 562 [0x4cb6ae]

Thread 6d753d4
User stack:
12 thread_start + 34 (in libSystem.B.dylib) [0x97718e42]
12 pthreadstart + 345 (in libSystem.B.dylib) [0x97718fbd]
12 _NSThread__main_ + 1499 (in Foundation) [0x98167888]
12 -[NSThread main] + 45 (in Foundation) [0x981678d8]
12 -[XTThread run:] + 387 (in ProXTCore) [0xf58363]
12 -[XTMsgQueue waitForMessage] + 49 (in ProXTCore) [0xf6a201]
12 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x9815c6d8]
12 -[NSConditionLock lockWhenCondition:beforeDate:] + 279 (in Foundation) [0x9815c7f5]
12 -[NSCondition waitUntilDate:] + 453 (in Foundation) [0x981a3a84]
12 pthread cond_timedwait_relativenp + 47 (in libSystem.B.dylib) [0x97748028]
12 semaphore timedwait_signaltrap + 10 (in libSystem.B.dylib) [0x976eb93a]
Kernel stack:
12 semaphore waitcontinue + 0 [0x22a0a5]

Thread 7114000
User stack:
12 thread_start + 34 (in libSystem.B.dylib) [0x97718e42]
12 pthreadstart + 345 (in libSystem.B.dylib) [0x97718fbd]
12 _NSThread__main_ + 1499 (in Foundation) [0x98167888]
12 -[NSThread main] + 45 (in Foundation) [0x981678d8]
12 ??? (in iPhoto + 5261001) [0x5056c9]
12 pthread condwait$UNIX2003 + 73 (in libSystem.B.dylib) [0x9771b158]
12 _semwaitsignal + 10 (in libSystem.B.dylib) [0x97719806]
Kernel stack:
12 semaphore waitcontinue + 0 [0x22a0a5]

Thread 71143d4
User stack:
12 thread_start + 34 (in libSystem.B.dylib) [0x97718e42]
12 pthreadstart + 345 (in libSystem.B.dylib) [0x97718fbd]
12 _NSThread__main_ + 1499 (in Foundation) [0x98167888]
12 -[NSThread main] + 45 (in Foundation) [0x981678d8]
12 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 329 (in Foundation) [0x981a0430]
12 CFRunLoopRunInMode + 97 (in CoreFoundation) [0x96a7b691]
12 CFRunLoopRunSpecific + 452 (in CoreFoundation) [0x96a7b864]
12 __CFRunLoopRun + 2079 (in CoreFoundation) [0x96a7c77f]
12 mach msgtrap + 10 (in libSystem.B.dylib) [0x976eb8da]
Kernel stack:
12 ipc mqueue_receivecontinue + 0 [0x210aa3]

Thread 7247b7c
User stack:
12 thread_start + 34 (in libSystem.B.dylib) [0x97718e42]
12 ***::TCMalloc_PageHeap::scavengerThread() + 614 (in JavaScriptCore) [0x90125276]
12 pthread condwait$UNIX2003 + 73 (in libSystem.B.dylib) [0x9771b158]
12 _semwaitsignal + 10 (in libSystem.B.dylib) [0x97719806]
Kernel stack:
12 semaphore waitcontinue + 0 [0x22a0a5]

Thread 7403000
User stack:
12 thread_start + 34 (in libSystem.B.dylib) [0x97718e42]
12 pthreadstart + 345 (in libSystem.B.dylib) [0x97718fbd]
12 _NSThread__main_ + 1499 (in Foundation) [0x98167888]
12 -[NSThread main] + 45 (in Foundation) [0x981678d8]
12 -[XTRunLoopThread run:] + 421 (in ProXTCore) [0xf598a5]
12 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 279 (in Foundation) [0x981a137c]
12 CFRunLoopRunInMode + 97 (in CoreFoundation) [0x96a7b691]
12 CFRunLoopRunSpecific + 452 (in CoreFoundation) [0x96a7b864]
12 __CFRunLoopRun + 2079 (in CoreFoundation) [0x96a7c77f]
12 mach msgtrap + 10 (in libSystem.B.dylib) [0x976eb8da]
Kernel stack:
12 ipc mqueue_receivecontinue + 0 [0x210aa3]

Thread 7592b7c
User stack:
12 thread_start + 34 (in libSystem.B.dylib) [0x97718e42]
12 pthreadstart + 345 (in libSystem.B.dylib) [0x97718fbd]
12 _NSThread__main_ + 1499 (in Foundation) [0x98167888]
12 -[NSThread main] + 45 (in Foundation) [0x981678d8]
12 ??? (in iPhoto + 5307088) [0x510ad0]
12 ??? (in iPhoto + 5309106) [0x5112b2]
12 -[NSCondition wait] + 316 (in Foundation) [0x9818faef]
12 pthread condwait$UNIX2003 + 73 (in libSystem.B.dylib) [0x9771b158]
12 _semwaitsignal + 10 (in libSystem.B.dylib) [0x97719806]
Kernel stack:
12 semaphore waitcontinue + 0 [0x22a0a5]

Binary Images:
0x1000 - 0x9f9ffe com.apple.iPhoto 8.1.1 (8.1.1) <13A7B173-F1BC-6A25-54AC-C27E27774B17> /Applications/iPhoto.app/Contents/MacOS/iPhoto
0xf51000 - 0xf98ff7 com.apple.proxtcore 1.0.0 (1.0.0) <00010203-0405-0607-0809-0A0B0C0D0E0F> /Applications/iPhoto.app/Contents/MacOS/../Frameworks/ProXTCore.framework/Versi ons/A/ProXTCore
0x90003000 - 0x901a0fef com.apple.JavaScriptCore 6531.21 (6531.21.9) <FF236E3F-A016-2AEB-3E62-7108E76EF825> /System/Library/Frameworks/JavaScriptCore.framework/Versions/A/JavaScriptCore
0x91100000 - 0x919deff7 com.apple.AppKit 6.6.3 (1038.25) <72A9AA47-8DCB-DB07-64F5-F837E98C62D8> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x91beb000 - 0x91f0efef com.apple.HIToolbox 1.6.2 (???) <E02640B9-7BC3-A4B4-6202-9E4127DDFDD6> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x96a40000 - 0x96bb7fef com.apple.CoreFoundation 6.6.1 (550.13) <AE9FC6F7-F0B2-DE58-759E-7DB89C021A46> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x976eb000 - 0x9788ffeb libSystem.B.dylib ??? (???) <D45B91B2-2B4C-AAC0-8096-1FC48B7E9672> /usr/lib/libSystem.B.dylib
0x97d8f000 - 0x97e48fe7 libsqlite3.dylib ??? (???) <16CEF8E8-8C9A-94CD-EF5D-05477844C005> /usr/lib/libsqlite3.dylib
0x98151000 - 0x983c1ffb com.apple.Foundation 6.6.1 (751.14) <CD815A50-BB33-5AA1-DD73-A5B07D394DDA> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation

Process: Activity Monitor [155]
Path: /Applications/Utilities/Activity Monitor.app/Contents/MacOS/Activity Monitor
UID: 501

Thread 6094b7c DispatchQueue 1
User stack:
12 ??? (in Activity Monitor + 6996) [0x100001b54]
12 NSApplicationMain + 364 (in AppKit) [0x7fff84dc1468]
12 -[NSApplication run] + 395 (in AppKit) [0x7fff84dc8747]
12 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 155 (in AppKit) [0x7fff84e02b41]
12 _DPSNextEvent + 708 (in AppKit) [0x7fff84e031f2]
12 BlockUntilNextEventMatchingListInMode + 59 (in HIToolbox) [0x7fff835df70c]
12 ReceiveNextEventCommon + 310 (in HIToolbox) [0x7fff835df853]
12 RunCurrentEventLoopInMode + 333 (in HIToolbox) [0x7fff835dfa4e]
12 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff845cfc2f]
11 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff845d07a2]
11 mach msgtrap + 10 (in libSystem.B.dylib) [0x7fff81014e3a]
1 __CFRunLoopRun + 6488 (in CoreFoundation) [0x7fff845d1a58]
1 __NSFireTimer + 114 (in Foundation) [0x7fff876b5a39]
1 ??? (in Activity Monitor + 38377) [0x1000095e9]
1 ??? (in Activity Monitor + 39148) [0x1000098ec]
1 ??? (in Activity Monitor + 39892) [0x100009bd4]
1 ??? (in Activity Monitor + 41655) [0x10000a2b7]
1 read + 10 (in libSystem.B.dylib) [0x7fff8101f426]
Kernel stack:
11 ipc mqueue_receivecontinue + 0 [0x210aa3]
1 lo64 unixscall + 77 [0x29e3fd]
1 unix_syscall64 + 617 [0x4ee947]
1 read_nocancel + 158 [0x496add]
1 write + 312 [0x49634d]
1 pipeinit + 2207 [0x4982b9]
1 soreceive + 1134 [0x4b01ab]
1 sbwait + 150 [0x4b22a7]
1 msleep + 157 [0x4882d6]
1 wakeup + 334 [0x487be3]
1 lck mtxsleep + 87 [0x2217b0]
1 thread_block + 33 [0x226fb5]
1 thread blockreason + 331 [0x226f27]
1 thread_dispatch + 1950 [0x226c88]
1 machine switchcontext + 753 [0x2a5a37]

Thread 72403d4 DispatchQueue 2
User stack:
12 start_wqthread + 13 (in libSystem.B.dylib) [0x7fff8102ea55]
12 pthreadwqthread + 353 (in libSystem.B.dylib) [0x7fff8102ebb8]
12 dispatch_workerthread2 + 244 (in libSystem.B.dylib) [0x7fff8102f286]
12 dispatch_queueinvoke + 185 (in libSystem.B.dylib) [0x7fff8102f75c]
12 kevent + 10 (in libSystem.B.dylib) [0x7fff8102dbba]
Kernel stack:
12 kevent + 97 [0x471745]

Binary Images:
0x100000000 - 0x10002dff7 com.apple.ActivityMonitor 10.6 (212) <3695EF1D-2370-2826-2219-8B0F81F7F900> /Applications/Utilities/Activity Monitor.app/Contents/MacOS/Activity Monitor
0x7fff81014000 - 0x7fff811d2ff7 libSystem.B.dylib ??? (???) <526DD3E5-2A8B-4512-ED97-01B832369959> /usr/lib/libSystem.B.dylib
0x7fff835b1000 - 0x7fff838affe7 com.apple.HIToolbox 1.6.2 (???) <D463A388-244E-047A-E49A-4DA6C15BD1BA> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
0x7fff84585000 - 0x7fff846f8ff7 com.apple.CoreFoundation 6.6.1 (550.13) <1E952BD9-37C6-16BE-B2F0-CD92A6283D37> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff84dbf000 - 0x7fff857b3fff com.apple.AppKit 6.6.3 (1038.25) <2F7A5AC8-29E7-9B5F-D3F1-4C7F5821BB80> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
0x7fff8764f000 - 0x7fff878d0fe7 com.apple.Foundation 6.6.1 (751.14) <767349DB-C486-70E8-7970-F13DB4CDAF37> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation

Process: activitymonitord [166]
Path: /Applications/Utilities/Activity Monitor.app/Contents/MacOS/activitymonitord
UID: 0

Process: AirPort Base Station Agent [101]
Path: /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent
UID: 501

Thread 74ac7a8 DispatchQueue 1
User stack:
12 ??? (in AirPort Base Station Agent + 5344) [0x1000014e0]
12 ??? (in AirPort Base Station Agent + 70666) [0x10001140a]
12 CFRunLoopRun + 70 (in CoreFoundation) [0x7fff845cf9b6]
12 CFRunLoopRunSpecific + 575 (in CoreFoundation) [0x7fff845cfc2f]
12 __CFRunLoopRun + 1698 (in CoreFoundation) [0x7fff845d07a2]
12 mach msgtrap + 10 (in libSystem.B.dylib) [0x7fff81014e3a]
Kernel stack:
12 ipc mqueue_receivecontinue + 0 [0x210aa3]

T

Reply

Answer 14

Yer_Man

Level 10

162,308 points

Nov 28, 2009 11:57 PM in response to Cult Hero

no, it has been on the drobo for about 2 years now. It has never had any problems up until the last week or so.

Yes, folks regularly report that everything was fine and then suddenly it n longer works. All I can tell you is that now it won't work. Some folks have got a few days out of it, some, like you, a couple of years. But once it goes, it's gone.

I have to fix this.

The only fix is to move it to an appropriately formatted disk.

Regards

TD

Reply

Answer 15

Cult Hero Author

Level 1

70 points

Nov 29, 2009 7:57 AM in response to Yer_Man

so I used Time Machine to rebuild iPhoto from a month ago and I moved the library onto my desktop. Same problem. I have 12,776 pictures and while iPhoto will launch in less than 10 seconds it will freeze up moving photos to the trash and opening events.

I have to force quit as although activity monitor says that iPhoto is responding it is using 0% of the CPU and is in permanent freeze.

Reply