-
Bug
-
Resolution: Duplicate
-
P4
-
None
-
8u111
-
x86
-
windows_7
-
Verified
FULL PRODUCT VERSION :
FULL OS VERSION :
Windows 7 Professional SP1 (32bit and 64bit)
A DESCRIPTION OF THE PROBLEM :
Upon execution of an application of a Java applet involving a network communication operation,
From JDK 8u40 onwards, memory consumption of the JVM process increases with the passage of time, a memory leak has occurred.
This phenomenon does not occur in Java SE 8u 31 or earlier environments.
As a result of investigating using the Native Memory Tracking function,
We are confirmed that this phenomenon is occurring by continuing the expansion of the area of Thread arena.
The size of the Thread arena area is about 30 KB immediately after starting, but it continues to increase about 3 MB in 24 hours.
The applet is running with the Internet Explorer 11 plugin.
THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: Did not try
THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: Did not try
EXPECTED VERSUS ACTUAL BEHAVIOR :
No memory leak phenomenon
REPRODUCIBILITY :
This bug can be reproduced always.
FULL OS VERSION :
Windows 7 Professional SP1 (32bit and 64bit)
A DESCRIPTION OF THE PROBLEM :
Upon execution of an application of a Java applet involving a network communication operation,
From JDK 8u40 onwards, memory consumption of the JVM process increases with the passage of time, a memory leak has occurred.
This phenomenon does not occur in Java SE 8u 31 or earlier environments.
As a result of investigating using the Native Memory Tracking function,
We are confirmed that this phenomenon is occurring by continuing the expansion of the area of Thread arena.
The size of the Thread arena area is about 30 KB immediately after starting, but it continues to increase about 3 MB in 24 hours.
The applet is running with the Internet Explorer 11 plugin.
THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: Did not try
THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: Did not try
EXPECTED VERSUS ACTUAL BEHAVIOR :
No memory leak phenomenon
REPRODUCIBILITY :
This bug can be reproduced always.
- duplicates
-
JDK-8164293 HotSpot leaking memory in long-running requests
-
- Resolved
-