Hi! Thank you for an awesome tool, it is a pleasure to use and has been very helpful to discover some subtle bugs in my code :)

I noticed a few minor issues when using time-capped collect command. All of them happen, when JVM exits before the configured duration of profiling session elapses:

• profiler does not exit immediately after JVM, but remains alive until the time elapses
• upon exiting the profiler prints Could not start attach mechanism: No such file or directory (I've commented redirection of output to /dev/null for debug purposes)
• if an output file was specified, then it contains only one line: CPU profiling started

Cheers,
Andrei