I'm brand new to the World of Processing and, as such, am unsure how or where to post this. I saw another OSX related post in this forum, so I thought I'd chime in here...
I found that starting up the Processing IDE on my Mac ( 8-core Mac Pro running OSX 10.6.5 ) took approximately 1.5 minutes. Far, far longer than it takes to start any other app on this machine. In fact, it took about as long to start the Processing IDE as it takes to boot the machine. Further investigation showed it taking as long, or longer, on my 14 year old's iMac.
After a bit of investigation, what I discovered is that the Processing IDE is trying to access "/home/lib" when it first starts. I can't find anything in my user environment that references "/home/lib", and I've tested this with several other user accounts the same machines, always with the same result.
I have a collection of Unix machines ( real and virtual ) and use the Unix "automount" facility to manage home directories for multiple users across all of these machines. What this means is that when Processing first starts up, it has to wait for the automount requests to time out whilst trying to find the home directory for a non-existent user ( i.e.: the user named "lib" ).
For the time being, I've disabled automount maps for home directories on the 2 Macs that might run Processing ( by commenting out the entries associated with "home" in /etc/auto_master and /etc/auto_home). Since automounting home directories, when the appropriate maps exist in a directory service, is the default behavior for OSX ( and many other Unix variants ), I'd very much like to find a way to prevent Processing from trying to access "/home/lib".
