Fading Coder

One Final Commit for the Last Sprint

Architectural Analysis of the G1 Garbage Collector

Managing cross-generation object references efficiently is critical for generational collectors. When a minor garbage collection occurs, the virtual machine must identify objects in the Young Generation that are still referenced by objects residing in the Old Generation. Scanning the entire Old Gene...

Understanding Garbage Collection

We know that garbage collection is handled by the engine. There are many JavaScript engines (different browsers have different ones), and their garbage collection mechanisms vary in details and optimizations. This article starts with some common collection algorithms, then takes V8 engine as an exam...

JVM Architecture and Garbage Collection Types

What is JVM? JVM stands for Java Virtual Machine. JVM Components Note: Before Java 8, the constant pool was located in the permanent generation within the heap. After Java 8, with the removal of the permanent generation and adoption of metaspace, the constant pool is now in the method area. Program...

Understanding Strong and Weak References in Java

Strong References Strong reference are the most prevalent type of object referencing in Java. When an object has a strong reference pointing to it, the garbage collector will not reclaim its memory. For example: Object obj = new Object(); If the program faces memory shortages, rather than collecting...