Concurrent mark sweep collector
The concurrent mark sweep collector (concurrent mark-sweep collector, concurrent collector or CMS)[1] was a mark-and-sweep garbage collector in the Oracle HotSpot Java virtual machine (JVM) available since version 1.4.1. It was deprecated on version 9[2] and removed on version 14,[3] so from Java 15 it is no longer available.[4][5]
HotSpot garbage collectors
The HotSpot JVM selects the default garbage collector based on several factors.[6] The newer garbage-first collector (G1) was planned to replace CMS.[7] That change was finally done in version 9.
To launch the JVM with this garbage collector you can add this property to the java command line -XX:+UseConcMarkSweepGC[8][1] when using java version less than 14.
See also
References
- ^ a b "Concurrent Mark Sweep Collector Enhancements".
- ^ "JEP 291: Deprecate the Concurrent Mark Sweep (CMS) Garbage Collector".
- ^ "JEP 363: Remove the Concurrent Mark Sweep (CMS) Garbage Collector".
- ^ "JVM Garbage Collectors".
- ^ "Release Note: JEP 363: Remove the Concurrent Mark and Sweep (CMS) Garbage Collector".
- ^ "Garbage Collector Ergonomics".
- ^ "Java HotSpot Garbage Collection".
- ^ "Garbage Collectors".
- v
- t
- e
Memory management
- Memory management as a function of an operating system
- Memory management unit (MMU)
- Translation lookaside buffer (TLB)
- Input–output memory management unit (IOMMU)
- Demand paging
- Memory paging
- Page table
- Virtual memory compression
- Protected mode
- Real mode
- Virtual 8086 mode
- x86 memory segmentation
- Static memory allocation
- C dynamic memory allocation
- new and delete (C++)
- Fragmentation
- Memory leak
- Unreachable memory
Memory management- Virtual memory
- Automatic memory management
- Memory management algorithms
- Memory management software
 | This computing article is a stub. You can help Wikipedia by expanding it. |
- v
- t
- e
