Suddenly getting bootstrap_register() errors with osascript commands

Question

Rarely but every so often my osascript commands start spitting back (for me) obscure errors--commands that tell me the iTunes current track, stream name, etc., various miscellany. Note that they do ordinarily work and have for quite some time. But for reasons I cannot fathom, this starts happening (a basic example):
$ osascript -e 'tell application "iTunes" to stop'
2009-01-11 03:44:03.443 osascript[974] CFLog (0): CFMessagePort:
bootstrap_register(): failed 1100 (0x44c), port = 0x2103, name =
'Processes-0.17563649'
See /usr/include/servers/bootstrap_defs.h for the error codes.
2009-01-11 03:44:03.443 osascript[974] CFLog (99):
CFMessagePortCreateLocal(): failed to name Mach port
(Processes-0.17563649)
CFMessagePortCreateLocal failed (name = Processes-0.17563649
error = 0)
Abort trap
They vary of course, but pretty much follow the model of the above whatever I try to do. I don't seem able to recover from this and get my osascript-ability back short of restarting the whole system. (This is not limited to iTunes. And I do wrap these up in shell scripts and the like, but the above is an actual verbatim example of what's happening to me right now.)
Please forgive me: my searches haven't found the answer. Is there some process I can kill, anything else I can do here? Any idea why this happens in the first place?

Answer 1

As a generic resolution of such memory issues, kindly
please follow up the next steps by the same order:
1.      
 Assure your memory configuration terms are
  with static values for min + max terms.
2.      
 For max terms , please assure you assign the appropriate value according to your memory specs + how many SQL instances installed
there on server
3-     
 Then Schedule appropriately a
 memory recycling job to Run some  or all of the below commands but particularly more the first 2 ones
 DBCC FREESYSTEMCACHE
('ALL');
 DBCC DROPCLEANBUFFERS
 DBCC FREEPROCCACHE
 DBCC FREESESSIONCACHE
4-      
 If you have low memory specs,
you have try to reduce polling interval of this schedule .
5-      
 Then configure the following notifications alerts
by an appropriate
 polling interval  like 1 minute  :
o  
 Memory grant queue waits _ Average wait time (ms) >0
o   
 Memory grant queue waits _Waits started per second>0
6-     
 Run your query again
>>and follow up the alerts .
7-     
 If you got alerted while executing your queries through
 more than attempt , then otherwise to :
 Enhance your query by seeking for examples the highest column sizes where they reduce TDS (Tabular Data stream packet) of query
then reduce memory usage
 Or seeking more memory for the server
 Or seeking if your VM has got properly its assigned memory or not ..?
 Since VM either Hyper V or VM ware or..etc might suffer from a general overload on the whole of station hosting VMs ending up
with such standstill cases for them
Think more deeply of performance terms