Can You Force GC in Java?

Direct Answer

System.gc() requests that the JVM make a best effort to reclaim unused objects; it does not guarantee an immediate collection, a particular scope, or that a chosen object is reclaimed. Application request paths should normally rely on the collector. Investigate an explicit request only for a measured, JVM-specific need and account for its possible CPU and latency cost.

Code Example

@Service
public class BatchProcessor {
    public void processBatch(List<Record> records) {
        for (var record : records) {
            processRecord(record);
        }
        // Do not call System.gc() as a cleanup step. Make sure this method
        // does not retain the records, and close owned resources explicitly.
    }
}

If a diagnostic experiment deliberately calls System.gc(), label it as a request, record the JVM and flags, and verify the resulting GC log. Do not write a helper named forceCollection, because the API cannot make that promise.

Common Mistakes & Pitfalls

• Calling a request a command: System.gc() gives no portable guarantee of immediate collection or a particular event.
• Using it as resource cleanup: Files, sockets, direct/native ownership, and connections need explicit close rules; collection timing is not a lifecycle boundary.
• Using it to fix retained memory: A reachable object remains live after explicit GC. Find the retaining path or allocation source instead.
• Assuming one performance effect: Explicit-GC behavior can be paused, concurrent, or disabled depending on JVM, collector, and flags; use logs and measurement.