In Java, static fields usually remain in memory as long as the application is running.We are having out of memory problem and not able to figure out where it is happening either the application or environment. Through static FieldsĮxcessive usage of static fields can potentially lead to a memory leak. The most common types are detailed below: 1. Memory leaks can be of various types, depending on how they happen.
Excessive operating system page swapping.Insertion without deletion into Collection objects.These unintentional object references prevent the built-in Java garbage collection mechanism from freeing up the memory consumed by these objects.Ĭommon causes for these memory leaks are: In general, a Java memory leak happens when an application unintentionally (due to logical errors in code) holds on to object references that are no longer required. If memory leaks are not handled, an application can eventually run out of memory and terminate with an 'OutOfMemoryError', which is irrecoverable. Memory leaks block access to resources and cause an application to consume more memory over time, leading to degrading system performance. As a result, these unused objects are unnecessarily maintained in memory.
Unused objects are typically removed by the Java Garbage Collector (GC) but in cases where objects are still being referenced, they are not eligible to be removed. A memory leak is a situation where unused objects occupy unnecessary space in memory.
0 kommentar(er)
