i have written a small program which is communicating with an arduino using
the serial library.
when my computer goes to sleep (standby) and then wakes up again processing
is totally dead as well as the applet running. processing can be killed by
using "Force Quit", however the processing.core.PApplet cannot be killed
without a restart..

using latest revision of processing, serial library and oscP5 library.

as a sidenote the Arduino-editor also goes dead after standby

this isn't something we can fix--there's no way to know that your machine
is going to sleep so there's no way we can respond to it and shut things
down. you'll just need to be careful to not run applications when the
machine might do that.

ok, is processing different from all other applications in this matter?
i don't expect the serial connection to work after a sleep but it's kinda nasty
that the processing editor itself cannot handle a sleep but crashes (never
seen this for any other application under osx and i run quite a few)..

yes, in the sense that you're not doing anything like that in any other
application. you're dealing with a programming environment.. i'd be
surprised if you can write an application that talks to the serial port
while still running inside eclipse (or another development environment),
and still have the application and environment responding properly after
sleep.

talking to serial involves native code and driver nastiness that just isn't
likely to work well after system-level events like sleep. it will depend on
the driver, the serial device used, how up to date the native/java bridge
is, etc.

also, as for closing, be sure to use the 'stop' button, rather than hitting
the close button on the window. the close button on the window attempts to
shut down the application, but the stop button is the only way to kill it
if the application has become unresponsive.

okay, i was just curious, thanks for your time and the lengthy explanation :)