If so then this is interesting. Could be an internal VM thread that is not filtered out for some reason. I would add tracking of the mail thread group only by adding:
@ThreadLeakGroup(Group.MAIN) Dawid On Mon, Jun 10, 2013 at 1:00 PM, Grant Ingersoll <[email protected]> wrote: > That was the whole stack trace, unfortunately. > > On Jun 10, 2013, at 2:35 AM, Dawid Weiss <[email protected]> wrote: > >> Grant, top of the stack trace is not sufficient to tell what was the >> offending thread. Copy-paste the entire stack, including nested >> exceptions. The console will also contain a full stack trace >> information at the moment the test framework detected a thread leak. >> It should be easy to tell what isn't cleaned up properly. >> >> Dawid > >
