Details
-
Bug
-
Resolution: Cannot Reproduce
-
P3
-
None
-
8u31
-
x86_64
-
windows_7
Description
FULL PRODUCT VERSION :
java version "1.8.0_31"
Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 6.1.7601]
A DESCRIPTION OF THE PROBLEM :
When starting Java Cache Viewer with an almost empty cache (via Java Control Panel | General | Temporary Internet Files | View...), Windows Task Manager shows on my machine (Intel i7-3630QM, 16GB RAM) a CPU activity of 0 and a memory consumption of 130MB.
However, once an application of considerable size (i.e. 100MB) has been downloaded and started via Java Web Start, opening Java Cache Viewer this way takes considerably longer (on my machine, from almost immediately before to 10 seconds afterwards.) Additionally, the javaw process that is running Java Control Panel allocates about 1.5GB of additional memory before actually opening the window.
On less powerful machines, this symptom makes Java Cache Viewer look like not responding. Additionally, starting times of Java Web Start applications become not acceptable on these machines when an application is cached (up to 45 minutes).
REGRESSION. Last worked in version 8u25
ADDITIONAL REGRESSION INFORMATION:
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Start with a freshly installed JRE 8u31.
2. Open Java Control Panel and then Java Cache Viewer. Determine memory consumption and CPU activity. Should be normal.
3. Close Java Control Panel.
4. Download an application of considerable size (i.e. 100MB) via Java Web Start.
5. Open Java Control Panel and Java Cache Viewer again. Compare response time, memory consumption and CPU activity.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Response time, memory consumption and CPU activity should only marginally depend on the actual cache size. For example, in JRE 8u25, Java Control Panel only allocates 130MB when cache size is 87MB.
ACTUAL -
Response time, memory consumption and CPU activity are at least one order of magnitude higher than before (i.e. memory: 1.5GB with a cache size of 87MB compared to 130MB with an empty cache.)
REPRODUCIBILITY :
This bug can be reproduced always.
java version "1.8.0_31"
Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)
ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 6.1.7601]
A DESCRIPTION OF THE PROBLEM :
When starting Java Cache Viewer with an almost empty cache (via Java Control Panel | General | Temporary Internet Files | View...), Windows Task Manager shows on my machine (Intel i7-3630QM, 16GB RAM) a CPU activity of 0 and a memory consumption of 130MB.
However, once an application of considerable size (i.e. 100MB) has been downloaded and started via Java Web Start, opening Java Cache Viewer this way takes considerably longer (on my machine, from almost immediately before to 10 seconds afterwards.) Additionally, the javaw process that is running Java Control Panel allocates about 1.5GB of additional memory before actually opening the window.
On less powerful machines, this symptom makes Java Cache Viewer look like not responding. Additionally, starting times of Java Web Start applications become not acceptable on these machines when an application is cached (up to 45 minutes).
REGRESSION. Last worked in version 8u25
ADDITIONAL REGRESSION INFORMATION:
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b18)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Start with a freshly installed JRE 8u31.
2. Open Java Control Panel and then Java Cache Viewer. Determine memory consumption and CPU activity. Should be normal.
3. Close Java Control Panel.
4. Download an application of considerable size (i.e. 100MB) via Java Web Start.
5. Open Java Control Panel and Java Cache Viewer again. Compare response time, memory consumption and CPU activity.
EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
Response time, memory consumption and CPU activity should only marginally depend on the actual cache size. For example, in JRE 8u25, Java Control Panel only allocates 130MB when cache size is 87MB.
ACTUAL -
Response time, memory consumption and CPU activity are at least one order of magnitude higher than before (i.e. memory: 1.5GB with a cache size of 87MB compared to 130MB with an empty cache.)
REPRODUCIBILITY :
This bug can be reproduced always.