Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Nigel Wade Newsgroups: comp.lang.java.programmer Subject: Re: Interrupt code while running (from Form) Date: Thu, 20 Oct 2016 16:01:49 +0100 Lines: 4 Message-ID: References: <6628a02c-9c5a-4cdc-8113-fcf13c972ea4@googlegroups.com> <17cd471e-65d9-47ed-b616-be748efd8fec@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net Zd8YQZaz71kOYSJi+ES/VwaiS/1OZy+j/EilXnF53W9leO4ek0 Cancel-Lock: sha1:m0x/zs5Kir08f7bbAdZ2yAOTTwU= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 In-Reply-To: <17cd471e-65d9-47ed-b616-be748efd8fec@googlegroups.com> Xref: csiph.com comp.lang.java.programmer:35851 On 20/10/16 13:27, Eric Douglas wrote: > If you run something from the IDE then you think you closed out but the IDE shows your test still running, go to your JDK install folder, to it's bin folder, and run the jvisualvm.exe. Double click your process, go to the Threads tab, and click the Thread Dump button. To perform background tasks in a Swing application it's preferable to use a SwingWorker. It takes care of worker thread management for you so you shouldn't get problems like this (the worker threads are daemons). It also has other advantages if any UI feedback is required.