You said it yourself, "I know Java's garbage collection mechanism. As long as something is still referencing it, it will not disappear." The variable "new1" is still referencing the memory of "new Data()" in the heap. , how can it be allowed to be recycled, so that the code we write is not all null pointer exceptions. You can use WeakReference instead of strong reference.

    WeakReference<Data> new1 = new WeakReference(data);
    Data new2 = data;
    new2 = null;
    data = null;
    System.gc();//告诉垃圾收集器打算进行垃圾收集，而垃圾收集器进不进行收集是不确定的 ,所以下面延迟2秒
    try {
      Thread.sleep(2000);
    } catch (InterruptedException e) {
      e.printStackTrace();
    }
    System.out.println(new1.get().num);

System.gc();

It is recommended that the JVM perform gc, which may be completely rejected. The GC itself will run automatically periodically, and the JVM determines the timing of the run. Moreover, the current version has a variety of smarter modes to choose from, and will automatically make selections based on the machine it is running on, even if there are indeed performance improvements. If required, you should also fine-tune the GC operating mechanism instead of optimizing performance by using this command.

Objects that have object references and are about to be deleted can still be set to null

    {
        OutClass outClass1 = new OutClass();
        OutClass outClass2 = new OutClass();
        outClass2.outClass = outClass1;
        outClass1 = null;
        System.out.print(outClass1);
    }
    
    class OutClass {
        public OutClass outClass;
    }

Before you understand the principles of JMM, never use System.gc() indiscriminately, just obj=null; when the object is used up.

The answer is no. This is undefined behavior in the JVM specification. Developers should not try to manually help the virtual machine recycle an object. If it is Sun's JDK, there seems to be an unsafe package, but I have never used it and I don't know if there is such an API.