Currently Being ModeratedJan 24, 2011 8:10 PM (in response to quenstalof)What was the name of the process? If it's an application at least you can force quit it. What you may have is a launch agent or daemon that relaunches automatically. Does it become unresponsive even after you force quit it?Mac Pro 2.66 Ghz; MBP Unibody; MBP C2D 2.33 Ghz; 11" MBA, Mac OS X (10.6.5), iMac C2D 17"; MB 2.0 Ghz; iPad 32G; 80GB iPod Video; iPod Touch; iPod Nano 2GB
Currently Being ModeratedJan 24, 2011 8:15 PM (in response to Kappy)In the process name column all it says is open(Not Responding). So I guess the process name is "open".
When I force quit it restarts automatically and then goes to not responding pretty soon after.MacBook4,1, Mac OS X (10.5.8)
Currently Being ModeratedJan 24, 2011 8:23 PM (in response to quenstalof)OK, you might give this a try. Go to /Library/Caches/ folder and remove com.apple.LaunchServices-023501.csstore. See if that helps.Mac Pro 2.66 Ghz; MBP Unibody; MBP C2D 2.33 Ghz; 11" MBA, Mac OS X (10.6.5), iMac C2D 17"; MB 2.0 Ghz; iPad 32G; 80GB iPod Video; iPod Touch; iPod Nano 2GB
Currently Being ModeratedJan 25, 2011 8:15 AM (in response to quenstalof)Caches will reappear when they are rebuilt. There is another cache associated with the dyld item that appeared in the open files you posted. Below is a fix you might try:
If you see this error in your system logs or in the terminal
"dyld: shared cached file was built against a different libSystem.dylib, ignoring cache"
Open terminal, type in this command, press enter.
Type in your admin password when prompted, press enter.Mac Pro 2.66 Ghz; MBP Unibody; MBP C2D 2.33 Ghz; 11" MBA, Mac OS X (10.6.5), iMac C2D 17"; MB 2.0 Ghz; iPad 32G; 80GB iPod Video; iPod Touch; iPod Nano 2GB
Currently Being ModeratedFeb 2, 2011 9:40 PM (in response to Kappy)+If you see this error in your system logs or in the terminal+
+"dyld: shared cached file was built against a different libSystem.dylib, ignoring cache"+
when would I see that error?MacBook4,1, Mac OS X (10.5.8)
Currently Being ModeratedMar 6, 2011 12:12 PM (in response to quenstalof)Did u solve the Problem this way?
'Cause I have exactly the same problem. But typing in the command in the Terminal and confirming it with my password, didn't work out. It still reappears.
Did you maybe solve the problem in the meanwhile?MacBook 2.4GHz, 2GB, Mac OS X (10.5.8)
Currently Being ModeratedMar 8, 2011 5:18 AM (in response to Jako129)Hi all.
I have exactly the same problem, and despite I followed the suggested procedure the "Open (Not Responding)" still comes back.
cheersMacBook 13", Mac OS X (10.5.8), 2.4 GHz Intel Core 2 Duo - 4GB DDR3
Currently Being ModeratedJun 10, 2012 5:37 PM (in response to iszio)
First post and looking for some help on the above too...
I'm receiving a 'open (not responding)' with the following message:
Any help would be much appreciated,
Currently Being ModeratedJun 10, 2012 6:12 PM (in response to scotirish14)
Hello, & welcome to the forums!
Could be many things, we should start with this...
"Try Disk Utility
1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at the top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
3. Click the First Aid tab.
4. Select your Mac OS X volume.
5. Click Repair. Disk Utility checks and repairs the disk."
Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
(Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)
If 10.7 or more, reboot holding CMD+r down to boot from the Restore Partition, use Disk Utility there.
BTW, I should mention that it's quite acceptable to start a new topic of your own.
Currently Being ModeratedJun 10, 2012 7:14 PM (in response to scotirish14)
In theory, it should prevent anymore losses & possibly recover some, but that's only 99.95% the case, there are rare instances where sometung could get worse, for instance if we're dealing with a RAM issue, anything you do could scramble it worse.
Currently Being ModeratedJul 17, 2012 1:40 AM (in response to quenstalof)
Hey everybody. I have had exactly this problem and could not find out what was going on. This morning I found out that I had a program SYNCMATE installed. I don't remember installing it but it was making it impossible to autostart/autostop the computer because it popped up a window asking to syncronize.
I deleted SyncMate and now the open (not responding) doesn't exist anymore.
Maybe a coincidence but............
Currently Being ModeratedOct 31, 2013 7:19 AM (in response to quenstalof)
I too had SyncMate installed at one time, but had deleted it. I was also seeing "Open(not responding)" in activity monitor – I installed EtreCheck which shows you all the little addons you have installed and I noticed a kernal extension from SyncMate still being loaded. Removed it and now the "open" process is no longer shown.