Memory management getting worse
So I've been using the same machine, working in the same file sized roughly 3k by 5k, making concept art for 2 years now, not much has changed in terms of how I worked over the years. Photoshop always hogs any extra memory I have on my machine, it like a memory leak. When I start working and load a file it's fine, as I work on the same file after a few hours Photoshop just takes over more and more of the system memory until it's all used up. It used to not cause problems, but now, especially the last few months I've been having to close the program, then end the photoshop.exe file in the task manager daily to clear the memory. Now it's getting to the point where I have to do it 2 or 3 times a day to keep my system from halting. It doesn't seem to matter how I set the memory usage of the program it just eventually takes up the rest of the free memory (16gb of it) over time. It feels like a memory leak. It's getting frustrating, and slowing me down at work. I see on the forum that it's a common issue. From my experience over the years Photoshop always hogs up the memory over time, would be nice to get this fixed.
We check Photoshop pretty closely for leaks, and fix them.
Photoshop should only allocate memory up to the limit you set in Preferences.
But bugs in drivers, the OS, or third party plugins can leak memory.
No, leaks in Photoshop are not a common issue. Misunderstandings of memory management, or the aforementioned third party issues are common.
Similar Messages
-
Logic Pro 9 is unstable on my system and just keeps getting worse. Any ideas?
Hello all, so, I've had a Mac Pro, Quad-Core 2.93 GHz Intel Xeon, 16 GB RAM, Mac Pro running Snow Leopard for about 3 years now. I use Logic Pro 9 (Academic Version) and it is really, really unstable. It seems to go through periods of getting worse, but lately it's been unbearable. I am a professional and I find it hard to believe that this software is allowed to have the word "Pro" in the name if it's this unstable for everyone. But, it seems that only some people have the issues I have. Off the top of my head, a few of the main issues are: CPU spiking like crazy (when the Activity Monitor says very little usage by Logic), I know some of the workarounds like making more auxes and splitting up the load, but this is ridiculous. I shouldn't have to work around a professional piece of software just to use it. Sometimes the CPU spikes with one instrument or one audio channel and nothing going on. It's really messed up.Then there's the memory errors when Logic is only using 1GB or RAM, IF THAT. I don't understand this at all, it also can happen in a fully loaded session or with barely anything going on. Then there are the random crashes that make no sense. There's also the part where it does not agree with many LEGIT-OWNED plugins, like Refx Nexus, XFER Nerve, most of the UAD plugins and many more. There's literally a TON more bugs, but these are the big and obvious ones that ruin my workflow. I have not been able to find a real fix for this, from deleting the preferences to reinstalling. I really don't understand it and Logic seems to work much better for other people I know. It also runs much smoother on my really crappy, old laptop. There's nothing wrong with the Mac Pro (other than it's probably self destructing like we all know Apple products do, but this has been a problem since the day I purchased it), it passes all tests and runs perfectly with any other software - from audio/video editing (Cubase, Ableton, Pro Tools, Final Cut, etc. all run like a dream) to video games. So, I really am fed up with this because I've been using Logic for so long that I really don't want to switch to a new DAW. That would slow down my workflow even more than Logic's crashes already do. Someone please help me, if you can.
Here's my latest crash report:
Process:
Logic Pro [844]
Path:
/Applications/Logic Pro.app/Contents/MacOS/Logic Pro
Identifier:
com.apple.logic.pro
Version:
9.1.8 (1700.67)
Build Info:
Logic-17006700~1
Code Type:
X86 (Native)
Parent Process: launchd [144]
Date/Time:
2012-12-21 13:10:49.982 -0800
OS Version:
Mac OS X 10.6.8 (10K549)
Report Version: 6
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Crashed Thread: 8
Application Specific Information:
abort() called
Thread 0: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1 libSystem.B.dylib
0x94c2a267 mach_msg + 68
2 com.apple.CoreFoundation
0x9a9622df __CFRunLoopRun + 2079
3 com.apple.CoreFoundation
0x9a9613c4 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation
0x9a9611f1 CFRunLoopRunInMode + 97
5 com.apple.HIToolbox
0x959cae04 RunCurrentEventLoopInMode + 392
6 com.apple.HIToolbox
0x959cabb9 ReceiveNextEventCommon + 354
7 com.apple.HIToolbox
0x959caa3e BlockUntilNextEventMatchingListInMode + 81
8 com.apple.AppKit
0x950f9595 _DPSNextEvent + 847
9 com.apple.AppKit
0x950f8dd6 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 156
10 com.apple.AppKit
0x950bb1f3 -[NSApplication run] + 821
11 com.apple.prokit
0x00fd4446 NSProApplicationMain + 326
12 com.apple.logic.pro
0x0002bad5 DummyConnection::DummyConnection() + 193
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib
0x94c50382 kevent + 10
1 libSystem.B.dylib
0x94c50a9c _dispatch_mgr_invoke + 215
2 libSystem.B.dylib
0x94c4ff59 _dispatch_queue_invoke + 163
3 libSystem.B.dylib
0x94c4fcfe _dispatch_worker_thread2 + 240
4 libSystem.B.dylib
0x94c4f781 _pthread_wqthread + 390
5 libSystem.B.dylib
0x94c4f5c6 start_wqthread + 30
Thread 2:
0 libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1 libSystem.B.dylib
0x94c2a267 mach_msg + 68
2 com.apple.CoreFoundation
0x9a9622df __CFRunLoopRun + 2079
3 com.apple.CoreFoundation
0x9a9613c4 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation
0x9a9611f1 CFRunLoopRunInMode + 97
5 com.apple.Foundation
0x94e20224 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 329
6 com.apple.Foundation
0x94de74c4 -[NSThread main] + 45
7 com.apple.Foundation
0x94de7474 __NSThread__main__ + 1499
8 libSystem.B.dylib
0x94c57259 _pthread_start + 345
9 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 3: com.apple.CFSocket.private
0 libSystem.B.dylib
0x94c48ac6 select$DARWIN_EXTSN + 10
1 com.apple.CoreFoundation
0x9a9a1c53 __CFSocketManager + 1091
2 libSystem.B.dylib
0x94c57259 _pthread_start + 345
3 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 4:
0 libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1 libSystem.B.dylib
0x94c2a267 mach_msg + 68
2 com.apple.CoreFoundation
0x9a9622df __CFRunLoopRun + 2079
3 com.apple.CoreFoundation
0x9a9613c4 CFRunLoopRunSpecific + 452
4 com.apple.CoreFoundation
0x9a967304 CFRunLoopRun + 84
5 com.apple.DVCPROHDMuxer
0x1c78b98f AVS::DestroyAVCDeviceController(AVS::AVCDeviceController*) + 317
6 libSystem.B.dylib
0x94c57259 _pthread_start + 345
7 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 5:
0 libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1 libSystem.B.dylib
0x94c2a267 mach_msg + 68
2 ....audio_hijack_server.hermes
0x02ea39b2 ah_serv_loop + 132
3 libSystem.B.dylib
0x94c57259 _pthread_start + 345
4 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 6:
0 libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1 libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2 libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.music.apps.MAFiles
0x02a53838 ResolveFile + 54808
4 com.apple.music.apps.MAFiles
0x02a53901 ResolveFile + 55009
5 libSystem.B.dylib
0x94c57259 _pthread_start + 345
6 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 7:
0 libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1 libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2 libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3 com.apple.music.apps.MAFiles
0x02a53838 ResolveFile + 54808
4 com.apple.music.apps.MAFiles
0x02a53901 ResolveFile + 55009
5 libSystem.B.dylib
0x94c57259 _pthread_start + 345
6 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 8 Crashed:
0 libSystem.B.dylib
0x94c970ee __semwait_signal_nocancel + 10
1 libSystem.B.dylib
0x94c96fd2 nanosleep$NOCANCEL$UNIX2003 + 166
2 libSystem.B.dylib
0x94d11fb2 usleep$NOCANCEL$UNIX2003 + 61
3 libSystem.B.dylib
0x94d33685 __abort + 136
4 libSystem.B.dylib
0x94d336f5 abort_report_np + 0
5 com.apple.logic.pro
0x003e6729 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 3842985
6 libSystem.B.dylib
0x94c9005b _sigtramp + 43
7 ???
0x0000000b 0 + 11
Thread 9:
0 libSystem.B.dylib
0x94c29c0e mach_wait_until + 10
1 ...ple.CoreServices.CarbonCore
0x9409d7f0 MPDelayUntil + 43
2 ...ple.CoreServices.CarbonCore
0x940ad226 Delay + 107
3 ...opellerheads.rewire.library
0x50d0e654 RWIsReWireMixerAppRunningImp + 30420
4 ...opellerheads.rewire.library
0x50d1d228 RWIsReWireMixerAppRunningImp + 90792
5 libSystem.B.dylib
0x94c57259 _pthread_start + 345
6 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 10:
0 libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1 com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2 com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3 com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 11:
0 libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1 com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2 com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3 com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 12:
0 libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1 com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2 com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3 com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 13:
0 libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1 com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2 com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3 com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 14:
0 libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1 com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2 com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3 com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 15:
0 libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1 com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2 com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3 com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 16:
0 libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1 com.ableton.live-engine
0x50d85652 0x50d7a000 + 46674
2 com.ableton.live-engine
0x50da944e 0x50d7a000 + 193614
3 com.ableton.live-engine
0x50d83737 0x50d7a000 + 38711
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 17:
0 libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1 libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2 libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3 ...le.music.apps.MAAudioEngine
0x02b09f7c MD::CallProcessThread1(void*) + 108
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 18:
0 libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1 libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2 libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3 ...le.music.apps.MAAudioEngine
0x02b09cfc MD::CallProcessThread2(void*) + 124
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 19:
0 libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1 libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2 libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3 ...le.music.apps.MAAudioEngine
0x02b09a6c MD::CallProcessThread3(void*) + 124
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 20:
0 libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1 libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2 libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3 ...le.music.apps.MAAudioEngine
0x02b097dc MD::CallProcessThread4(void*) + 124
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 21:
0 libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1 libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2 libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3 ...le.music.apps.MAAudioEngine
0x02b0954c MD::CallProcessThread5(void*) + 124
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 22:
0 libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1 libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2 libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3 ...le.music.apps.MAAudioEngine
0x02b092bc MD::CallProcessThread6(void*) + 124
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 23:
0 libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1 libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2 libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3 ...le.music.apps.MAAudioEngine
0x02b0902c MD::CallProcessThread7(void*) + 124
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 24:
0 libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1 libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2 libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3 ...le.music.apps.MAAudioEngine
0x02b07bac MD::CallProcessThread15(void*) + 124
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 25:
0 libSystem.B.dylib
0x94c57aa2 __semwait_signal + 10
1 libSystem.B.dylib
0x94c5775e _pthread_cond_wait + 1191
2 libSystem.B.dylib
0x94c593f8 pthread_cond_wait$UNIX2003 + 73
3 ...le.music.apps.MAAudioEngine
0x02b273a9 MDFileIOThread_IsBusy + 3593
4 libSystem.B.dylib
0x94c57259 _pthread_start + 345
5 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 26:
0 libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1 libSystem.B.dylib
0x94c2a267 mach_msg + 68
2 com.apple.audio.midi.CoreMIDI
0x0139a0c1 XServerMachPort::ReceiveMessage(int&, void*, int&) + 155
3 com.apple.audio.midi.CoreMIDI
0x013b897a MIDIProcess::RunMIDIInThread() + 150
4 com.apple.audio.midi.CoreMIDI
0x0139b2d9 XThread::RunHelper(void*) + 17
5 com.apple.audio.midi.CoreMIDI
0x0139aca6 CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib
0x94c57259 _pthread_start + 345
7 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 27:
0 libSystem.B.dylib
0x94c29b5a semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib
0x94c576e1 _pthread_cond_wait + 1066
2 libSystem.B.dylib
0x94c865a8 pthread_cond_timedwait_relative_np + 47
3 ...ple.CoreServices.CarbonCore
0x94019b90 TSWaitOnConditionTimedRelative + 242
4 ...ple.CoreServices.CarbonCore
0x940198ce TSWaitOnSemaphoreCommon + 511
5 ...ple.CoreServices.CarbonCore
0x9403db8b TimerThread + 97
6 libSystem.B.dylib
0x94c57259 _pthread_start + 345
7 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 28:
0 libSystem.B.dylib
0x94c48ac6 select$DARWIN_EXTSN + 10
1 com.apple.logic.pro
0x0096fc07 void UnitTest::CheckEqual<ScTypeSetter::tVerticalAlignment, ScTypeSetter::tVerticalAlignment>(UnitTest::TestResults&, ScTypeSetter::tVerticalAlignment, ScTypeSetter::tVerticalAlignment, UnitTest::TestDetails const&) + 375367
2 com.apple.logic.pro
0x005b1d84 std::ostream& TraceOutContainer<CEvs>(std::ostream&, CEvs, char const*, int) + 5724676
3 libSystem.B.dylib
0x94c57259 _pthread_start + 345
4 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 29:
0 libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1 ...ery 3.MusicDevice.component
0x5c4876be BEngine::SetEngineParThreadProc() + 62
2 ...ery 3.MusicDevice.component
0x5cdc2d68 NI::GP::Thread::execute(void*) + 72
3 libSystem.B.dylib
0x94c57259 _pthread_start + 345
4 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 30:
0 libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1 ...ery 3.MusicDevice.component
0x5c4d8336 BStreamingEngine::run() + 230
2 ...ery 3.MusicDevice.component
0x5cdc2d68 NI::GP::Thread::execute(void*) + 72
3 libSystem.B.dylib
0x94c57259 _pthread_start + 345
4 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 31:
0 libSystem.B.dylib
0x94c29b36 semaphore_wait_trap + 10
1 ...ery 3.MusicDevice.component
0x5c82c1ea BBackgroundLoader::run() + 74
2 ...ery 3.MusicDevice.component
0x5cdc2d68 NI::GP::Thread::execute(void*) + 72
3 libSystem.B.dylib
0x94c57259 _pthread_start + 345
4 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 32:
0 libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1 libSystem.B.dylib
0x94c2a267 mach_msg + 68
2 ...tope.audioplugins.AU.Trash2
0x667bd57a catch_exception_raise + 250
3 libSystem.B.dylib
0x94c57259 _pthread_start + 345
4 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 33:
0 libSystem.B.dylib
0x94c29b5a semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib
0x94c576e1 _pthread_cond_wait + 1066
2 libSystem.B.dylib
0x94c865a8 pthread_cond_timedwait_relative_np + 47
3 ...ple.CoreServices.CarbonCore
0x94019b90 TSWaitOnConditionTimedRelative + 242
4 ...ple.CoreServices.CarbonCore
0x940198ce TSWaitOnSemaphoreCommon + 511
5 ...ickTimeComponents.component
0x920ee8b5 ReadSchedulerThreadEntryPoint + 4698
6 libSystem.B.dylib
0x94c57259 _pthread_start + 345
7 libSystem.B.dylib
0x94c570de thread_start + 34
Thread 34:
0 libSystem.B.dylib
0x94c4f412 __workq_kernreturn + 10
1 libSystem.B.dylib
0x94c4f9a8 _pthread_wqthread + 941
2 libSystem.B.dylib
0x94c4f5c6 start_wqthread + 30
Thread 8 crashed with X86 Thread State (32-bit):
eax: 0x0000003c ebx: 0x94c96f39 ecx: 0xb052211c edx: 0x94c970ee
edi: 0x00000000 esi: 0xb0522178 ebp: 0xb0522158 esp: 0xb052211c
ss: 0x0000001f efl: 0x00000247 eip: 0x94c970ee cs: 0x00000007
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x62e4d000
Binary Images:
0x1000 - 0xbeafff com.apple.logic.pro 9.1.8 (1700.67) <94981650-518B-2288-F07D-F28F27103100> /Applications/Logic Pro.app/Contents/MacOS/Logic Pro
0xe8f000 - 0xeadfef com.apple.XSKey 1.0.0 (52) <71B94F53-15DB-9012-91F2-211F7C2CD790> /Library/Frameworks/XSKey.framework/Versions/A/XSKey
0xebc000 - 0xeeffe7 com.apple.music.apps.MAAudioUnitSupport 9.1.8 (233.53) <E8A99468-7726-CCFE-8D26-DDBC9D5E1AC3> /Applications/Logic Pro.app/Contents/Frameworks/MAAudioUnitSupport.framework/Versions/A/MAAudioUnit Support
0xefc000 - 0xf2dff3 com.apple.musicaudiodataservices 1.1 (251.4) <0265F317-13AB-6CF1-A171-7D5853442E75> /Applications/Logic Pro.app/Contents/Frameworks/MAAssetSharing.framework/Versions/A/MAAssetSharing
0xf3c000 - 0xf9aff3 com.apple.music.apps.MALoopManagement 9.1.8 (219.66) <0075F2D0-7A48-A362-2D49-4FECA5E9DF8E> /Applications/Logic Pro.app/Contents/Frameworks/MALoopManagement.framework/Versions/A/MALoopManagem ent
0xfb0000 - 0x11e8fff com.apple.prokit 7.0 (1331) <B3DAD7D3-5D87-CBA6-D4C7-74E96928BA77> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
0x12f0000 - 0x136afff com.apple.music.apps.MACore 9.1.8 (477.58) <8025A098-49AF-AFF3-4B8E-4C30C06123FF> /Applications/Logic Pro.app/Contents/Frameworks/MACore.framework/Versions/A/MACore
0x138a000 - 0x13d6ffb com.apple.audio.midi.CoreMIDI 1.7.1 (42) <FB4D4B64-6ABB-679E-3AA8-21DE9062B4C1> /System/Library/Frameworks/CoreMIDI.framework/Versions/A/CoreMIDI
0x13fb000 - 0x1451ff7 com.apple.music.apps.MAHarmony 9.1.8 (199.72) <448DD823-9EF9-8F88-FFF1-2C7EBD9647B1> /Applications/Logic Pro.app/Contents/Frameworks/MAHarmony.framework/Versions/A/MAHarmony
0x1468000 - 0x1882feb com.apple.music.apps.MAPlugInGUI 9.1.8 (424.79) <9EBA5689-ECE1-E66B-6A0D-DE3F9C7867E4> /Applications/Logic Pro.app/Contents/Frameworks/MAPlugInGUI.framework/Versions/A/MAPlugInGUI
0x1aa0000 - 0x1b82feb com.apple.music.apps.OMF 9.1.8 (109.7) <65E724BA-01DB-68E1-9661-E9B96DA76300> /Applications/Logic Pro.app/Contents/Frameworks/OMF.framework/Versions/A/OMF
0x1b96000 - 0x21e7fe3 com.apple.music.apps.MADSP 9.1.8 (588.98) <93C7306D-07A8-DED0-C59B-B333A475E6DB> /Applications/Logic Pro.app/Contents/Frameworks/MADSP.framework/Versions/A/MADSP
0x28cc000 - 0x28edff7 com.apple.music.apps.LogicFileBrowser 9.1.8 (1700.67) <DB122163-0F15-2E23-16AE-3DCAE41D1870> /Applications/Logic Pro.app/Contents/Frameworks/LogicFileBrowser.framework/Versions/A/LogicFileBrow ser
0x28f6000 - 0x296fff7 com.apple.music.apps.LogicLoopBrowser 9.1.8 (1700.67) <AFAED0FE-A81D-8204-3633-B6DEF6455B8A> /Applications/Logic Pro.app/Contents/Frameworks/LogicLoopBrowser.framework/Versions/A/LogicLoopBrow ser
0x2983000 - 0x29a4ff7 com.apple.music.apps.MAApogeeSupport 9.1.8 (313.26) <B23133C5-90D1-4B22-7421-375F9374C9EA> /Applications/Logic Pro.app/Contents/Frameworks/MAApogeeSupport.framework/Versions/A/MAApogeeSuppor t
0x29a9000 - 0x29aeff7 com.apple.music.apps.MAResources 9.1.8 (212.66) <EEB8FFEB-61A3-69E2-D6AC-AB5C7B8337E2> /Applications/Logic Pro.app/Contents/Frameworks/MAResources.framework/Versions/A/MAResources
0x29b2000 - 0x29dbfe3 com.apple.audio.CoreAudioKit 1.6.1 (1.6.1) <7FFBD485-5251-776A-CC44-4470DD84112B> /System/Library/Frameworks/CoreAudioKit.framework/Versions/A/CoreAudioKit
0x29ec000 - 0x29fcff7 com.apple.AERegistration 1.2 (401) <09312188-9C9E-E1A8-0F53-B8F34AA7F76A> /Applications/Logic Pro.app/Contents/Frameworks/AERegistration.framework/Versions/A/AERegistration
0x2a10000 - 0x2a1cff3 com.apple.music.apps.MAUnitTest 9.1.8 (97.27) <1B77FF0E-ABF2-ABC4-5D7E-638D56A24C69> /Applications/Logic Pro.app/Contents/Frameworks/MAUnitTest.framework/Versions/A/MAUnitTest
0x2a24000 - 0x2adafff com.apple.music.apps.MAFiles 9.1.8 (144.87) <23D65681-872A-1E6B-91E5-B93643CCB375> /Applications/Logic Pro.app/Contents/Frameworks/MAFiles.framework/Versions/A/MAFiles
0x2af3000 - 0x2b6bfe3 com.apple.music.apps.MAAudioEngine 9.1.8 (158.42) <6ADDBB03-0D41-4473-AFC3-385EFA574B87> /Applications/Logic Pro.app/Contents/Frameworks/MAAudioEngine.framework/Versions/A/MAAudioEngine
0x2bd2000 - 0x2bddff7 com.apple.music.apps.MAToolKit 9.1.8 (359.28) <FEEF1A62-CB87-8FD2-F724-0BB660D63146> /Applications/Logic Pro.app/Contents/Frameworks/MAToolKit.framework/Versions/A/MAToolKit
0x2be1000 - 0x2bf5ff7 com.apple.music.apps.MAVideo 9.1.8 (12.70) <FAFE71CD-0FC8-69F4-6FEE-9E873D9F5DD5> /Applications/Logic Pro.app/Contents/Frameworks/MAVideo.framework/Versions/A/MAVideo
0x2c08000 - 0x2cbdfe7 libcrypto.0.9.7.dylib 0.9.7 (compatibility 0.9.7) <AACC86C0-86B4-B1A7-003F-2A0AF68973A2> /usr/lib/libcrypto.0.9.7.dylib
0x2d03000 - 0x2d9fffc com.apple.MobileMe 9 (1.01) <EBADB981-9ED6-82B0-810F-F1CB05CB5A17> /Applications/Logic Pro.app/Contents/Frameworks/MobileMe.framework/Versions/A/MobileMe
0x2e59000 - 0x2e8eff7 com.apple.prokit.SnowLeopardPanels 7.0 (1331) <BB481932-46DC-8FB1-97CB-67C484A6CBF2> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/Resources/SnowLeo pardPanels.bundle/Contents/MacOS/SnowLeopardPanels
0x2e9f000 - 0x2eabff7 +com.rogueamoeba.audio_hijack_server.hermes 2.2.5 (2.2.5) <CD6C7A74-BA03-F3A7-0D1E-460E6A043024> /usr/local/hermes/modules/Instant Hijack Server.hermesmodule/Contents/MacOS/Instant Hijack Server
0x3f9a000 - 0x3f9eff3 com.apple.audio.AudioIPCPlugIn 1.1.6 (1.1.6) <E9CB576C-283B-1DB2-0C69-E7C914BD7922> /System/Library/Extensions/AudioIPCDriver.kext/Contents/Resources/AudioIPCPlugI n.bundle/Contents/MacOS/AudioIPCPlugIn
0x3fa3000 - 0x3fa9ff7 com.apple.audio.AppleHDAHALPlugIn 2.0.5 (2.0.5f14) <38E3C1A4-84E4-C105-B55F-8FC4C154036D> /System/Library/Extensions/AppleHDA.kext/Contents/PlugIns/AppleHDAHALPlugIn.bun dle/Contents/MacOS/AppleHDAHALPlugIn
0x3fae000 - 0x3fccfff +de.access-music.virus_ti.util.hal ??? (2.1.0) <DBC06F6E-0D35-0700-D515-CD0BAC2B6002> /Library/Audio/Plug-Ins/HAL/de.access-music.virus_ti.plugin/Contents/MacOS/de.a ccess-music.virus_ti
0x1b0b3000 - 0x1b0ddff7 +com.grame.JackRouter JackRouter (0.9.5) <13AB2581-FFAF-AC76-FB8F-D1C8779C94AF> /Library/Audio/Plug-Ins/HAL/JackRouter.plugin/Contents/MacOS/JackRouter
0x1c4a2000 - 0x1c4cbfff +Jackmp ??? (???) <0B8EB3A5-FD59-2D99-839C-2D4A9A59AA94> /Library/Frameworks/Jackmp.framework/Versions/A/Jackmp
0x1c700000 - 0x1c755fe2 com.apple.DVCPROHDAudio 1.3.2 (1.3.2) <2E0A9883-4EA5-706F-78F6-4C1F105A4D30> /Library/Audio/Plug-Ins/HAL/DVCPROHDAudio.plugin/Contents/MacOS/DVCPROHDAudio
0x1c774000 - 0x1c7d9fe0 com.apple.DVCPROHDMuxer 1.3.2 (1.3.2) <483DD62C-46C4-36AA-6A1C-2DEA6F062863> /Library/QuickTime/DVCPROHDMuxer.component/Contents/MacOS/DVCPROHDMuxer
0x4577c000 - 0x45782ff7 +com.prosofteng.soundbunny.plugin 1.0.2 (898) <26781624-AE2F-3FCB-A11A-FC51C889E7A8> /Library/Audio/Plug-Ins/HAL/SoundBunny.plugin/Contents/MacOS/SoundBunny
0x457af000 - 0x457b7ff7 com.apple.proapps.mrcheckpro 1.4 (397) <25DBA6AA-139D-EFAC-1BF8-5D29A3DFA497> /Applications/Logic Pro.app/Contents/Resources/MRCheckPro.bundle/Contents/MacOS/MRCheckPro
0x457f2000 - 0x457f4ff3 com.apple.music.apps.anvil.resources 9.1.8 (280.4) <AFA90574-C724-880F-9C99-52E064F5B3E8> /Applications/Logic Pro.app/Contents/PlugIns/anvil.res/Contents/MacOS/anvil
0x457f8000 - 0x457faff3 com.apple.music.apps.common.resources 9.1.8 (280.4) <579C1A3C-3636-9A69-185E-819DC01E1083> /Applications/Logic Pro.app/Contents/PlugIns/common.res/Contents/MacOS/common
0x460e9000 - 0x460eafef com.apple.music.apps.midi.device.plugin.FaderPort 9.0.0 (173) <00C2D825-856B-A371-4684-6FCD1FDECC21> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/FaderPort.bundle/Contents/MacOS/FaderPort
0x46161000 - 0x46163ff3 com.apple.music.apps.ebp.resources 9.1.8 (280.4) <95A85BC0-7D35-B965-2026-1A44E96DC653> /Applications/Logic Pro.app/Contents/PlugIns/ebp.res/Contents/MacOS/ebp
0x46e3b000 - 0x46fb4ff7 GLEngine ??? (???) <76C922AA-A4A7-2835-537B-17F316AD95F6> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
0x46fe6000 - 0x473f9fef com.apple.ATIRadeonX2000GLDriver 1.6.36 (6.3.6) <257CAA1D-6573-2932-E344-E96F6C9CDA84> /System/Library/Extensions/ATIRadeonX2000GLDriver.bundle/Contents/MacOS/ATIRade onX2000GLDriver
0x4742b000 - 0x4744ffe7 GLRendererFloat ??? (???) <F19DDBE8-1DF6-6618-F554-0E81ED85CE67> /System/Library/Frameworks/OpenGL.framework/Resources/GLRendererFloat.bundle/GL RendererFloat
0x47705000 - 0x47708fe7 com.apple.MIDIDevicePlugIn.Axiom Pro 1.0.1 (70) <B8D61742-3ADC-1EDB-4D0B-344E0CD0D33A> /Library/Application Support/MIDI Device Plug-ins/Axiom Pro.bundle/Contents/MacOS/Axiom Pro
0x47840000 - 0x47842ff3 com.apple.music.apps.efx.resources 9.1.8 (280.4) <FB5BBFF8-DF5E-32BC-4F4C-C5A2DA3FB1A6> /Applications/Logic Pro.app/Contents/PlugIns/efx.res/Contents/MacOS/efx
0x47846000 - 0x47848ff3 com.apple.music.apps.egt.resources 9.1.8 (280.4) <11B09E42-9FC4-A372-8738-057CAB888671> /Applications/Logic Pro.app/Contents/PlugIns/egt.res/Contents/MacOS/egt
0x4784c000 - 0x4784eff3 com.apple.music.apps.emx.resources 9.1.8 (280.4) <A3C65CFE-2BBF-DB8C-D4C8-5950284E44CF> /Applications/Logic Pro.app/Contents/PlugIns/emx.res/Contents/MacOS/emx
0x47852000 - 0x47854ff3 com.apple.music.apps.es1.resources 9.1.8 (280.4) <DB1CD8D6-2C8F-32EE-266B-A28C00B2DFB7> /Applications/Logic Pro.app/Contents/PlugIns/es1.res/Contents/MacOS/es1
0x47858000 - 0x4785aff3 com.apple.music.apps.es2.resources 9.1.8 (280.4) <7E91D13E-87CF-0B50-14A7-9B7A1E3D345C> /Applications/Logic Pro.app/Contents/PlugIns/es2.res/Contents/MacOS/es2
0x4785e000 - 0x47860ff3 com.apple.music.apps.esp.resources 9.1.8 (280.4) <C5284B25-3250-2201-D4EE-523FE37B9E6B> /Applications/Logic Pro.app/Contents/PlugIns/esp.res/Contents/MacOS/esp
0x47864000 - 0x47866ff3 com.apple.music.apps.evb3.resources 9.1.8 (280.4) <068F656F-6CA6-37E9-96F5-1F8E10546A43> /Applications/Logic Pro.app/Contents/PlugIns/evb3.res/Contents/MacOS/evb3
0x4786a000 - 0x4786cff3 com.apple.music.apps.evd6.resources 9.1.8 (280.4) <B15F044D-60BB-FD36-6A49-685C7DCA7FB4> /Applications/Logic Pro.app/Contents/PlugIns/evd6.res/Contents/MacOS/evd6
0x47870000 - 0x47872ff3 com.apple.music.apps.evoc.resources 9.1.8 (280.4) <E361301A-56EF-FF6C-67E5-AC3D9F15E190> /Applications/Logic Pro.app/Contents/PlugIns/evoc.res/Contents/MacOS/evoc
0x47876000 - 0x47878ff3 com.apple.music.apps.evp88.resources 9.1.8 (280.4) <6E1152B4-E9F3-3F6E-7246-A10456888210> /Applications/Logic Pro.app/Contents/PlugIns/evp88.res/Contents/MacOS/evp88
0x4787c000 - 0x4787eff3 com.apple.music.apps.exs24.resources 9.1.8 (280.4) <DC363BF8-D15A-6049-F148-7804EADF7539> /Applications/Logic Pro.app/Contents/PlugIns/exs24.res/Contents/MacOS/exs24
0x47882000 - 0x47884ff3 com.apple.music.apps.guitaramp.resources 9.1.8 (280.4) <27F67C33-C9BA-D9CE-DC89-A33A7F674F2C> /Applications/Logic Pro.app/Contents/PlugIns/guitaramp.res/Contents/MacOS/guitaramp
0x47888000 - 0x4788aff3 com.apple.music.apps.guitarcontrols.resources 9.1.8 (280.4) <DAD1836E-F4DD-EB95-2F48-A8AF8552D087> /Applications/Logic Pro.app/Contents/PlugIns/guitarcontrols.res/Contents/MacOS/guitarcontrols
0x4788e000 - 0x47890ff3 com.apple.music.apps.mutapdel.resources 9.1.8 (280.4) <555A65F0-E35D-0F5F-76EC-7C83D06C68AB> /Applications/Logic Pro.app/Contents/PlugIns/mutapdel.res/Contents/MacOS/mutapdel
0x47894000 - 0x47896ff3 com.apple.music.apps.pedalboard.resources 9.1.8 (280.4) <9923C7F7-E681-EE64-06CE-A0C8AABF7E65> /Applications/Logic Pro.app/Contents/PlugIns/pedalboard.res/Contents/MacOS/pedalboard
0x4789a000 - 0x4789cff3 com.apple.music.apps.revolver.resources 9.1.8 (280.4) <9AE36A7E-5D8F-681C-ABFD-4BCFE5048FF4> /Applications/Logic Pro.app/Contents/PlugIns/revolver.res/Contents/MacOS/revolver
0x478a0000 - 0x478a2ff3 com.apple.music.apps.sphere.resources 9.1.8 (280.4) <FF758F38-414E-5BFD-97CF-778DF8F52EAE> /Applications/Logic Pro.app/Contents/PlugIns/sphere.res/Contents/MacOS/sphere
0x478f1000 - 0x478f6ffb +com.WavesAudio.WavesReWireDevice.8.0.0 8.0.0 (8.0.0.10) <DBA04305-F027-23DF-A1EC-4D112843C03F> /Library/Application Support/Propellerhead Software/ReWire/WavesReWireDevice.bundle/Contents/MacOS/WavesReWireDevice
0x48ff8000 - 0x48ffaff3 com.apple.music.apps.midi.device.plugin.GiO 9.1.8 (198.73) <E2634721-B8D4-03CE-43B5-7C64EED8BFD3> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/GiO.bundle/Contents/MacOS/GiO
0x50ce5000 - 0x50d6cffb +se.propellerheads.rewire.library 1.8.1 build 124 (1.8.1) <79A1E240-4153-9288-475D-697D84C94343> /Library/Application Support/Propellerhead Software/ReWire/ReWire.bundle/Contents/MacOS/ReWire
0x50d7a000 - 0x5122dff7 +com.ableton.live-engine 8.2 (8.2) <DCF40AE3-0F7F-41FC-2B5E-EA8673EFBE99> /Applications/Live 8.2 OS X/Live.app/Contents/Resources/Ableton Live Engine.bundle/Contents/MacOS/Ableton Live Engine
0x5193c000 - 0x51947ff7 com.apple.DVCPROHDVideoOutput 1.3.2 (1.3.2) <8D8A75CC-6204-1187-04CC-B3323E76DCF9> /Library/QuickTime/DVCPROHDVideoOutput.component/Contents/MacOS/DVCPROHDVideoOu tput
0x519c9000 - 0x51d33fef +se.propellerheads.reason.engine 5.0 (5.0) <D7415C86-0873-62CC-358B-B205326D790D> /Applications/Reason/Reason.app/Contents/PlugIns/Reason Engine.plugin/Contents/MacOS/Reason Engine
0x51ffc000 - 0x5205bfe1 +se.propellerheads.rewire.library 1.7 (1.7) /Users/brandonscrushy/Library/Application Support/Propellerhead Software/ReWire/ReWire.bundle/Contents/MacOS/ReWire
0x5207a000 - 0x52095ff7 com.apple.OpenTransport 10.6.0 (10.6.0) <ECA6FEC6-5ECD-51BA-162F-CFC43899196A> /System/Library/PrivateFrameworks/OpenTransport.framework/OpenTransport
0x52328000 - 0x52369fe3 com.apple.audio.SoundManager.Components 3.9.4 (3.9.4) <AD66647C-03A9-EBAF-6FFC-E5A631F4D6BE> /System/Library/Components/SoundManagerComponents.component/Contents/MacOS/Soun dManagerComponents
0x52370000 - 0x523acfe3 com.apple.QuickTimeFireWireDV.component 7.6.6 (1791) <50D03C98-3DF6-BF7E-6440-7E3AB5A78CBE> /System/Library/QuickTime/QuickTimeFireWireDV.component/Contents/MacOS/QuickTim eFireWireDV
0x523b8000 - 0x52475fe2 com.apple.DesktopVideoOut 1.2.7 (1.2.7) <7959538F-2A96-F2BB-EEC3-0718A326C152> /Library/QuickTime/DesktopVideoOut.component/Contents/MacOS/DesktopVideoOut
0x52494000 - 0x5249eff7 com.apple.IOFWDVComponents 1.9.9 (1.9.9) <5B4E7BD7-EF5A-2F5C-DF8E-3D4A7B59F779> /System/Library/Components/IOFWDVComponents.component/Contents/MacOS/IOFWDVComp onents
0x524e8000 - 0x524eafe3 com.apple.music.apps.midi.device.plugin.CS-32 9.1.8 (198.73) <EA9B28F8-4962-8224-D724-7ECA99692774> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/CS-32.bundle/Contents/MacOS/CS-32
0x524f2000 - 0x524f5feb com.apple.music.apps.midi.device.plugin.FW-1884 9.1.8 (198.73) <9A51CFA4-711B-1164-6874-80FBF4411A3B> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/FW-1884.bundle/Contents/MacOS/FW-1884
0x52700000 - 0x52704ffb com.apple.music.apps.midi.device.plugin.HUI 9.1.8 (198.73) <838E7E91-15F9-779A-9F34-18003221C5CE> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/HUI.bundle/Contents/MacOS/HUI
0x52710000 - 0x52711fff com.apple.music.apps.midi.device.plugin.iControl 9.1.8 (198.73) <F67DC4BC-6556-6AB6-F5CA-C07F087EF639> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/iControl.bundle/Contents/MacOS/iControl
0x52717000 - 0x5271eff3 com.apple.music.apps.midi.device.plugin.Logic-Control 9.1.8 (198.73) <04DC4A0E-2FE2-BE3F-5F5C-686FB712D8F5> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/Logic Control.bundle/Contents/MacOS/Logic Control
0x5273b000 - 0x5273cfff com.apple.music.apps.midi.device.plugin.MCS3 9.1.8 (198.73) <FB25C00A-5481-F18F-21DB-53D28ADCC168> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/MCS3.bundle/Contents/MacOS/MCS3
0x52741000 - 0x52743ff7 com.apple.music.apps.midi.device.plugin.microKONTROL 9.1.8 (198.73) <48E33623-5220-448C-E0D5-6F53B79EC815> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/microKONTROL.bundle/Contents/MacOS/microKONTROL
0x5274a000 - 0x5274aff3 com.apple.music.apps.midi.device.plugin.Recording-Light 9.1.8 (198.73) <62130915-EEC9-7EE1-AFB9-737A32AA09AC> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/Recording Light.bundle/Contents/MacOS/Recording Light
0x5274f000 - 0x52752fff com.apple.music.apps.midi.device.plugin.TouchOSC 9.1.8 (198.73) <09337083-973D-480B-C17F-8F68AE3F2FA2> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/TouchOSC.bundle/Contents/MacOS/TouchOSC
0x5275b000 - 0x5275dff3 com.apple.music.apps.midi.device.plugin.TranzPort 9.1.8 (198.73) <26E0C91B-097C-E77A-5E34-6BD85A8BA365> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/TranzPort.bundle/Contents/MacOS/TranzPort
0x52762000 - 0x52764fe7 com.apple.music.apps.midi.device.plugin.US-2400 9.1.8 (198.73) <8D056088-15A4-9FE5-4DDD-14CA2AC746A4> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/US-2400.bundle/Contents/MacOS/US-2400
0x5276d000 - 0x5276effb com.apple.music.apps.midi.device.plugin.US-428 9.1.8 (198.73) <A9C8442B-C474-977F-B61C-4C35DF494201> /Applications/Logic Pro.app/Contents/MIDI Device Plug-ins/US-428.bundle/Contents/MacOS/US-428
0x527ef000 - 0x527f0ff7 com.apple.textencoding.unicode 2.3 (2.3) <78A61FD5-70EE-19EA-48D4-3481C640B70D> /System/Library/TextEncodings/Unicode Encodings.bundle/Contents/MacOS/Unicode Encodings
0x5332a000 - 0x5332affd +jp.Canon.DPPCMPlugIn ??? (1.0) /Library/Contextual Menu Items/dppCMPlugIn.plugin/Contents/MacOS/dppCMPlugIn
0x5b18a000 - 0x5b18aff7 libmx.A.dylib 315.0.0 (compatibility 1.0.0) <01401BF8-3FC7-19CF-ACCE-0F292BFD2F25> /usr/lib/libmx.A.dylib
0x5b3c9000 - 0x5b3cafff +com.symantec.NAVCMPlugIn 11.1 (102) /Library/Contextual Menu Items/NAVCMPlugIn.plugin/Contents/MacOS/NAVCMPlugIn
0x5b5ec000 - 0x5b606fff +AdobeBIB ??? (???) /Library/Contextual Menu Items/ADFSMenu.plugin/Contents/Frameworks/AdobeBIB.framework/Versions/A/AdobeBI B
0x5b611000 - 0x5b617ff7 +com.symantec.avscan.framework 1.0.2 (6) /Library/PrivateFrameworks/SymAVScan.framework/Versions/A/SymAVScan
0x5bab6000 - 0x5bac7fe7 com.apple.FCP Uncompressed 422.component 1.6.1 (1.6.1) <62C290FB-2735-60C4-CE88-7ECB0DE6EDB3> /Library/QuickTime/FCP Uncompressed 422.component/Contents/MacOS/FCP Uncompressed 422
0x5bb49000 - 0x5bb64fef com.apple.AppleIntermediateCodec 1.3.2 (153) <D42634C1-8BDA-31ED-5216-13CB19BA7D1B> /Library/QuickTime/AppleIntermediateCodec.component/Contents/MacOS/AppleInterme diateCodec
0x5bb6a000 - 0x5bb83fe7 com.apple.applepixletvideo 1.2.29 (1.2d29) <52810348-A138-D148-92E4-9E1D73EA18A0> /System/Library/QuickTime/ApplePixletVideo.component/Contents/MacOS/ApplePixlet Video
0x5bc19000 - 0x5bc2cfe3 com.apple.IMXCodec 1.4 (155) <B7A1514F-1A2B-EC3E-719D-B8BB25016A05> /Library/QuickTime/IMXCodec.component/Contents/MacOS/IMXCodec
0x5c2c3000 - 0x5d52bfe3 +Battery 3.MusicDevice.component 3.2.3. (R637) (3.2.3. (R637), Copyright © 2011 Native Instruments) <8263B199-AABD-2CA2-6BAB-1111FF6B9828> /Library/Audio/Plug-Ins/Components/Battery 3.component/Contents/MacOS/Battery 3
0x5dbd8000 - 0x5dc0cfff +se.propellerheads.rex.library 1.7.0 (1.7.0) <7180964B-2D1C-03CC-E266-51DE3EFBAFA6> /Library/Application Support/Native Instruments/Helper/REX Shared Library.bundle/Contents/MacOS/REX Shared Library
0x5dcab000 - 0x5e04fff7 +de.native-instruments.kconvert.macho.bundle 3.0.0.7 (3.0.0.7) <92504456-EF51-82A6-ABBE-0FA019B40B23> /Library/Application Support/Native Instruments/Battery 3/bconvert.bundle/Contents/MacOS/kconvert
0x5fb4f000 - 0x5fb86fe7 com.apple.DVCPROHDCodec 1.5 (237) <5BA42205-5AEE-73BB-A7DE-5417EF028D5B> /Library/QuickTime/DVCPROHDCodec.component/Contents/MacOS/DVCPROHDCodec
0x5fba7000 - 0x5fbc3ffb +com.symantec.sharedsettings.framework 1.3 (6) /Library/PrivateFrameworks/SymSharedSettings.framework/Versions/A/SymSharedSett ings
0x601d3000 - 0x6028afef +com.xfer.LFOTool 1.0 (1.0) <AD242775-C1D9-3F6E-AACF-598117B69C22> /Library/Audio/Plug-Ins/Components/LFOTool.component/Contents/MacOS/LFOTool
0x60e27000 - 0x61236fc3 +com.reFX.Nexus 2.4.2 (2.4.2) <CB29856E-0602-3904-A599-26FDDB615A26> /Library/Audio/Plug-Ins/Components/Nexus.component/Contents/MacOS/Nexus
0x61334000 - 0x613b0ff3 +com.eLicenser.POSAccess-DLL ??? (1.4.0.9) <9FEB2066-B500-305F-8C6C-182F3BD62666> /Library/Application Support/eLicenser/pos/Synsoacc.bundle/Contents/MacOS/Synsoacc
0x633b7000 - 0x633dbfe3 +com.symantec.symbase 2.3 (15) <2FD986B4-9D7B-8800-0DDA-0872E4FD997F> /Library/PrivateFrameworks/SymBase.framework/Versions/B/SymBase
0x63f57000 - 0x64662fef +com.cytomic.theglue 1.0.15 (1.0.15) <3858820B-835B-6FDA-2E5D-EBE4241EF912> /Users/brandonscrushy/Library/Audio/Plug-Ins/Components/The Glue.component/Contents/MacOS/The Glue
0x64f33000 - 0x64f59ff7 +com.TailoredNoise.AU.SausageFattener 1.0 (1.0) <38AD3492-C3F8-3ED5-A625-95CCD38116E4> /Library/Audio/Plug-Ins/Components/SausageFattener.component/Contents/MacOS/Sau sageFattener
0x66000000 - 0x66199ff7 +com.wallanderinstruments.VST.SausageFattener ??? (2.32) <40C8BC6E-05FD-F722-A700-596499F82A71> /Library/Application Support/SausageFattener/Resource/SausageFattener.dat/Contents/MacOS/SausageFatt ener
0x66770000 - 0x667ebffb +com.izotope.audioplugins.AU.Trash2 2.0.0 (2.0.0b257) <ECBCABDA-2457-3058-A580-E2744D200565> /Library/Audio/Plug-Ins/Components/iZTrash2AUHook.component/Contents/MacOS/Plug inHooksAU
0x67a84000 - 0x684baffb +com.izotope.audioplugins.Trash2 2.0.0 (2.0.0b257) <88BA73FD-A36F-3344-8EAC-90E6C6D88DDE> /Library/Audio/Plug-Ins/Components/iZTrash2AUHook.component/Contents/Resources/ iZTrash2.bundle/Contents/MacOS/iZTrash2
0x6f9ce000 - 0x6fa0afc7 +com.adobe.vcmenu ??? (4.0.0.344) /Library/Contextual Menu Items/ADFSMenu.plugin/Contents/MacOS/ADFSMenu
0x6fa64000 - 0x6fa7cfe3 +com.symantec.internetSecurity.framework 1.3.2 (5) <0FF940EF-4FA3-C001-A7D1-976FE2351F54> /Library/PrivateFrameworks/SymInternetSecurity.framework/Versions/A/SymInternet Security
0x6fd40000 - 0x6fef6feb +com.fabfilter.Timeless.AU.2 2.13 (2.13) <141A5C98-C087-1463-2921-B7B695C0D35D> /Library/Audio/Plug-Ins/Components/FabFilter Timeless 2.component/Contents/MacOS/FabFilter Timeless 2
0x7083e000 - 0x7087efec +com.audiodamage.audiounit.DubStation_15 1.5.1 (1.5.1) <D2D31F5F-7C6E-2D59-A7B8-9753F0BD4D84> /Library/Audio/Plug-Ins/Components/DubStation_15.component/Contents/MacOS/DubSt ation_15
0x71232000 - 0x713dffeb +com.soundtoys.audiounit.EchoBoy 4.0.2 (4.0.2) <15B3A8F0-5DA7-8996-19B3-4B1D0CE6EC7D> /Library/Audio/Plug-Ins/Components/Echoboy.component/Contents/MacOS/EchoBoy
0x73c41000 - 0x74c2efe7 +com.voxengo.audio-plugins.audiounit.SPAN 2.4.1 (2.4.1) <B60A5232-CEEB-DF40-270E-5CEDCCD45704> /Library/Audio/Plug-Ins/Components/SPAN.component/Contents/MacOS/SPAN
0x76af0000 - 0x76b1cfe2 +com.symantec.daemon.framework 1.2.2 (7) <18F8E556-EA30-D193-69CB-4B0A60A5E821> /Library/PrivateFrameworks/SymDaemon.framework/Versions/A/SymDaemon
0x76d0f000 - 0x76d7cfe7 com.apple.AppleProResCodec 2.0 (224) <B7A79FF2-9C32-5554-A3C3-BE91F9B89419> /Library/QuickTime/AppleProResCodec.component/Contents/MacOS/AppleProResCodec
0x76dc9000 - 0x76e43fef com.apple.AppleVAH264HW.component 2.0 (1.0) <9F28FEE8-C61E-C474-4C4A-B4932DF28794> /System/Library/QuickTime/AppleVAH264HW.component/Contents/MacOS/AppleVAH264HW
0x76f06000 - 0x76fb5fe3 com.apple.AppleHDVCodec 1.6 (229) <C45D37E1-3CE0-1FBE-17DE-91D5B65FD940> /Library/QuickTime/AppleHDVCodec.component/Contents/MacOS/AppleHDVCodec
0x7f01a000 - 0x7f547ff7 +com.RPCX.SubBoomBass.component 1.1.0 (1.1.0) <62D227BF-1409-A527-ABEA-A4EF7B134BCD> /Library/Audio/Plug-Ins/Components/SubBoomBass.component/ContePancenter...
Yes... but I have come across some setups that came with a native SL (and even one Lion!) installation.. that somehow had a corrupted or older Prokit installed for some unknown reason... and given it's a quick fix to try.. I thought I'd mention it..
I frankly don't think it is entirely a Prokit issue itself, but it wouldn't do any harm to try and install v7 just in case it is part of the problem...
+1 on the UAD stuff....
Also, at the time it crashed... according to the logs...the OP was running Ableton Live at the same time, presumably rewired with Logic... so add all that together with UAD plugins... and that's quite a load on the system...
Finally in thread 32 there is a weird exception msg relating to the Trash2 plugin.. that I haven't seen before...
Thread 32:
0 libSystem.B.dylib
0x94c29afa mach_msg_trap + 10
1 libSystem.B.dylib
0x94c2a267 mach_msg + 68
2 ...tope.audioplugins.AU.Trash2
0x667bd57a catch_exception_raise + 250
3 libSystem.B.dylib
0x94c57259 _pthread_start + 345
4 libSystem.B.dylib
0x94c570de thread_start + 34
That might be nothing... but as i said, I haven't seen that one before and given what else is going on.. it might be involved too... or nothing to do with that at all! -
Have been using Bridge for ages but ran across a problem this morning I had not seen before.
Creating some web galleries for a couple of customers I used Bridge to Create a Flash Gallery and then posted on my web site. All worked just fine and with only 16 images creating the gallery was about 30 seconds. Then went back to the "Essentials View". Went back into Photoshop CS6 to work on some images for another upload, and Photshop was running really slow. Normally on my Win 7 x64 system (16GB) RAM it runs really well. Fired up task Manager and saw that Bridge was consuming just over a GB of memory. Closed Bridge, opened Bridge again, used Bridge to open images in ACR then into Photoshop. Bridge at 250 GB and system running fine. Created another Web Gallery and Bridge up to a GB again. Finished and went back to Essentials view - Bridge not giving back any memory. Now this was with 16 images - gets worse when you create a gallery of say 200 images.
Now I know Bridge is somewhat of an Orphan but is there any need to hold onto the memory -as even with my somewhat beefy system I have to close and reopen Bridge to bring performance back.
Cheers
Mike
PS Running the latest versionsof Bridge and Photoshop and ACR 7.3 that are available for a non-cloud userI have only used Web Galleries from Bridge a few times before - but I think I have narrowed down the cause. If I just create the Gallery resources look normal - but if I hit preview the memory allocation goes up - so could be caching the whole Gallery - but would have thought that it would have released it once the browser was closed - looks like Bridge does not look for close of the preview so hold onto everything.
Have to admit that the Web Gallery feature works well to get images onto a site in a hurry for a client to preview - and email me back with the final images they want. Now to brush up on my XML & HTML to add in a few instructions and add a link to direct them back to my home page
Happy New Year
Mike -
Is it just me or is Firefox getting worse?
I have been using Firefox since it came into the world and have never looked back at IE -- it works, is updated regularly and is free.
Well recently (within the last couple months or so) I have been experiencing a couple really annoying problems related to loading Firefox:
1) I'll load Firefox -- the Firefox window will appear, but the entire Window canvas will be filled with gray. There is no web page, no search bar -- nothing, just gray and the Windows title bar saying "Firefox". If I exit the Window (Microsoft's minimize, maximize, and close buttons are still in tact) and try to restart again I'll either get this gray screen again or Firefox will launch as expected -- as a browser I can use.
This problem is REALLY ANNOYING! So much so that I uninstalled Firefox, re-downloaded the installer and re-installed. The problem persisted so I formatted the ENTIRE box, patched the OS, installed Firefox and the problem still persists intermittently.
And now I'm beginning to notice ANOTHER problem. When I have my browser window open, I often launch new instances of Firefox (as opposed to CTRL+N for new Window -- I use that plenty too). I've been finding that when I click the icon to launch FF when FF is already running, NOTHING HAPPENS! If I click it 10 times, I might have 2 FF windows appear or maybe none! The task manager does not show that I have a bunch of FF instances running -- its as if FF is deciding I don't need another instance because I already have one.
In summary, the browser never behaved this poorly until the past one or two months. It's really starting to irritate me, especially after spending a day wiping my box and reinstalling all the Windows patches. The only add-on I have is Adobe Flash 10 and I doubt that is the issue since the browser start page (default Google/FF) doe snot have any Flash on it ever.
Please fix the code soon! It never used to have these problems.I agree that Firefox keeps getting worse. I can't stand the current interface with its smaller icons and monochromatic tool bars. Everything is just harder to deal with. I just reverted to 3.6, but was getting messages that certain Web sites needed a browser update. So, now I'm back to this annoying 7.01, but I'm switching to IE8 as my default.
Probably most annoying to me is Firefox's inability to manage history settings so that the user can set time limits on memory, which is an extremely handy way of quickly determining what's already been looked at. -
Dedup performance getting worse and worse
Hi Everyone
I am running Windows 2012 Server and using it for storing VEEAM backups of our VMware environment, and well as a lot of SQL database backups
Deduplication has been running well for the past couple of months (about 35Tb saved), but the performance seems to be getting worse and worse and it is now struggling to keep up with the rate at which new data is added
Checking task and resource manager it doesn't appear that the fdsmhost.exe is really doing much work at all. I see long periods of complete inactivity with no disk access which is not really what I would expect. The files deduped and dedup savings are not
changing either
Does anyone have any good information about factors affecting dedup performance. I've tried manually starting the dedup job with the priority and memory usage parameters to force it to high priority and give it a decent amount of memory but still no joy
We have recently added some more VMs to our setup so some of the backup files are very large (around 1.6Tb). is it likely to just be struggling with these large files?
Any clues or best practices?
Thanks
Harley1) I can share current stats but don't have anything historically before things started to slow down
Volume : D:
VolumeId :
\\?\Volume{222fb
StoreId : {4D7E4D3E-EC7F-4
DataChunkCount : 79157302
DataContainerCount : 2188
DataChunkAverageSize : 27.09 KB
DataChunkMedianSize : 0 B
DataStoreUncompactedFreespace : 0 B
StreamMapChunkCount : 69269
StreamMapContainerCount : 564
StreamMapAverageDataChunkCount :
StreamMapMedianDataChunkCount :
StreamMapMaxDataChunkCount :
HotspotChunkCount : 758605
HotspotContainerCount : 21
HotspotMedianReferenceCount :
CorruptionLogEntryCount : 0
TotalChunkStoreSize : 2.07 TB
2) There is no integration between VEEAM and MS as such. VEEAM just writes the backup files to a share and then Windows goes and deduplicates these at a later date. This was working fine for a couple of months but now seems to basically be doing nothing.
This is causing me to run out of space fast as a weekly full backup is around 1.6Tb and the nightly incrementals are about 200Gb each. When this was working they would all get deduplicated back close to nothing freeing up nearly all of the space. Obviously
this makes a massive difference. VEEAM itself is still working, but no deduplication seems to be happening
3) I probably wasn't very clear, but it is only SQL backups being stored on here and not any actual live databases. As the nightly backups don't change very much and are never accessed except in a restore they should be perfect candidates for deduplication
and do actually give very good deduplication rates.
I do notice that one of the items on your list is files approaching or greater than 1Tb
so maybe that is the problem as the weekly backup is one 1.6Tb file
Maybe i'll try to split the backups up slightly and see if that makes any difference. Thinking about it ..... before we adding the recent batch of servers to VMware the backup was around the 1Tb mark and it seems to have died around the jump to 1.6Tb -
Anyone use nio-memory-manager ?? what's it good for?
Can someone give me an example of when the nio-memory-manager should be used?
Thanks,
AndrewIf I remember the outcome of my experiments with NIO right the situation is as follows:
1. Allocating/releasing huge shared memory blocks over and over can lead to OS/JVM issues. To avoid this I allocated the max size I wanted from the start (this is an option when configuring "off-heap" storage I believe). When doing it this way I had no reliability issues with the NIO memory manager in my tests.
2. Tangosol/Oracle used to claim that the off-heap (NIO memory manager) result in worse performance than on-heap - I could not see any clear indication of this but this may be application dependent. For our app the reduced number of JVM:s per server (reducing network communication, number of threads, risk of any JVM performing GC at a given time etc etc) seemed to more than offset the allegedly slower memory manager resulting in MUCH BETTER performance! A lot of queries etc anyhow (at least for us) mainly work against indexes that always are stored "on-heap"...
3. There is a limitation to 2Gb per NIO block (at least in 32-bit JVM:s not sure about 64:bit - never seen any point in using them since larger heaps than 2Gb seldom work well anyhow and each pointer consumes double the space in heap and CPU-caches) but this is for each CACHE and separate for PRIMARY and BACKUP I believe! So my understanding is that if you (using 64-bit OS) for instance have two (equally big) caches you could allocate max 2 * 2 * 2 = 8Gb of off-heap memory for folding data per JVM (without ANY impact on GC-pauses!) and in addition to that use as much heap as you can get away with (given GC-pause times) for holding the indexes to that data. This would makes a huge difference in JVM count!- for example we today have to run like 10+ JVM:s per server using "on-heap" while we using "off-heap" storage probably could get that down to one or two JVM:s per server!
4. There may be both OS and JVM parameter that you need to set (depending on OS and JVM used!) in order to allocate large amounts of shared memory using NIO (the default is rather small).
As for the question about de-allocation I never saw any sign of memory leaks with the NIO memory manager (i.e. space previously occupied by deleted objects were reused for new objects) but as I mentioned above you better allocating the max size NIO memory block you intend to use up-front and that memory will then remain allocated for this use so if your amount of cache data vary and you would like to use memory for other purposes (like heap!) at some point you may be better of sticking with "on-heap" that is more flexible in that respect.
As I previously mentioned off-heap is today (until Oracle fixes the improvement request!) really only an option if you do not plan to use "overflow protection" or your objects are fixed size :-(
And if you are interested in using servers with a lot of memory and would like to use "off-heap" please talk to your Oracle sales rep about it! If enough people do that it may allow the Coherence developers to assign more time for making "off-heap" storage better! With this feature in place Coherence will be even more of a "killer application" than it already is!
Best Regards
Magnus -
Hi everyone I am sahasvat.I am using Acer aspire 5755. It's specification are Intel i3 3rd gen processor, 2Gb DDR 3 ram and 500 GB hdd.I am running on windows 8 OS. I opened about 4 tabs on google chrome and suddenly a blue screen with sad face displayed
an error kernel data inpage and it got restarted and after 5 mins I opened google chrome and again blue screen came and displayed an another error memory management and while restarting on bios I pressed f8 and booted to safe mode as normal
mode didn't open.soon after 20 mins I restarted my lap and I received an error 0xc000021a bios and windows booted.i then pressed power button for a min and switched on my pc but it showed a different error 0xc00000e9. I restarted many times
either 0xc000021a or 0xc00000e9 used to come not an fixed error. I don't have my cd as it got scratches on CD. Plzz help me to get out of this problem.
I can't even access my laptop and I am using my windows phone to post this.Hi everyone I am sahasvat.I am using Acer aspire 5755. It's specification are Intel i3 3rd gen processor, 2Gb DDR 3 ram and 500 GB hdd.I am running on windows 8 OS. I opened about 4 tabs on google chrome and suddenly a blue screen with sad face displayed
an error kernel data inpage and it got restarted and after 5 mins I opened google chrome and again blue screen came and displayed an another error memory management and while restarting on bios I pressed f8 and booted to safe mode as normal
mode didn't open.soon after 20 mins I restarted my lap and I received an error 0xc000021a bios and windows booted.i then pressed power button for a min and switched on my pc but it showed a different error 0xc00000e9. I restarted many times
either 0xc000021a or 0xc00000e9 used to come not an fixed error. I don't have my cd as it got scratches on CD. Plzz help me to get out of this problem.
I can't even access my laptop and I am using my windows phone to post this. -
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 -
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? -
Oracle 11g AMM (Automatic Memory Management)
Hi All,
I have a very powerful server 24 Processors with 6 cores each and 74 GB RAM for my production database. The server will host only one production database. I wanted to use AMM for this database and allocate maximum memory to Oracle by setting memory_target. By default /dev/shm is set 37 GB but I wanted to increase it least 55 GB. I know I can get this changed by my system admin but I wanted to know how much memory should leave for OS?
Please help me on sizing this.
Thanks,
Arun SinghFrom MOS ID 169706.1
Automatic Memory Management
Starting with Oracle Database 11g, the Automatic Memory Management feature requires more shared memory (/dev/shm) and file descriptors. The shared memory should be sized to be at least the greater of MEMORY_MAX_TARGET and MEMORY_TARGET for each Oracle instance on the computer. To determine the amount of shared memory available, enter the following command: # df -k /dev/shm/
Note: MEMORY_MAX_TARGET and MEMORY_TARGET cannot be used when LOCK_SGA is enabled or with huge pages on Linux -
MAC OS X Lion performance problem - broken memory management
Starting with OS X 10.5 there are evident memory management problems in MAC OS X. The web was already then cluttered with complaints about system slowing down dramatically after some time. Back then i had slower machine, Mac Mini with 1GB RAM, so i (wrongly) concluded that it was due to inferior hardware.
Now i have 2010 MBP, core i7, 8 GB RAM, dual GPU.
Mac os X Snow Leopard was pain, but after migrating to OS X Lion, working some serious stuff on MAC started to be a nightmare.
I finally managed to reproduce the problematic scenario, so i run the test and recorded the screen, into video.
http://www.youtube.com/watch?v=u5wZwZh61_4
I run the tar+bzip command, which is basic unix stuff, on the large amount of picture files, in my Pictures/ folder. Just before start, i run the "purge" command, to delete inactive/cached program data.
You can see on the video that free memory starts to drop very fast, and inactive is constantly rising. If you take a look at "bsdtar" command, it takes only a fragment of RAM, so the problem is not in this process. You cannot say that it is a program memory leak, because then the problem would not be in inactive ram, rather in active/wired.
When the free memory dropped below 100mb, i started some apps, like Safari, iPhoto and MS Word, and you can see in the video, that it takes even minutes to start an app, when normally (when there is free RAM), it would take some 3-5 secs to load.
I run the same scenario and the same commands on my Linux Centos 6 box, no problem there ! Memory usage is some 10-20mb, no problems with cache/buffer.
The memory management must be very broken in Mac OS X !Broken? That's a bit harsh.
Immature? That's perhaps a better explanation.
This paper describes Priority Paging as implemented in Solaris 2.7 back in 1998, and that's essentially what Mac OS X is in need of today:
The problem is that when pages are needed, no differentiation is made between system file cache pages and application pages, and worse, the file cache can actually steal pages needed by applications.
Finally when Dynamic Pager starts up and needs to start swapping things out, it's fairly heavy weight in operation, and causes the UI not responding cursor (aka the spinning beach ball) to appear. -
Memory Management in LabView / DLL
Hi all,
I have a problem concerning the memory management of LabView. If my data is bigger than 1 GB, LabView crashes with an error message "Out of Memory" (As LabView passes Data only by value and not by reference, 1 GB can be easily achieved). My idee is to divide the data structure into smaller structures and stream them from Hard Disk as they are needed. To do so, i have to get access to a DLL which reads this data from disk. As a hard disk is very slow in comparison to RAM, the LabView program gets very slow.
Another approach was to allocate memory in the DLL and pass the pointer back to LabView...like creating a Ramdisk and reading the data from this disk. But memory is allocated in the context of Labview...so LabView crashes because the memory was corrupted by C++. Allocating memory with LabView-h-Files included doesnt help because memory is still allocated in the LabView context. So does anybody know if it's possible to allocate memory in a C++-DLL outside the LabView context, so that i can read my Data with a DLL by passing the pointer to this DLL by LabView? It should work the following way:
-Start LabView program--> allocate an amount of memory for the data, get pointer back to labview
-Work with the program and the data. If some data is needed, a DLL reads from the memory space the pointer is pointing at
-Stop LabView program-->Memory is freed
Remember: The data structure should be used like a global variable in a DLL or like a ramdisk!
Hope you can understand my problem
Thanks in advance
Christian
THINK G!! ;-)
Using LabView 2010 and 2011 on Mac and Win
Programming in Microsoft Visual C++ (Win), XCode (Mac)If you have multiple subvis grabbing 200MB each you might try using the "Request Deallocation" function so that once a vi is done processing it releases the memory.
LabVIEW Help: "When a top-level VI calls a subVI, LabVIEW allocates a data space
of memory in which that subVI runs. When the subVI finishes running, LabVIEW
usually does not deallocate the data space until the top-level VI finishes
running or until the entire application stops, which can result in out-of-memory
conditions and degradation of performance. Use this function to deallocate the
data space immediately after the VI completes execution."
Programming >> Application Control >> Memory Control >> Request Deallocation
I think it first appeared in LabVIEW 7.1.
Message Edited by Troy K on 07-14-2008 09:36 AM
Troy
CLDEach snowflake in an avalanche pleads not guilty. - Stanislaw J. Lec
I haven't failed, I've found 10,000 ways that don't work - Thomas Edison
Beware of the man who won't be bothered with details. - William Feather
The greatest of faults is to be conscious of none. - Thomas Carlyle -
Hello All!
I read the Memory Management Programming Guide for Cocoa - several times. But some things are still not really clear.. I would like and need to have a deeper understanding. So, I hope someone could help me The problem is that I had to get rid of several (..) memory leaks in my app, and now I am a bit confused and unsure about my skills at all..
1.
What is the difference between sayHello1,sayHello2,getHello1,getHello2,getHello3 and which one is "better" (and why) - please dont try to interprete the logic/sense of the methods itself
- (NSString *) sayHello1{
return [[[NSString alloc] initWithString:@"Hello"] autorelease];
- (NSString *) sayHello2{
return [[[NSString alloc] initWithString:@"Hello"] retain];
- (void) getHello1{
NSString *hello = [self sayHello1];
[hello release];
- (void) getHello2{
NSString *hello = [self sayHello2];
[hello release];
- (void) getHello3:(NSString *)hello{
[hello retain];
NSLog(@"%@", hello);
[hello release];
Concerning this, there are several questions:
2.
If I have to release everything I retain/alloc, why then do I have a memory leak, if am returning an object (which was allocated with alloc and init) from a method without autorelease. The object is still in memory. But the following method wont work. What I accept. But the object is, if returned, not reachable, but also not released. Why then is it not automatically released? (i dont mean autorelease)
- (NSString *) sayHello1{
return [[NSString alloc] initWithString:@"Hello"]];
- (void) getHello{
NSString *hello = [self sayHello1]; //wont work. the object is not there, but also not released. WHERE is it?
[hello release];
3.
When is a delegate method released, if I have no variable I can use to "release"? So, if I have nothing to access the delegate like a NSURLConnection delegate?
should I, for example, call a [self release]?
- (void)startParser{
Parser *parser = [[Parser alloc] init];
[parser start];
//should I use a [parser autorelease or retain] here?
- (void)parserDidEndDocument:(NSXMLParser *)parser{
//do somethings with the parserstuff
[self release];
4.
*And the last question:*
Where can I see in instruments, which elements have retain counts > 1 and potential leaks? I was reading the instruments guide but there is only theoretical stuff. No practical guides like: your app should not have/use more than x megabyte ram.. for example: my app gets slower and slower the longer a i use it. -> this indicates memory leaks..A Leak is only a leak if the reference to the object is lost.
https://devforums.apple.com/message/189661#189661 -
Memory Management with NSString and synthesized properties
I thought I understood memory management but now I'm getting some odd behavior and that's the only thing I can see that I might be doing incorrectly:
I have a synthesized NSString propery called displayText. At one point I attempt to set a label with the displayText property (label.text = [[note displayText]]). The first one works, but the second one does not:
[note setDisplayText:[[note fileName]]]; // - works
[note setDisplayText:[[self getCharacterInFileName:[[note fileName]]]]; // - does not work
And here is getCharacterInFileName:
// Given the fileName for the image, get the specific part of that fileName for the note letter
- (NSString *)getCharacterInFileName:(NSString *)fileName
NSRange range = {1,1};
NSString *characterInString = [[[NSString alloc]] initWithString:[[fileName substringWithRange:range]]];
return characterInString;
Is there some pointer mismanagement going on here that I'm missing?
Message was edited by: darkpegasusNevermind, I'm an idiot. I forgot to close an if/else block with a brace and it screwed everything up.
-
hi everyone.
I m trying to use OpenCV in After Effects. The problem is that OpenCV has its own management of memory.
The AE memory management is kind of bound to the lock/unlock system for multi thread processing and is kind of difficult to use from openCV...
So, as long as you dont use multi processing, I thought that using openCV would not be a problem.
But I was wrong. I got a random error:
After Effects error: Effects modules should only dispose worlds they have allocated.
My effect is allocating a lot of opencv layers, and one temporary AE layer. When I dispose the AE temporary layer, I have some errors when the rendering get slow and the user tries to interrupt it. the "After Effects error: Effects modules should only dispose worlds they have allocated."
When looking at the layer before disposing it, It s totally corrupted with random values for all the field, but data field is not NULL.
I did not get any error during the memory allocation of the layer though. Still it gets corrupted at some point.
I m wondering if it is openCV memory and AE memory that get into conflict or if it s my way of checking if layer has not been correctly allocated that is wrong.
I dont understand also why it would conflict, since system will allocate the memory on demand, and there is no reason the system would give conflicting memory regions....
I solved my problem by stopping using the AE temporary layer.
If anyone experienced and solved this kind of problem, please, let me know.
Regardshey marc,
I think you are overcomplicating things a little,
1) add a local variable of type PF_LayerDef (or allocate on heap); no
need to initialise anything
2) WorldSuite1()->new_world()
3) use the layer. use PF_GET_PIXEL_DATA8() to get pixels
4) WorldSuite1()->dispose_world() (optionally free a heap variable)
Am 28.07.2011 05:06, schrieb salvati marc:
I m back to this problem...
As always, Shachar, it seems you are right. I deactivated OpenCV code, and... still crashing.
I investigate the problem more in depth and found my mistakes...
What I was doing was:
1) allocating my tmp layer
2) copying source to tmp
3) processing with opencv
4) copying back to output
5) cleaning tmp layer
I did few mistakes:
1) I was checking tmpLayer->data == NULL to see if the tmp layer was right or not (in step 5). BUT, I copyed my source to tmp (step 2) even if it was not correctly allocated... I guess that s why when I check NULL before dispose it was not consistent
2) I did not always set the tmpLayer->data to NULL before allocation! default value is not NULL. So my check after allocation was not consistent in some case
So multiple reason of not getting a NULL data although the data where not allocated...
Like you said, ill supervised creating/disposing of worlds...
Anyways, I realized in my algorithm that i did not nid the tmp layer, and I could just use the output layer for that purpose... But i m sure i ll get this problem again in the near future, so I had to investigate that.
Thanks again for your precious help.
Regards.
>
Maybe you are looking for
-
Difference between factory excise invoice and Depot Excise Invoice
Hi Is there any difference in invoice calculation part in excise invoice through Factory sales and excise invoice through depot sales?I know the processes but not sure about the excise calulation in these.
-
Did a LOT of troubleshooting, but not finding suitable solution, still getting same error i referred all below links but not working for me. "http://blogs.msdn.com/b/how24/..." "http://social.msdn.microsoft.com/Forums/..." "http://stackoverflow.com/q
-
Error in Select Statement " Comma Without Preceding Colon"
Helo Gurus. This is my select query : SELECT SINGLE STREET HOUSE_NUM1 CITY2 TEL_NUMBER FAX_NUMBER POST_CODE1 STR_SUPPL1 REGION INTO ( L_STREET, L_HOUSENUM, L_CITY2, L_TELNUMBER , L_FAXNUM
-
ParameterBindingException when pipelining an Outlook.Folder object to custom cmdlet
Hello all- I've written a simple C# powershell cmdlet (Get-Store) that returns an Outlook Object Model Store object. Another cmdlet I've written reads the above Store object from the pipeline and creates an email folder (Get-Folder) I get a Parameter
-
How do I eject a blank DVD-R?
I inserted a blank DVD-R intending to produce a DVD using iDVD. My iMac made a lot of noise moving the disk around after I inserted it, way more than normal. I tried to make a DVD, but iDVD said to insert a blank disc and there is one in the computer