IPhoto Memory Management Issue?!
I've been having an issue with trying to import Photos with iPhoto 9.21 for some time now and finally decided to try to figure out what's going on. Config: Mac Pro 1.1, 5 gigs RAM, 250 Gig, 500 Gig x 2 (RAID 1) where iTunes and iPhoto reside, 160 Gig for Time Machine, OSX Lion.
I believe this issue is due to a lack of memory management. Our iPhoto library is approximately 40 gigabytes and will crash when trying to import even small quantities of images/video. I've run disk permissions, deleted plists, etc. I have noticed that iphoto will use all of the available RAM on the computer when it's running.
I figured I'd try rebuilding the library using iPhoto Library Manager and while that was running, I was watching memory usage while the rebuild process was going and over time more memory was getting used. The rebuilt library hit around 27.5 gigs when I ran out of free memory and iPhoto quit.
The next step was to create a new library and try importing photos and videos again. Started with a mix of files from my iphone 4S and then RAW and jpeg files from a Canon (18 megapixel) and they all imported without issue. The same files would crash iphoto in the original library.
Adding another 4 gigs of RAM to the computer to see if that rectifies the problem assuming it doesn't get sucked dry on a 40 gig library! I'll update the post after I get the RAM installed and can try importing into the main library.
John
Finished rebuilding the library per Fix #1. Tried to import 48 RAW files and it crashed while in process. Again, the RAM Free RAM was gone! Here's the crash report:
Process: iPhoto [706]
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier: com.apple.iPhoto
Version: 9.2.1 (9.2.1)
Build Info: iPhotoProject-628000000000000~1
App Item ID: 408981381
App External ID: 4641130
Code Type: X86 (Native)
Parent Process: launchd [152]
Date/Time: 2012-01-28 15:52:26.203 -0800
OS Version: Mac OS X 10.7.2 (11C74)
Report Version: 9
Interval Since Last Report: 182337 sec
Crashes Since Last Report: 8
Per-App Interval Since Last Report: 21333 sec
Per-App Crashes Since Last Report: 8
Anonymous UUID: F900FBFC-BDD3-4299-ADFF-5CC409100C51
Crashed Thread: 44 Import thread 1
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000001568b2
VM Regions Near 0x1568b2:
shared memory 0000000000002000-0000000000003000 [ 4K] rw-/rw- SM=SHM
-->
MALLOC_SMALL 0000000004458000-0000000004800000 [ 3744K] rw-/rwx SM=PRV
Thread 0:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.HIToolbox 0x9b863a7f RunCurrentEventLoopInMode + 318
7 com.apple.HIToolbox 0x9b86ad9b ReceiveNextEventCommon + 381
8 com.apple.HIToolbox 0x9b86ac0a BlockUntilNextEventMatchingListInMode + 88
9 com.apple.AppKit 0x901bc040 _DPSNextEvent + 678
10 com.apple.AppKit 0x901bb8ab -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
11 com.apple.AppKit 0x901b7c22 -[NSApplication run] + 911
12 com.apple.AppKit 0x9044c18a NSApplicationMain + 1054
13 ??? 0x0001159a 0 + 71066
14 ??? 0x00010a29 0 + 68137
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x9b7d2b5e __select_nocancel + 10
1 libdispatch.dylib 0x938e6b11 _dispatch_mgr_invoke + 642
2 libdispatch.dylib 0x938e56a7 _dispatch_mgr_thread + 53
Thread 2:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 3:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9c674607 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 ??? 0x0175aaed 0 + 24488685
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 4:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9c674607 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 ??? 0x0175aaed 0 + 24488685
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 5:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 6:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 8:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 9:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9c674607 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 273
7 ??? 0x0175aaed 0 + 24488685
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 10:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 11:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 12:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 13:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 14:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 15:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 16:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 17:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 18:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 19:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 20:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 21:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 22:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 23:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 24:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 ??? 0x0184bf41 0 + 25476929
3 ??? 0x0184bdc9 0 + 25476553
4 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
5 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 25:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 ??? 0x0184bf41 0 + 25476929
3 ??? 0x0184bdc9 0 + 25476553
4 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
5 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 26:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01d35ac1 0 + 30628545
7 com.apple.CoreFoundation 0x9ac2f53a -[NSObject performSelector:] + 58
8 ??? 0x01763626 0 + 24524326
9 com.apple.CoreFoundation 0x9ac27091 -[NSObject performSelector:withObject:] + 65
10 ??? 0x0175acb5 0 + 24489141
11 ??? 0x0175a406 0 + 24486918
12 ??? 0x01759f55 0 + 24485717
13 ??? 0x017586c6 0 + 24479430
14 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
15 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
16 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
17 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 27:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.CoreServices.CarbonCore 0x944385a3 TSWaitOnConditionTimedRelative + 178
4 com.apple.CoreServices.CarbonCore 0x94438319 TSWaitOnSemaphoreCommon + 490
5 com.apple.CoreServices.CarbonCore 0x9443812a TSWaitOnSemaphoreRelative + 24
6 com.apple.QuickTimeComponents.component 0x91abade6 0x914ce000 + 6213094
7 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 28:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 com.apple.Foundation 0x9c6c9d40 -[NSCondition wait] + 304
4 ??? 0x0005c66a 0 + 378474
5 ??? 0x0005c5c2 0 + 378306
6 com.apple.CoreFoundation 0x9ac29e1d __invoking___ + 29
7 com.apple.CoreFoundation 0x9ac29d59 -[NSInvocation invoke] + 137
8 ??? 0x01d57e61 0 + 30768737
9 ??? 0x01d696c4 0 + 30840516
10 com.apple.CoreFoundation 0x9ac27091 -[NSObject performSelector:withObject:] + 65
11 ??? 0x01763626 0 + 24524326
12 com.apple.CoreFoundation 0x9ac27091 -[NSObject performSelector:withObject:] + 65
13 ??? 0x0175acb5 0 + 24489141
14 ??? 0x0175a406 0 + 24486918
15 ??? 0x01759f55 0 + 24485717
16 ??? 0x017586c6 0 + 24479430
17 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
18 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
19 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
20 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 29:
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x9c6fa507 -[NSCondition waitUntilDate:] + 427
4 com.apple.Foundation 0x9c6c092a -[NSConditionLock lockWhenCondition:beforeDate:] + 294
5 com.apple.Foundation 0x9c6c07fe -[NSConditionLock lockWhenCondition:] + 69
6 ??? 0x01759702 0 + 24483586
7 ??? 0x017586b0 0 + 24479408
8 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
9 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
10 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
11 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 30:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.Foundation 0x9c6d421c +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 378
7 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
8 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
9 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
10 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 31:: com.apple.CFSocket.private
0 libsystem_kernel.dylib 0x9b7d2b42 __select + 10
1 com.apple.CoreFoundation 0x9ac16195 __CFSocketManager + 1557
2 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
3 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 32:
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 ??? 0x0184bf41 0 + 25476929
3 ??? 0x0184bdc9 0 + 25476553
4 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
5 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 33:: JavaScriptCore::BlockFree
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c3e0 pthread_cond_timedwait$UNIX2003 + 70
3 com.apple.JavaScriptCore 0x92ce09dc ***::ThreadCondition::timedWait(***::Mutex&, double) + 156
4 com.apple.JavaScriptCore 0x92ed4f03 JSC::Heap::blockFreeingThreadMain() + 323
5 com.apple.JavaScriptCore 0x92ed4f3f JSC::Heap::blockFreeingThreadStartFunc(void*) + 15
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 34:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc2382a pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x91bdccc9 0x914ce000 + 7400649
4 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 35:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc2382a pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x91bdccc9 0x914ce000 + 7400649
4 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 36:: jpegdecompress_MPLoop
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc2382a pthread_cond_wait + 48
3 com.apple.QuickTimeComponents.component 0x91bdccc9 0x914ce000 + 7400649
4 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
5 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 37:
0 libsystem_kernel.dylib 0x9b7d302e __workq_kernreturn + 10
1 libsystem_c.dylib 0x9bc79ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x9bc7b6fe start_wqthread + 30
Thread 38:
0 libsystem_kernel.dylib 0x9b7d2b0a __rename + 10
1 libsystem_kernel.dylib 0x9b7d1c53 rename + 25
2 com.apple.CoreFoundation 0x9ac151bc -[CFXPreferencesPropertyListSourceSynchronizer writePlistToDisk] + 1052
3 com.apple.CoreFoundation 0x9abd9ab3 -[CFXPreferencesPropertyListSourceSynchronizer synchronizeAlreadyFlocked] + 595
4 com.apple.CoreFoundation 0x9abd981e -[CFXPreferencesPropertyListSourceSynchronizer synchronize] + 526
5 com.apple.CoreFoundation 0x9ac1c88a __-[CFXPreferencesPropertyListSource synchronizeInBackgroundWithCompletionBlock:]_block_invoke_1 + 122
6 libdispatch.dylib 0x938e4e11 _dispatch_call_block_and_release + 15
7 libdispatch.dylib 0x938e6797 _dispatch_queue_drain + 224
8 libdispatch.dylib 0x938e663c _dispatch_queue_invoke + 47
9 libdispatch.dylib 0x938e5e44 _dispatch_worker_thread2 + 187
10 libsystem_c.dylib 0x9bc79b24 _pthread_wqthread + 346
11 libsystem_c.dylib 0x9bc7b6fe start_wqthread + 30
Thread 39:: CVDisplayLink
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be78 _pthread_cond_wait + 914
2 libsystem_c.dylib 0x9bc7bf7b pthread_cond_timedwait_relative_np + 47
3 com.apple.CoreVideo 0x953f92e8 CVDisplayLink::waitUntil(unsigned long long) + 306
4 com.apple.CoreVideo 0x953f843a CVDisplayLink::runIOThread() + 706
5 com.apple.CoreVideo 0x953f8161 _ZL13startIOThreadPv + 160
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 40:
0 libsystem_kernel.dylib 0x9b7d302e __workq_kernreturn + 10
1 libsystem_c.dylib 0x9bc79ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x9bc7b6fe start_wqthread + 30
Thread 41:
0 libsystem_kernel.dylib 0x9b7d302e __workq_kernreturn + 10
1 libsystem_c.dylib 0x9bc79ccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x9bc7b6fe start_wqthread + 30
Thread 42:: com.apple.appkit-heartbeat
0 libsystem_kernel.dylib 0x9b7d2bb2 __semwait_signal + 10
1 libsystem_c.dylib 0x9bc2c7b9 nanosleep$UNIX2003 + 187
2 libsystem_c.dylib 0x9bc2c558 usleep$UNIX2003 + 60
3 com.apple.AppKit 0x90403be2 -[NSUIHeartBeat _heartBeatThread:] + 2399
4 com.apple.Foundation 0x9c6c7f7d -[NSThread main] + 45
5 com.apple.Foundation 0x9c6c7f2d __NSThread__main__ + 1582
6 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
7 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 43:: Import thread 0
0 libsystem_kernel.dylib 0x9b7d0c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x9b7d01f6 mach_msg + 70
2 com.apple.CoreFoundation 0x9abbf0ea __CFRunLoopServiceMachPort + 170
3 com.apple.CoreFoundation 0x9abc8214 __CFRunLoopRun + 1428
4 com.apple.CoreFoundation 0x9abc78ec CFRunLoopRunSpecific + 332
5 com.apple.CoreFoundation 0x9abc7798 CFRunLoopRunInMode + 120
6 com.apple.AE 0x9367024f AESendMessage + 4116
7 com.apple.ImageCapture 0x93e8c462 ICAAESendMessage + 192
8 com.apple.ImageCapture 0x93e8c112 ICACommand::SendSync() + 62
9 com.apple.ImageCapture 0x93e8c00e ICACommand::ProcessCommand() + 74
10 com.apple.ImageCapture 0x93e8def3 ICADownloadFile + 819
11 ??? 0x0029a2fb 0 + 2728699
12 ??? 0x006831de 0 + 6828510
13 ??? 0x00150aeb 0 + 1379051
14 ??? 0x001508ef 0 + 1378543
15 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
16 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 44 Crashed:: Import thread 1
0 ??? 0x001568b2 0 + 1403058
1 libobjc.A.dylib 0x9369754e _objc_rootRelease + 47
2 ??? 0x0067b2de 0 + 6795998
3 ??? 0x001512a0 0 + 1381024
4 ??? 0x001508ef 0 + 1378543
5 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
6 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 45:: Import thread 2
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 ??? 0x0068446c 0 + 6833260
4 ??? 0x00683178 0 + 6828408
5 ??? 0x00150aeb 0 + 1379051
6 ??? 0x001508ef 0 + 1378543
7 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 46:: Import thread 3
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 ??? 0x0068446c 0 + 6833260
4 ??? 0x00683178 0 + 6828408
5 ??? 0x00150aeb 0 + 1379051
6 ??? 0x001508ef 0 + 1378543
7 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 47:: Import thread 4
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 ??? 0x0068446c 0 + 6833260
4 ??? 0x00683178 0 + 6828408
5 ??? 0x00150aeb 0 + 1379051
6 ??? 0x001508ef 0 + 1378543
7 libsystem_c.dylib 0x9bc77ed9 _pthread_start + 335
8 libsystem_c.dylib 0x9bc7b6de thread_start + 34
Thread 48:: Import thread 5
0 libsystem_kernel.dylib 0x9b7d283e __psynch_cvwait + 10
1 libsystem_c.dylib 0x9bc7be21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9bc2c42c pthread_cond_wait$UNIX2003 + 71
3 ??? 0x0068446c 0 + 6833260
4 ???
Similar Messages
-
Last month I downloaded this software called Sponge to get rid of duplicated pictures. I had about 6000+ pictures then. Now when it found a duplicated pic, they went in the trash and I kept it in there till I got the job done. So then I opened my iPhoto and to my surprise almost all of my pics had the exclamation point. I got really scared. So I checked the Pictures>iPhoto Library folder and all my pics are still there. So thankfully I still had all the duplicated pics in the trash, so I pulled them out and imported them back to iPhoto thinking that will solve the problem. That only made things worse! Now I have over 11000 pics and still exclamation points!
So I have been reading all the forums here and they say to use the iPhoto Library Manager . So i have used that but i have some problems with it. It seems like it is rebuilding my library but it always stops because its running out of room. I know i need to delete some pics but if i do that what will happen?
I was also wondering : If I take everything out of iPhoto , will it also be gone in the iPhoto Library Folder?
I'm just so confused on which approach I should take to recover my beloved pics.
Thanks for all your help in advanceWelcome to the Apple Discussions.
Your problem begins here:
Last month I downloaded this software called Sponge to get rid of duplicated pictures.
Using this on your iPhoto Library Folder has broken the cardinal rule of using iPhoto: Don't change anything in the iPhoto Library Folder via the Finder or any other application. iPhoto depends on the structure as well as the contents of this folder. Moving things, renaming things or otherwise making changes will prevent iPhoto from working and could even cause you to damage or lose your photos.
This app does not understand iPhoto and so it has damaged your Library:
Unfortunately you compounded the problem:
I still had all the duplicated pics in the trash, so I pulled them out and imported them back to iPhoto thinking that will solve the problem. That only made things worse! Now I have over 11000 pics and still exclamation points!
The ! turns up when iPhoto loses the connection between the thumbnail in the iPhoto Window and the file it represents. Re-importing the files will mean new files, it will not reconnect the old one.
You have a back up, right? These are your beloved pics, so you've got them backed up? The easiest solution to this mess is to restore from your back up and overwrite the ruined Library.
Regards
TD -
IPhoto and iPhoto Library Manager Issue With Faces
I use iPhoto ’11. I just recently imported some photos from my iMac iPhoto to my Macbook using the product iPhoto Library Manager. I thought everything went well until closer inspection. A lot of the faces in the imported library are off meaning for example, the people may be in the centre of the photo but the face tags are off to the left or right.
I thought I would manually try to fix this. However when I try to “add a face”, it looks like it’s going to work until I leave the photo and come back to it. The face tag has disappeared. Also on some photos, I can’t even click “add a face”. A few of the pictures say there is an unnamed face but there isn’t.
Any suggestions? Would it help if I reinstalled iPhoto 11?
TomIf you export out of iPhoto with Format=JPEG and the checkboxes selected to include keywords you can keep the keywords, titles and descriptions. If you check the box for Locations I believe you will get the faces also but am not sure on that.
iPhoto Library Manager keeps keywords, titles, description and Faces and Places when it copes between libraries. The fact that you had faces problems leads me believe that the library you were rebuilding with iPLM was damaged initially.
But you could check that out very easily. Create a new library, import about 10 photos and identify the faces in them. Then rebuild that library with iPLM. If it comes up the same then there's a problem with iPLM. It it comes up good then the original library was the culprit. -
Mountain Lion memory management Issue !!!
Hi,
I have a MacPro Mid-2010 quad-core intel xeon with 10 gb ram.
Im an audio engineer n i use this machine extensively for my work.
I recently updated to mountain lion.
Since updating the memory management has gone from amazing (never ran out of memory even while doing extensive tasks) to crap (running out of memory all the time).
At the moment im adding a lot of tracks to itunes while simultaneously using mp3 scan+repair to fix my mp3 files.
this to me doesnt sound like anything that my MacPro should have difficulty with but its sluggish. i can still type this message easily while the other 2 tasks are on but its just feeling slow.
now when i look at istat this is what i see:
now why would there be so much inactive memory n free mem only like 10 mb with 260 page outs?
i shouldnt be getting page outs with so much inactive memory.
getting page outs means buying more memory but i dont think i need it.
im unclear about mountain lions memory management.
please advise.
Thanks.
Gautam.I'm using version 7.0.15104.778994 and having no trouble under Mountain Lion. I think that it was a July 10th release (coinciding with the GM developer release of ML).
What version do you have?
Clinton -
ICC profiles- iPhoto colour management issues.
I read in one of the Mac magazines the following regarding the release of iPhoto 5.0.3 ...."images are no longer colour-shifted after editing;....". Does anyone know if this refers to a resolution to the long running problem whereby iPhoto would overide the embedded ICC profile when saving back into iPhoto after editng in Photoshop. I do hope so as this was an unacceptable major flaw in a programme from Apple - a firm which prides itself at being at the forefront of colour management ! I can find no reference to this is in any release notes on the Apple support site - anyone with 'inside knowledge" ?
When I place the files into the document they become noticeably over saturated.
Select the image and check the ICC profile in the Links panel link info. Make sure its profile is the expected blurb CMYK profile. If it's Document CMYK check the document CMYK profile in Edit>Assign Profiles... and make sure it is the Blurb profile. The assigned profile can be different than the Color Setting's working space profile. -
File management advice for iphoto avoiding space issues
I've just returned form a full OS crash and want to rethink my workflow approach.
I have about 50Gb of RAW & Jpeg files to re import. This will not rise more than 20% over the year. Before switching from PC to MBP I used Adobe Bridge/CS for file mgt & editing. But on switching to Macs last yr I got soon sucked in by the simplicity of iphoto. Sure, it's toy like but it's **** food at what it does and if you're just intermediate dslr snapper like me with limited time, it's okay.
BUT before I go back to it, and quickly run out of space - can someone advise on best workflow/storage option considering I don't want to invest in Aperture or others.
So what shall I do?
1) Keep my entire collection on on an external drive (with additional DVD backup for safety) and keep another smaller library of recent stuff on the MBPro (thus using 2 libraries with Library Mgr http://www.fatcatsoftware.com/iplm/). Is this safe? Any issues or guidance?
OR
2) Use Adobe Bridge to manage raw files and only import the final jpegs into iphoto for browsing showcasing etc. This would help keep the duplicates down in iphoto
Any ideas welcome.James
I would go for option one - multiple libraries managed with iPhoto Library Manager. IPLM will also help you move files between libraries. I see no safety issues. I can see no advantage to using iPhoto for one set up and Bridge for the other. I always think you should keep things simple.
Regards
TD -
Memory management in jelly bean xperia tablet s and performance issues
Most used apps are always in memory.
while recent apps few remain in memory untill memory is full.
this is how memory management is supose to work.
pretty much same as windows 7
but if this true then why are games lagging ?
http://www.youtube.com/watch?v=S3TwBlW5ibk
When their not enough memory games i suspect lagging.
if their not enough memory recent apps getting killed to free up ram.
why does't this happen ?
And why are their apps in memory that i never use ?
tv sideview never use why its in memory ?
social life again never use again using memory
reader widget again using ram again never use at all
music unlimited again in memory never actualy use
Like i say'd most used apps are in memory all the time while rest is in cache.
But my most used apps are never in ram untill i start them
now if disabled lot apps my tablet become much faster respondsive.
Can sony plz plz plz plz fix memory management stop saying you did ?
You maybe reduced random shutdowns by like 90% or 95% perhaps even 99.99%
Before random shutdowns happend because of broken memory management, which obviously still broken as i see lag in games
sony apps use way to much ram, stop treating it like a computer with infinity amount of ramI rooted my tablet, and when looking at the processor speed in SetCPU, Sony uses a governor for power management that makes the tablet run jagged... I changed the power governor to ondemand, and got MUCH better smoothness and performance, while not sacrificing my battery life. You should try it out, maybe that'll help with games and such.
-
I've had issues with my iPhoto "not responding" and as a result I am attempting to save my photos to an external hard drive using iPhoto library Manager but each time I start the program it saves some, and then when it starts iPhoto, iPhoto then goes into not responding mode. Using mac book pro, iphoto 9.5.1, and maverick 10.9.2. I have completed all of the photo library first aid steps several times, but it makes no difference, iphoto eventually goes to "not responding." Initial issues started with Time Machine back ups stopping because of iphoto. Thanks......
Do you have a back up?
If you're just trying to recover the photos you can do that much more simply:
Go to your Pictures Folder and find the iPhoto Library there. Right (or Control-) Click on the icon and select 'Show Package Contents'. A finder window will open with the Library exposed.
Look there for a Folder called 'Originals' or 'Masters'. (varies according to the version of iPhoto)
Your photos are inside - these are the originals as imported from your camera. -
Iphoto 11 rotation issue.. Please Help..
I'm having an issue with iphoto with the way it's displaying images. For some reason when I view the contents of an event it will rotate and stretch images randomly even when the thumbnails are displayed the correct way round. There seems to be no reason why this is happening,
I have been through all the rebuild options in iphoto and have rebuilt the library using iphoto library manager but it's still happening.
Sometimes when I launch iphoto it isn't an issue straight away, I have to look through several events before it starts rotating images...One the chance that it might be a preference file in your account that is the culprit first start with this:
1 - delete the iPhoto preference file, com.apple.iPhoto.plist, that resides in your
User/Home/Library/ Preferences folder.
2 - delete iPhoto's cache file, Cache.db, that is located in your
User/Home/Library/Caches/com.apple.iPhoto folder (Snow Leopard and Earlier).
or with Lion and Mt. Lion from the User/Library/Containers/com.apple.iPhoto/
Data/Library/Caches/com.apple.iPhoto folder
3 - launch iPhoto and try again.
NOTE 1: If you're moved your library from its default location in your Home/Pictures folder you will have to point iPhoto to its new location when you next open iPhoto by holding down the Option key when launching iPhoto. You'll also have to reset the iPhoto's various preferences.
NOTE 2: In Lion and Mountain Lion the Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and hit the Enter button - 10.7: Un-hide the User Library folder.
If that doesn't do the job it could be a preference file other than iPhoto's. Here's how to test that:
Trouble Shooting Preferences
NOTE: In Lion and Mountain Lion the Library folder is now invisible. To make it permanently visible enter the following in the Terminal application window: chflags nohidden ~/Library and hit the Enter button - 10.7: Un-hide the User Library folder.
1 - close all applications.
2 - open your Home/Library folder and Option-drag (copy) the Preferences folder to the Desktop.
3 - select the contents of your Home/Library/Preferences folder and drag them into the Trash bin in the Dock. You will be asked to provide your Admin password.
4 - reboot.
5 - run the application again and determine if the problems is fixed
6 - If the problem is fixed:
A - open the working Home/Library/Preferences folder.
B - Open the Preferences folder on the Desktop, select all of the contents and drag them into the working Home/Library/Preferences folder.
C - When the Copy window pops up check the "Apply to All" check box and then click on the Don't Replace or Skip button.
D - reboot.
7 - If the problem is NOT fixed, drag the contents of the Preference folder on the Desktop into the Home/Library/Preference folder and replace the entire contents that were created by clicking on Replace.
8 - reboot. -
SAP 64bit Linux application server (Linux on Power) memory config issues
Hello Everyone,
Let me give some background. I have been tasked with replacing our AIX6.1 SAP application server with new Linux on Power servers (SLES11SP3)
Our current production BW application servers (AIX) are running fine given their current setup. We are fine implementing the same size of the AIX systems on the new Linux systems, but we now have more room to grow in the fur, however when I tried to implement the Linux server using the same memory sizing I am getting runtime errors: "TSV_TNEW_PAGE_ALLOC_FAILED" with a specific user created program and process chain. The AIX servers do not run into this issue running the exact same program. When this process runs, it utilizes 3 BTC process for the program.
Using the note 941735, I have tried to correctly setup the system using STD memory implementation, however I have a feeling that I am missing something or setup something incorrectly which is causing the above issue. Looking in ST02 here is the SAP buffer parameters for two of the systems. Perhaps someone might notice something that I am not see or point me in the right direction. Please let me know if more parameters from the profile are needed. Thanks!
AIX system (existing):
ztta/roll_area 6500000 Byte Roll area per workprocess (total)
ztta/roll_first 1 Byte First amount of roll area used in a dialog WP
ztta/short_area 3200000 Byte Short area per workprocess
rdisp/ROLL_MAXFS 32768 8 kB Maximum roll file size
rdisp/ROLL_SHM 16384 8 kB Part of roll file in shared memory
rdisp/PG_SHM 16384 8 kB Part of paging file in shared memory
rdisp/PG_LOCAL 150 8 kB Paging buffer per workprocess
em/initial_size_MB 2027 MB Initial size of extended memory
em/blocksize_KB 4096 kB Size of one extended memory block
em/address_space_MB 4092 MB Address space reserved for ext. mem. (NT only)
em/global_area_MB 256 MB Extended global memory
ztta/roll_extension 2000000000 Byte Max. extended mem. per session (external mode)
abap/heap_area_dia 2000000000 Byte Max. heap memory for dialog workprocesses
abap/heap_area_nondia 2000000000 Byte Max. heap memory for non-dialog workprocesses
abap/heap_area_total 2000000000 Byte Max. usable heap memory
abap/heaplimit 250000000 Byte Workprocess restart limit of heap memory
abap/use_paging 0 Paging for flat tables used (1) or not (0)
abap/shared_objects_size_MB 20 MB Shared objects
Linux system (new):
ztta/roll_area 6500352 Byte Roll area per workprocess (total)
ztta/roll_first 1024 Byte First amount of roll area used in a dialog WP
ztta/short_area 3200000 Byte Short area per workprocess
rdisp/ROLL_MAXFS 131072 8 kB Maximum roll file size
rdisp/ROLL_SHM 32768 8 kB Part of roll file in shared memory
rdisp/PG_SHM 16384 8 kB Part of paging file in shared memory
rdisp/PG_LOCAL 150 8 kB Paging buffer per workprocess
em/initial_size_MB 4092 MB Initial size of extended memory
em/blocksize_KB 4096 kB Size of one extended memory block
em/address_space_MB 4096 MB Address space reserved for ext. mem. (NT only)
em/global_area_MB 256 MB Extended global memory
ztta/roll_extension 2000683008 Byte Max. extended mem. per session (external mode)
abap/heap_area_dia 2000683008 Byte Max. heap memory for dialog workprocesses
abap/heap_area_nondia 2000683008 Byte Max. heap memory for non-dialog workprocesses
abap/heap_area_total 2000683008 Byte Max. usable heap memory
abap/heaplimit 250609664 Byte Workprocess restart limit of heap memory
abap/use_paging 0 Paging for flat tables used (1) or not (0)
abap/shared_objects_size_MB 20 MB Shared objectsYes sapconf has been installed. sapconf however only sets the kernel settings.
I was able to resolve the issue by having Zero Admin tool using 'es/implementation = map' and setting the PHYS_MEMSIZE to the desired amount. Then commenting out all the values that are defaulted in the 32bit version of the memory management guide for linux and let it size many of the values. Then I simply copied those from st02. I updated the profile with those values to override default for 'es/implementation = std' and commented out PHYS_MEMSIZE as it is not needed. In a nut shell, the following parameters were updated.
es/implementation = std
em/address_space_MB = 4096
em/blocksize_KB = 4096
em/initial_size_MB = 14320
em/max_size_MB = 14326
rdisp/PG_MAXFS = 131072
rdisp/PG_SHM = 16384
rdisp/ROLL_MAXFS = 131072
rdisp/ROLL_SHM = 131072
ztta/roll_area = 6500352
ztta/roll_extension = 4000000000
ztta/roll_extension_dia = 4000000000
ztta/roll_extension_nondia = 4000000000
ztta/roll_first = 1 -
OSX inactive memory management problems
On my 2010 Macbook Air 11" running OSX 10.8 Mountain Lion, I have run into some major issues with memory management. This problem persists across both my Mac machines and multiple generations of OSX. I have a 2007 2.2 Ghz Core 2 Duo Macbook Pro Running Lion (upgraded from Tiger) with 3 gb 667Mhz DDR2 RAM and my 2010 Air 1.4Ghz Core 2 Duo (Upgraded from Snow Leopard to Mountain Lion) with 2gb 1067mhz DDR3 RAM. On both machines, for some time now, during normal usage; especially web browsing using Chrome and Safari (respectively); the inactive RAM on both machines will grow to consume around 30% of all RAM and force time consuming page outs to the mass storage drives on both machines. The Pro has a slower hard drive and the problem is the worst here, the air has a much faster SSD. I have found myself constantly having a window of Activity Monitor up on at least one of my desktops watching my RAM usage, using terminal to purge ram upwards of 10 times an hour to prevent costly page outs, especially on the Pro. I know Apple claims that inactive RAM is essentially free RAM that is temporarily storing recently used information for ease of access later and that it's supposed to be released as free memory when needed, but this obviously is not happening. Right now on my air my swap file is over 650Mb and I've seen it top 2Gb before. The air is exponentially better than the Pro due to the faster SSD, but I do notice substantial UI lag and a massive drop in fluidity as soon as my meager 2Gb is full and I start paging. The Pro is another story entirely, the entire system will essentially become unusable, having to wait several seconds for mouse clicks to even register. That's why I upgraded the stock 2Gb of RAM it comes with to 3Gb hoping that a 150% increase in RAM would help, but it just prolonged the inevitable. I still end up paging out just as bad across both systems if un checked. Even when I keep a close eye on memory usage and purge often, I still end up paging out because I'm not vigilant enough.
I have to limit my browsing to less than 5 tabs and keep my number of open programs less than 2 on both machines. My active and wired memory rarely seem to top 70%, meaning the rest gets taken by inactive, which isn't functioning as Apple claims. Even if my conclusions aobut what is happening under the hood are incorrect, something is going terribly wrong. I can't upgrade the RAM on my Air at all, and the RAM on my Pro is capped at 4Gb. I'm holding on upgrading because I don't think the excess hardware will solve this software memory problem. Whatever is happening is causing a serious drop in performance for me (yes I do know I have underpowered machines), but there has to be something I can do to speed performance. I've read about disabling the dynamic page file entirely, which just seems to crash the system when free memory is gone, and I've read about programs that claim to free memory. Those programs seem to work by taking a high priority in the process heigharchy of the OS and then proceeding to eat up large portions of RAM and releasing them as needed in an attempt to replicate the true intentions of inactive RAM, but I've heard of problems with this method as well. Does anyone have a viable solution? Monitoring my RAM usage myself and ensuring I don't end up paging out is costly, time consuming, annoying, and inefficient since I fail to catch the problem before I page if I get particularly busy. There is no other OS I've ever been acquainted with that has this problem, not any flavor of Linux, not even the dreaded windows. I seriously hope Apple can do something to manage this runaway memory problem. I'd like to be able to open more than 3 windows in Safari. I've had to purge 3 seperate times while writing this on my Air, and I now have 678 inactive memory, 741 inactive, 582 wired, and less than 14Mb free out of 2Gb with a growing swap at 680Mb. Each purge becomes less and less effective and the last one I did freed up only about 100Mb and it got eaten up again by inactive in less than 10 seconds. On my Air, the memory hog is Safari right now at 700Mb between the web content and flash player with only Facebook, youtube, and this Apple Supprt tab open. I have NO other applications running in the fore or background other than Activity Monitor and Terminal. On my Pro the memory hog is always kernel task, I use Chrome and Safari both. While the memory used by the browser does not usually take up the most substantial portion of the total used RAM out of any process, the more tabs I open, the more RAM I use. The browser is usually the second heaviest RAM hog to Kernel Task. So it seems that across the two machines there are two lsightly different manifestations of the same problem with the same results: massive performance drops and extremely annoying and costly page outs no matter the reason. I just want this problem to go away. I've used underpowered windows laptops that can open a dozen tabs in a heavier browser like IE or Firefox while using other programs like Word or Excel and more with no memory lag issues. There's no way in **** I could manage to open that many pages in a browser while using Pages and/or Numbers on either of my machines and expect reliable (swap free performance). This is just kind of sad in my opinion. Does anyone have a way to get my OSX machine running smooth so that I can remove the one thing that windows and Linux fan boys get the right to laugh at my Macs for?Hi Zephryl,
I was actually able to get an initial response from Sun on this a few months ago. However, the Sun Swing team has not followed up on a resolution for this pervasive problem, even though they noticed the same problem when running a test applet I had created for them. Apparently, I.E. is not releasing memory from the heap.
Below is a quote from a Sun rep. on this in an e-mail sent to me on Dec 4, 2002:
"I suspected the leak is in the native code because the # of handles and GDI objects keep increasing but no obvious Java objects are left behind in the Java heap during page switch."
So, until Sun and/or Microsoft work out a solution to this, anyone who uses I.E. 6 and applets for their UI seems to be in a lot of trouble.
As a note, trying to invoke the Garbage Collector does not do anything, but generally a very small amount of memory will be released (like maybe 5-10% of the memory allocated for the applet).
Cheers!
Avi Gray
Global Computer Enterprises -
Memory leak issue on Blackberry Torch 9860
I own a Blackberry Torch 9860 Os 7.0 Bundle 1465 for the last 5 months
Previously I had Blackberry Curve 9300 which I had upgraded to OS 6.0. It had memory leak issues wherein my application memory would gradually dropdown to merely KBs within a few days and I had to reboot it to restore the same.
When I purchased Torch 9860, I migrated my device settings from Curve to Torch using the Desktop Manager. I face the same memory leak issues in this new device as well. I have 3 email accounts configured on my device and some social networking applications which include facebook, twitter, and some messengers. I usually delete my emails and keep only a few useful mails for reference. Still I am facing this issue wherein I have to reboot my device to restore the application memory. It starts from 152 Mb and usually dropsdown to merely Kilobytes of memory. The phone freezes for around 1-2 minutes sometimes when I am on call, or accessing my contacts.
Also to let you know that I have a 8GB memory card on my phone which has around 1.6 GB free space. I have disabled Compression on my memory card as well.
Please advise as I am having a hard time using this time this way.
Regards,
Abhinav Sharma
Thanks and regards,
Abhinav SharmaI have the almost same problem when i run the phone gap app on the 9800 torch OS 6 than this build of 1.2 MB takes the memory of 40 MB at run time and the device gives the low memory message and close the app forcefully.
In my app phone gap is using 3-4 html pages and java script .
And when i navigate on these pages it gives this message of memory low.
Please help me to out of this .
And please suggest if any professional help in this
Thanks\\\
Vipin Tomer -
RE: (forte-users) memory management
Brenda,
When a partition starts, it reserves the MinimumAllocation. Within this
memory space, objects are created and more and more of this memory is
actually used. When objects are no longer referenced, they remain in memory
and the space they occupy remains unusable.
When the amount of free memory drops below a certain point, the garbage
collector kicks in, which will free the space occopied by all objects that
are no longer referenced.
If garbage collecting can't free enough memory to hold the additional data
loaded into memory, then the partition will request another block of memory,
equal to the IncrementAllocation size. The partition will try to stay within
this new boundary by garbage collecting everytime the available part of this
memory drops below a certain point. If the partition can't free enough
memory, it will again request another block of memory.
This process repeats itself until the partition reaches MaximumAllocation.
If that amount of memory still isn't enough, then the partition crashes.
Instrument ActivePages shows the memory reserved by the partition.
AllocatedPages shows the part of that memory actually used.
AvailablePages shows the part ot that memory which is free.
Note that once memory is requested from the operating system, it's never
released again. Within this memory owned by the partition, the part actually
used will always be smaller. But this part will increase steadily, until the
garbage collecter is started and a part of it is freed again.
There are some settings that determine when the garbage collector is
started, but I'm not sure which ones they are.
The garbage collector can be started from TOOL using
"task.Part.OperatingSystem.RecoverMemory()", but I'm not sure if that will
always actually start the garbage collector.
If you track AllocatedPages of a partition, it's always growing, even if the
partition isn't doing anything. I don't know why.
If you add AllocatedPages and AvailablePages, you shoud get the value of
ActivePages, but you won't. You always get a lower number and sometimes even
considerably lower. I don't know why.
Pascal Rottier
Atos Origin Nederland (BAS/West End User Computing)
Tel. +31 (0)10-2661223
Fax. +31 (0)10-2661199
E-mail: Pascal.Rottiernl.origin-it.com
++++++++++++++++++++++++++++
Philip Morris (Afd. MIS)
Tel. +31 (0)164-295149
Fax. +31 (0)164-294444
E-mail: Rottier.Pascalpmintl.ch
-----Original Message-----
From: Brenda Cumming [mailto:brenda_cummingtranscanada.com]
Sent: Tuesday, January 23, 2001 6:40 PM
To: Forte User group
Subject: (forte-users) memory management
I have been reading up on memory management and the
OperatingSystemAgent, and could use some clarification...
When a partition is brought online, is the ActivePages value set to the
MinimumAllocation value, and expanded as required?
And what is the difference between the ExpandAtPercent and
ContractAtPercent functions?
Thanks in advance,
Brenda
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.comThe Forte runtime is millions of lines of compiled C++ code, packaged into
shared libraries (DLL's) which are a number of megabytes in size. The
space is taken by the application binary, plus the loaded DLL's, plus
whatever the current size of garbage collected memory is.
Forte allocates a garbage-collected heap that must be bigger than the size
of the allocated objects. So if you start with an 8MB heap, you will always
have at least 8MB allocated, no matter what objects you actually
instantiate. See "Memory Issues" in the Forte System Management Guide.
-tdc
Tom Childers
iPlanet Integration Server Engineering
At 10:37 PM 6/11/01 +0200, [email protected] wrote:
Hi all,
I was wondering if anyone had any experience in deploying clients on NT
concerning
the memory use of these client apps.
What is the influence of the various compiler options (optimum
performance, memory use etc)?
We seem to see a lot of the memory is taken by the Forte client apps (seen
in the Task Manager
of NT) in respect to the other native Window apps. For example an
executable of approx 4Mb takes up to
15Mb of memory. When I look at the objects retained in memory after
garbage collection, these are about
2Mb. Where do the other Mb's come from? -
IPhoto 6 crashes when opening with iPhoto Library Manager with external sto
I've had stored many iPhoto libraries on my Freecom Mobile Drive 160gb, accessing them via iPhoto Library Manager, for years. Suddenly, when I try to open a library, iPhoto crashes. I'm still able to go into the storage disk so I don't think this is damaged. I've also reinstalled IPLManager (using original 3.2.3), without any luck.
I get this crash report (greatly abbreviated)
PID: 809
Thread: 0
Exception: EXCBADACCESS (0x0001)
Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
Does this make sense to anyone? I can't understand why one minute everything is fine, and then the next a procedure which has worked for a long time, doesn't. BTW, I've taken off lots of junk from the Freecom external drive (have 44gb available) and 3gb available on my iBook.
Many thanks in advance for any help or advice.That
Exception Codes: KERNPROTECTIONFAILURE
is always a Data Related issue.
So use iPhoto Library Manager to rebuild the Library. 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 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 -
Tuxedo Memory Leak Issue (Tuxedo 8.1 - Windows Server 2003)
Hi
We are running tuxedo 8.1, 32 bit with patch level 258 in our windows server 2003 based production environment. We are currently facing an issue where the memory usage of machine slowly keeps on going higher and higher eventually resulting in “Memory Allocation Failure” to tuxedo servers. We then have to do a complete restart of tuxedo which stabilizes the system for other few days.
We have been analyzing the our source code in development/test environment using different tools like a customized Alzheimer tool and IBM purify but both tools reported no memory leaks. We then developed a test tuxedo server exposing a tuxedo service which simply allocates a memory to a response buffer and then returns the response buffer. I then configured tuxedo queue with same name “MEMTEST3” and configured a TMQForward server to call this “MEMTEST3” service every time a message is en-queued to the MEMTEST3 queue.
unsigned long _LIBENTRY ulTPAlloc(FBFR32 **ppc, long size)
unsigned long ulRes = MSG_SUCCESS_c;
ppc = (FBFR32 ) tpalloc("FML32", (char *) 0, size);
if (*ppc == (FBFR32 *) 0) {
vLogMessage(hGetLogHandle(), MSG_MEM_ALLOC_ERR_c, (char *) 0, (Event_t *) 0,
BM_NOSUPPRESS_c, size);
ulRes = MSG_MEM_ALLOC_ERR_c;
return (ulRes);
/*==============================================================================
Service MEMTEST2
==============================================================================*/
void MEMTEST3(TPSVCINFO *pRequest)
FBFR32 *pFmlResponse = NULL;
FBFR32 *pFml = NULL;
unsigned long ulRes = MSG_SUCCESS_c;
unsigned long ulActionCode = 0;
int iExitValue = 0;
long lTpurcode = 0;
FBFR32 *pFmlNULL = NULL;
userlog("Starting MEMTEST3 service.");
if (pRequest == NULL || pRequest->data == NULL)
vLogMessage(hGetLogHandle(), MSG_API_ARGS_ERR_c, NULL, NULL, BM_NOSUPPRESS_c);
ulRes = MSG_API_ARGS_ERR_c;
else
pFml = (FBFR32 *) pRequest->data;
userlog("MEMTEST3: GET THE MEM");
ulRes = ulTPAlloc(&pFmlResponse, 1024);
userlog("Ending MEMTEST3 service.");
tpreturn( iExitValue, lTpurcode, ( char * ) pFmlResponse , 0L, 0L );
While I was en-queuing the messages to the queue, I kept on monitoring the memory usage of the server hosting the service. What I observed was that I saw an initial hike in the usage of memory of the server followed by small jumps in memory increase. I kept on monitoring the server for a long time and the memory was never returned. What I suspect is that there is memory leak in tuxedo TMQforward process as it never released the memory allocated in the service.
Can anyone help how this situation can be avoided ?
Kind Regards,
AsimHi Todd,
Also as well as my previous question, I also found your reply to another user posting something similar at Re: Memory leaks in Tuxedo libraries
You mention that:
In general Tuxedo will free anything it allocates, although there are cases where memory is allocated and not freed because:
+1) it is one time or a fixed number of times allocations that will not continue to grow, and freeing up the memory just before exiting isn't of any benefit.+
+2) the memory is under Tuxedo's memory management functions where we manage our own look aside lists to provide better buffer allocation performance and again freeing these before process termination is of little benefit.+
Our code does only issue TPALLOC once and then a TPRETURN - could point (1) of your comment above also be something of concern to us, where we would observe a continuous growth of memory usage?
I know it may sound like a stupid question but do we need to run our code 20,000 times before memory gets freed?
Kind Regards,
Asim
Maybe you are looking for
-
Adobe premiere pro cc 2014 - constantly crashing
Naturally, my project is under deadline.. My system is running OS X 10.9.4 (13E28) late-2012 MacBook Pro Retina 2.6 GHz Intel Core i7 16GB 1600 MHz DDR3 Intel HD Graphics 4000 NVIDIA GeForce GT 650M 768Gb Flash Hard Drive My project consists of DSLR
-
Trial Balance with the combination of F.08 & F.54
Hi All i have a requirement from my client they are asking the trial balnce report in such a way that it should contians Financial statement version heads and trial balance i have checked this combination in F.08 & F.54 In F.08 the values are showin
-
Why live broadcast can be seen only on my computer? Why not be seen by other computers?
Hello, I have a problem with FMS 4.5! The live broadcast can only see on my computer. When someone tries to view broadcast, on another computer, error occurs #2048 !When I connect from another computer to see broadcast, FMC Console shows me that the
-
Can not make presenter view work in Yosemite
Can not make
-
IllegalStateException problem...
Hi, I have a problem with a jsp application. I have a form which I use to access to a secured area. To login I send to a servlet the username and the password but the result is this error: java.lang.IllegalStateException org.apache.catalina.conn