StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POAre Thread.stop and friends ever safe in Java?
text
Body
copied!<p>The <code>stop()</code>, <code>suspend()</code>, and <code>resume()</code> in <code>java.lang.Thread</code> are deprecated because they are <a href="http://docs.oracle.com/javase/7/docs/technotes/guides/concurrency/threadPrimitiveDeprecation.html" rel="nofollow noreferrer">unsafe</a>. The Sun recommended work around is to use <code>Thread.interrupt()</code>, but that approach doesn't work in all cases. For example, if you are call a library method that doesn't explicitly or implicitly check the <code>interrupted</code> flag, you have no choice but to wait for the call to finish.</p> <p>So, I'm wondering if it is possible to characterize situations where it is (provably) safe to call <code>stop()</code> on a Thread. For example, would it be safe to <code>stop()</code> a thread that did nothing but call <code>find(...)</code> or <code>match(...)</code> on a <code>java.util.regex.Matcher</code>? </p> <p>(If there are any Sun engineers reading this ... a definitive answer would be really appreciated.)</p> <p><strong>EDIT</strong>: Answers that simply restate the mantra that you should not call <code>stop()</code> because it is deprecated, unsafe, whatever are <strong>missing the point</strong> of this question. I know that that it is genuinely unsafe in the majority of cases, and that if there is a viable alternative you should always use that instead. </p> <p>This question is about the subset cases where it is safe. Specifically, <em>what</em> is that subset?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload