Working on the ColDesp project, I discovered that at a certain point in working through a batch job, the script stops executing (it does nothing). I'm pretty sure this must be a memory issue. Hopefully it's not a leak in the SpiderMonkey dll. More likely, I'm failing to free something, or I can do a better job of creating and freeing objects so the memory's retrieved when it's needed. This will need a bit of work.

I've also realized that there's only really one way to do monitoring/policing of operations: spawning a thread to do all the JS stuff, and leaving the main thread counting time, with a dialog box always open which enables you to kill the JS thread. That will also take some work.

But the app is now so useful and convenient that it's worth the time. I'm using it for all sorts of little tasks now.