Probes to monitor some aspects of thread life cycle:
java.lang.Threador its subclass) are created
The table rows represent lasting events. The event starts when thread object is created, and ends when thread is started.
Thus, non-closed events in the table correspond to threads which has not started.
Such threads indicate potential design flaw.
However, note that threads actually started in native code can be shown as not started,
start() method is not called.
Thread constructor allows not to specify thread name explicitly.
Such threads get automatically generated name in form
To improve maintainability and clearness of your application, avoid creating anonymous threads, specifying thread name explicitly.
To check if there are anonymous threads in the profiled application,
sort the table by name column and look for threads named
Group by name column and sort by row count to check if there are threads with same name.
To improve maintainability and clearness of your application, ensure thread names are unique.
<Profiler Installation Directory>/probes/src