Os X Finder Error 10810
Contents |
is full. When the process table is full, new (not currently running) applications cannot be opened until another running application ends. Programming errors in third-party applications can fill-up the process table, leading to the -10810 error when opening the application cannot be opened 10810 an application. This FAQ discusses: the background of this problem; its history, reported workarounds, and
The Application Finder Can't Be Opened 10810 Fix
general troubleshooting advice; and provides a procedure for identifying the process or processes that are filling the process table. It is based "10810" "finder" "disown" upon extensive research of this problem on the Web, especially a 2009 Apple Mailing Lists post by contributor Terry Lambert. This FAQ expounds upon Terry's post in an attempt to make the cause and resolution of this problem failed with error 10810 for the file more accessible to the general Mac OS X user. Background All running programs on your Mac are processes. This includes both applications that you open and faceless background processes, i.e. processes without a graphical user interface (GUI), such as mds (the Spotlight metadata server) or cupsd (the CUPS printing daemon). Activity Monitor shows a list of all running processes. Finder is an application, hence it is a process. Processes can launch other processes, known as
The Application Finder Can't Be Opened 600
child processes. For example, the launchd (launch daemon) process opens many background processes when you start up or log in to your Mac; launchd is the parent process and each process it opens is a child process of launchd. Mac OS X tracks running processes in a process table. Mac OS X has a default limit of 266 user processes per account. You can see this limit by issuing the Terminal command ulimit -a and noting the max user processes value. Once this limit is reached, the process table is full: new processes cannot be started until a currently running process terminates, hence new applications cannot be opened. If you attempt to open a new application when the process table is full, an alert dialog will appear showing error code -10810, e.g. The application appname.app can't be opened. -10810 where appname is the name of the application you attempted to open. If Finder is hung and you attempt to relaunch it when the process table is full, an alert dialog appears with the message: The application Finder.app can't be opened. -10810 The limit of 266 user processes per account is set high enough that it would be virtually impossible for a user to open enough applications to fill the process table (the default limit is different under Mac OS X Server). Programming errors,
a reboot. From what I've gathered by searching around on the web, Error 10810 occurs when the Launch Services framework has some sort of meltdown, causing the Mac OS X Kernel to run out of available threads the application finder can't be opened el capitan for anymore processes to launch. In the event that some process has got errant and is the application finder can't be opened 10810 snow leopard in some infinite loop of launching and hoarding threads, this will cause a rather lovely barrage of error dialog boxes (see screenshot below). If
The Application Finder Can't Be Opened 1712
you start getting Error 10810 in OS X, you likely won't be able to launch any other application (Finder included) and so the best thing you can do is to reboot your Mac. Yes, rebooting the Mac will fix the http://www.thexlab.com/faqs/error-10810.html error - kind of lame, but it works. If you are continuously plagued by this error, then you may be using some buggy software that is launching itself into a gazillion threads causing Mac OS X to freak out. If anyone has additional information or troubleshooting tips regarding this error, feel free to chime in. For what it's worth, simply killing and restarting the Finder was not sufficient in my experience to resolve the error, which is why a http://osxdaily.com/2010/02/09/mac-error-10810/ complete reboot of the Mac was necessary. Enjoy this tip? Subscribe to the OSXDaily newsletter to get more of our great Apple tips, tricks, and important news delivered to your inbox! Enter your email address below: Related articles: Fix Mac App Store Error @@errorNum@@Fix Mac App Store Error 100Fix "Error Establishing Database a Connection" When Using AbsintheFix the App Store "MZFreeProductCode .ClientCannotRedeemIosApp_explanation" Promo Code Redemption Error Posted by: William Pearson in Mac OS X, Troubleshooting 30 Comments » Comments RSS Feed Patrick McMahon says: February 9, 2010 at 5:21 pm I run into this every so often in Snow Leopard, to the point where I have to perform a hard restart. I noticed, on accident, yesterday that if I kick off Spotlight via Command+Space, and click on Show All, it will sometimes kick the Finder back into motion and restore my desktop icons, etc. Reply Aqilah says: September 18, 2012 at 8:36 pm Thanks a lot! really helpful patrick! Reply Steinar says: February 9, 2010 at 7:29 pm Logging out and back in again works for me. Reply Ian Cull says: February 9, 2010 at 8:02 pm Coincidence! This happened to me tonight, first time … I'll try logging out/in, better than reboot (plus it didn't shut down, I had to force off/on). Seemed to be LogMeIn that took it down, so Safari. Odd. Reply Dave says: February 9, 2010 at 11:30 pm If you use Sprin
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more http://stackoverflow.com/questions/23398435/applescript-error-10810 about Stack Overflow the company Business Learn more about hiring developers or posting ads http://jacobsalmela.com/infamous-execution-error-error-type-10810-occurred-10810/ with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 6.2 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Applescript Error -10810 up vote 4 down vote favorite I have an the application Applescript that runs fine on my Macbook Retina but fails on a Mac Mini. Both are running MacOS 10.9.2. After peeling the onion a bit I'm able to reproduce the problem with a one-line Applescript: tell application "MidiPipe" to activate On the Mini that throws the error: An error of type -10810 has occurred. On the Macbook the MidiPipe application opens. MidiPipe works normally on the Mini when started from the application finder the Finder or from Launchpad. Google provides no insight into this error. osx applescript share|improve this question asked Apr 30 '14 at 21:35 Richard Milewski 142210 Is the Mini running the same version of MidiPipe? –Digital Trauma Apr 30 '14 at 22:40 Have you tried removing and reinstalling MidiPipe on the mini? Perhaps a botched install is to blame? –Digital Trauma Apr 30 '14 at 22:41 add a comment| 2 Answers 2 active oldest votes up vote 2 down vote accepted Well, I found this: http://www.thexlab.com/faqs/error-10810.html and this: http://osxdaily.com/2010/02/09/mac-error-10810/ and this: http://forums.adobe.com/thread/1389805 . At least one of these suggests a RAM problem. But just to make sure you've tried every weird variation, have you tried the following: 1) using a full path: tell application "Full:Path:To:MidiPipe.app" --(probably "YourHDName:Applications:MidiPipe.app"? 2) using an actual tell block: tell application "MidiPipe"--or full path activate end tell 3) using the Finder: tell application "Finder" to open "Full:Path:To:MidiPipe.app" 4) using shell: do shell script "open /Applications/MidiPipe.app" ? share|improve this answer answered Apr 30 '14 at 22:41 CRGreen 2,0581517 Trying to figure out how to put line breaks into these comments while holding appplescript anomolies in my head risks explosion, so I'm going to do this a seve
Google Apps QI B.A.S. Information Technology Contact Me The Infamous OS X execution error: An error of type -10810 has occurred. (-10810) This error seems to appear often when I am using osascript for automating things. This error is a bit of a mystery as hundreds of users will say. In addition, it is not even listed in the MacErrors.h file found at: /System/Library/Frameworks//CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/Headers/MacErrors.h 1 /System/Library/Frameworks//CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/Headers/MacErrors.h After a lot of searching, I found some possible reasons why this error occurs: there is not a GUI, but one is required-even if being run as root access to assistive devices is not enabled the process table is full (i.e. fork bombs or zombie processes) LaunchServices has some sort of failure Since I mostly deal with scripting and automation, this post will be more about that and not so much about the Finder not being able to open because of this error. There Is Not A GUI, But One Is Required This error sometimes appears when running a script that requires a GUI, but the script is being run as root. The solution here is to get the current user and substitute as them. First, you need to get the current user and store that value in a variable, which can be done a number of ways: currentUser=$(stat -f "%Su" /dev/console) # Alternate ways to get the currently logged in user currentUser=$(who | grep console | awk '{print $1}') currentUser=$(logname) currentUser=$(ls -l /dev/console | cut -d " " -f4) currentUser=$(printf "get State:/Users/ConsoleUser\nd.show" | scutil | awk '/kCGSSessionUserNameKey/ {print $3}') 123456 currentUser=$(stat -f "%Su" /dev/console)# Alternate ways to get the currently logged in usercurrentUser=$(who | grep console | awk '{print $1}')currentUser=$(logname)currentUser=$(ls -l /dev/console | cut -d " " -f4)currentUser=$(printf "get State:/Users/ConsoleUser\nd.show" | scutil | awk '/kCGSSessionUserNameKey/ {print $3}') Then you can run the script under that user's context: su "$c