-
Bug
-
Resolution: Unresolved
-
P3
-
11, 17, 21
glibc can sometimes, especially in case of multi threaded applications, keep certain pages in physical memory even though those pages have already been freed. This can be observed as increase in RSS for programs using glibc allocator.
The goal of this issue is to identify if there are any allocation patterns in the JVM that can lead to such memory fragmentation and in turn cause increase in RSS for Java applications.
The goal of this issue is to identify if there are any allocation patterns in the JVM that can lead to such memory fragmentation and in turn cause increase in RSS for Java applications.
- relates to
-
JDK-8193521 glibc wastes memory with default configuration
- Closed
-
JDK-8302264 Improve dynamic compiler threads creation
- Open
-
JDK-8198756 Lazy allocation of compiler threads
- Resolved