Finder Application 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 the application finder can't be opened 10810 fix error when opening an application. This FAQ discusses: the background of this problem; its history, the application cannot be opened 10810 reported workarounds, and general troubleshooting advice; and provides a procedure for identifying the process or processes that are filling the process table. "10810" "finder" "disown" It is based 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
The Application Finder Can't Be Opened 600
and resolution of this problem 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 the application finder can't be opened el capitan process. Processes can launch other processes, known as 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
Please enter a title. You can not post a blank message. Please type your message and try again. Kel Solaar Level 1 (0 points) Q: The application Finder.app can't the application finder can't be opened 1712 be opened. I upgraded to Snow Leopard yesterday, and I'm having a
The Application Finder Can't Be Opened 10810 Snow Leopard
lot of troubles, Finde, Time Machine and Disk Utility being the most annoying of them. I don't really know
Failed With Error 10810 For The File
which one of them is making the others unstable / crash but well that's starting to be very irritating, now when I try to start the Finder I get this http://www.thexlab.com/faqs/error-10810.html :*The application Finder.app can't be opened.*-10810Restarting the Computer ( Mac Book Pro Uni ) usually fix that, but it's the second time that it's crashing a 220 go files package copy. I ended up doing it with rsync, the copy is still going on ( it will take a long time ) but I'm left with a Zombie Computer where I can't https://discussions.apple.com/thread/2135129?start=0 open a finder, and every Application that use it to open some file is crashing itself.Is there a way to manually relaunch it ( I don't want to reboot, my computer is stuck backing up a lot of files ) ? I tried Sudo Launch the Finder from /System/Library/CoreServices/Finder.app/Contents/MacOS with no luck, any help would be appreciated.KSMessage was edited by: Kel Solaar Mac OS X (10.6) Posted on Aug 30, 2009 12:36 PM I have this question too Close Q: The application Finder.app can't be opened. All replies Helpful answers Page 1 of 47 last Next by willdenow, willdenow Aug 30, 2009 12:56 PM in response to Kel Solaar Level 1 (0 points) Aug 30, 2009 12:56 PM in response to Kel Solaar This message seems to be new to SL. I've had plenty of Finder crashes in Leopard, and never once recall seeing it.This has happened to me twice on my MacBook Pro 13". If Finder crashes, you will get this error message under SL if you try and reinitiate Finder after a crash or a force quit and before Finder fully reco
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies http://stackoverflow.com/questions/23398435/applescript-error-10810 of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask http://jacobsalmela.com/infamous-execution-error-error-type-10810-occurred-10810/ Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign the application up Applescript Error -10810 up vote 4 down vote favorite I have an 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 the application finder of type -10810 has occurred. On the Macbook the MidiPipe application opens. MidiPipe works normally on the Mini when started from 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
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)curr