RFR(xs): 6344935: Clarify Object.wait javadoc with respect to spurious wakeups

Martin Buchholz martinrb at google.com
Sat Aug 12 01:33:53 UTC 2017

OK, I'll try my hand as well at making forward progress:

diff --git a/src/java.base/share/classes/java/lang/Object.java
--- a/src/java.base/share/classes/java/lang/Object.java
+++ b/src/java.base/share/classes/java/lang/Object.java
@@ -334,7 +334,7 @@
      * The thread <var>T</var> is then removed from the wait set for this
      * object and re-enabled for thread scheduling. It then competes in the
      * usual manner with other threads for the right to synchronize on the
-     * object; once it has gained control of the object, all its
+     * object; once it has regained control of the object, all its
      * synchronization claims on the object are restored to the status quo
      * ante - that is, to the situation as of the time that the {@code
      * method was invoked. Thread <var>T</var> then returns from the

More information about the core-libs-dev mailing list