Error -10810: what's that?

PPC G5 and having the same problem. I've got too much stuff here to delete everything that hasn't been formally Leopard Certified, but they're not loaded or used.

Knowing what the error code means would go a long way towards solving the problem.

I have had this problem ever since I installed Leopard. I have found no clear answer. I have visited the loacl Apple store and they have no clear answer. Error code -10810 is a big mystery. I am very frustarted and starting to feel like a Vista user.

I googled the error code and found that it dates back to 2004.

Help Steve Jobs, you are our only hope.

This is really interesting because I've recently spent almost two hours on the phone with a level-2 apple technician who had to do a Google search to identify this error number and claimed there were no internal documents that referenced it.

He (I'm not naming him because I believe the problem is at a higher level) was only able to identify the issue because of these discussions. I also believe this group is subject to censure and topic erasure by Apple.

My system is mostly stable now, however I've also removed almost all of my utilities from my startup group and uninstalled software running drivers I couldn't swear didn't cause a conflict (like Wacom's Graphire tablet software). I'm afraid to plug in my Samson usb microphone.

I wonder when Apple will release 10.5.2........

It's a pain in the ***, that's what it is. 😟
I can't believe I'm not finding any solutions that work in this forum or elsewhere on the Internet.
I erased my hard disk, installed Leopard and must have moved some Tiger app settings that are not compatible using the import from your old computer-option.
Well then that's a problem in the assistant that helps you move your account then, isn't it?? IT SHOULDN'T ALLOW INCOMPATIBLE STUFF TO BE COPIED.
Why doesn't Apple do something about that?!

The process count is the problem, but shutting down unneeded processes is not a fix, there is an airport process that is forking new children soon after you free up a process slot (actually, I don't know the rate of forking as it is likely slow enough to work). There is a bug in airport on this issue.

I've seen this a few times now and we need a fix from Apple. I have airport turned off and it still happens.

If you log out and login back in, this will fix it for a while.

It seems to be the error that happens when your computer reaches the maximum amount of threads.
It turns out AppTrap was causing the problem for me. To find out what is causing the problem, quit an open program and immediately open activity monitor, closing an open app should free up some threads. Organize the list by number of threads. Be sure to list all processes. Whatever is at the top of the list is probably what is causing the problem.

donazipe,

The following file defines the error -10810:

/System/Library/Frameworks/CoreServices.framework/... /Frameworks/LaunchServices.framework/... /Headers/LSInfo.h

as:

/* ======================================================== */

/* LaunchServices Type & Constants */

/* ======================================================== */

enum {

kLSUnknownErr = - 10810 , /* Unexpected internal error*/

};

Basically, it means that the Launch Services framework is misbehaving and is encountering errors when trying to launch an application. This is fairly rare, as I've only seen a few other people in these forums have this error in the last several years.

When you encounter this error message, it is probably best to restart the machine (as I can't think of any other easy way out of this, since it's a catch-22 situation: if there was an app that could fix the problem you still wouldn't be able to launch it).

There could be a potential problem with the Launch Services database cache file, which is a file that OS X uses to store information about what applications are installed and the types of documents they can open, etc. You could try rebuilding this database as a step to troubleshoot the issue. I've written a small application that can do this: http://homepage.mac.com/mdouma46/images/LaunchServicesDatabaseRebuildApp.zip (.zip, ~60 KB). (Yes, there are literally hundreds of other third-party utilities that offer to basically accomplish this same thing, but none that I've seen follow the advice given to a developer friend of mine several years ago in a Developer Technical Support Incident (not customer support, developer support, normally these are $200/problem where you get help from an actual Apple engineer on a specific problem). That advice is to quit the Finder during the rebuild and to restart afterward). Obviously, if you're encountering the launch error, you'll need to run this after you restart, but it should hopefully prevent the problem from occurring in the future.

Sorry, I'm not sure about the Trash errors...

Hope this helps....

While you are correct in finding the result, the problem is that some process is running multiple copies of itself and sucking up the all of the per user process ids that are permitted. In my case, it is "always" airport. Everyone else might be identifying the "symptom" when they try to start a process and get the error, but the error is with the process that is found in the process list 25+ times. Logging out and back in will work for a few days, but the problem will come back. Anyone who comes across this again should quit something, and quickly open a shell and type 'ps -ax' and post the results. You might have to quit two or three apps.

Once we have that data, then we can make a guess.

I did notice that my ISP was having DNS errors last night (slow actually) and this preceded the problem. the DNS resolution library on Unix is the most nasty piece of business I have worked with since you can't timeout or abort with out using a setjump/longjump setup and that is evil stuff. This might be a hint.

Robert

It happened again, but this time I found the criminal. The "(airport)" process was launched through the dashboard and there was an active dashboard widget named "Air Traffic Control" that watched for wireless signal strength. I had wireless turned off, but the widget was active. It looks like it spawns a child process on every activation of the widget desktop and since there was no wireless interface active, it hangs that process. Nothing wrong with Apple's launch process, just a bad widget.

Like any process that spawns a child process, they must ensure they reap the dead child processes and make sure the child's life time is controlled!

I was getting the same message (-10810) when using iTunes, and sometimes Itunes shows as not responding in the "Activity Monitor". Looking at the Console's logs for iTunes I realize that an error was occurring when trying to open a Xvid codec (r58), so I deleted the codec, and the problem seem to be gone. The codec was dated back to 2006....

Check to see if you have an airport widget and then remove it ....

At the least, close one or more applications, start up the terminal and the do "ps -alx" and post the output here. I bet you have a runaway spawn.

Robert