...
However, the Thread.stop() method causes the thread to stop what it is doing and throw a ThreadDeath exception. All acquired locks are subsequently released [API 20062014]. If the thread were in the process of adding a new integer to the vector when it was stopped, the vector would become accessible while it is in an inconsistent state. For example, this could result in Vector.size() returning an incorrect element count because the element count is incremented after adding the element.
...
Forcing a thread to stop can result in inconsistent object state. Critical resources could also leak if cleanup operations are not carried out as required.
Rule | Severity | Likelihood | Remediation Cost | Priority | Level |
|---|---|---|---|---|---|
THI05-J | Low | Probable | Medium | P4 | L3 |
Automated Detection
| Tool | Version | Checker | Description | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Parasoft Jtest |
| CERT.THI05.THRD | Avoid calling unsafe deprecated methods of 'Thread' and 'Runtime' |
Related Guidelines
POS47-C. Do not use threads that can be canceled asynchronously | |
CWE-705, Incorrect Control Flow Scoping |
Android Implementation Details
On Android, Thread.stop() was deprecated in API level 1.
Bibliography
[API 2006] | Class |
Section 24.3, "Stopping a Thread" | |
Chapter 7, "Cancellation and Shutdown" | |
Section 2.4, "Two Approaches to Stopping a Thread" | |
Concurrency Utilities, More information: Java Thread Primitive Deprecation | |
[JPL 2006] | Section 14.12.1, "Don't Stop" |
" |
[Sun 1999] |
...
...