Skip to content
This repository has been archived by the owner. It is now read-only.
Permalink
Browse files
8225667: Clarify the behavior of System::gc w.r.t. reference processing
Reviewed-by: rriggs, kbarrett, tschatzl
  • Loading branch information
Mandy Chung committed Jul 6, 2021
1 parent 2b20778 commit 3a690240336bda8582a15ca52f4dcb78be323dcd
Showing 2 changed files with 9 additions and 0 deletions.
@@ -655,6 +655,10 @@ public Process exec(String[] cmdarray, String[] envp, File dir)
* There is no guarantee that this effort will recycle any particular
* number of unused objects, reclaim any particular amount of space, or
* complete at any particular time, if at all, before the method returns or ever.
* There is also no guarantee that this effort will determine
* the change of reachability in any particular number of objects,
* or that any particular number of {@link java.lang.ref.Reference Reference}
* objects will be cleared and enqueued.
* <p>
* The name {@code gc} stands for "garbage
* collector". The Java Virtual Machine performs this recycling
@@ -1872,6 +1872,11 @@ public static void exit(int status) {
* There is no guarantee that this effort will recycle any particular
* number of unused objects, reclaim any particular amount of space, or
* complete at any particular time, if at all, before the method returns or ever.
* There is also no guarantee that this effort will determine
* the change of reachability in any particular number of objects,
* or that any particular number of {@link java.lang.ref.Reference Reference}
* objects will be cleared and enqueued.
*
* <p>
* The call {@code System.gc()} is effectively equivalent to the
* call:

1 comment on commit 3a69024

@openjdk-notifier
Copy link

@openjdk-notifier openjdk-notifier bot commented on 3a69024 Jul 6, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please sign in to comment.