<AWT Dev> RFR: 8256643: Terminally deprecate ThreadGroup stop, destroy, isDestroyed,…

Sergey Bylokhov serb at openjdk.java.net
Fri Nov 20 07:46:15 UTC 2020

On Thu, 19 Nov 2020 18:51:50 GMT, Sergey Bylokhov <serb at openjdk.org> wrote:

>> This change terminally deprecates the following methods defined by java.lang.ThreadGroup 
>> - stop 
>> - destroy 
>> - isDestroyed 
>> - setDaemon 
>> - isDaemon 
>> The stop method has been deprecated since=1.2 because it is inherently unsafe. It is time to terminally deprecate this method so it can be removed in a future release. Thread.stop will be examined in a separate issue. 
>> The destroy, isDestroyed, setDaemon, isDaemon methods support the mechanism to explicitly or automatically destroy a thread group. As detailed in JDK-8252885, the mechanism to destroy thread groups is flawed and racy. Furthermore, this mechanism inhibits efforts to drop the reference from a thread group to its threads (so that thread creation, starting and termination do not need to coordinate with their thread group). These methods should be terminally deprecated so they can be degraded in a future release and eventually removed.
>> CSR with more information:  https://bugs.openjdk.java.net/browse/JDK-8256644
> Marked as reviewed by serb (Reviewer).

The changes in the awt are trivial and look fine.


PR: https://git.openjdk.java.net/jdk/pull/1318

More information about the awt-dev mailing list