The best way I have found to restart a processing application is to use task scheduler in windows to restart and put a shortcut link in your startup folder. 

If you don't have access to the task scheduler, it is possible to launch a .bat file from processing itself. For that approach you would just check the system time periodically and a at a time you want, launch the bat file set to restart the computer. You will still need to put your app shortcut in the startup folder of windows to make is start on boot.

hope this works!

ak

@cageehv:

I don't believe the version of processing has anything to do with memory leaks. if your code has leaks, it will leak in any version of processing, or pure java for that matter. Many things have changed in the newer version and maybe one of your methods works great in processing 1.5 but needs to be adjusted for 2.0. I believe for any continuous application it is best to restart every day to start fresh, not for memory leaks, but for variables like frameCount that through a day can get huge and eventually too big to hold in an int. A good way to watch for memory leaks is a program called VisualVM ( http://visualvm.java.net/) it has a memory graph that can show you what the application's memory usage is. Watch that graph and you will know pretty quickly if you have a leak or not.