JDK-4905952 : jvmtiEnterTrace and jvmdiEnterTrace have large memory footprint
  • Type: Bug
  • Component: hotspot
  • Sub-Component: jvmti
  • Affected Version: 5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,solaris_9,windows_2000
  • CPU: generic,x86,sparc
  • Submitted: 2003-08-13
  • Updated: 2004-01-21
  • Resolved: 2004-01-21
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 b35Fixed
Related Reports
Duplicate :  
JDK-4905492 - The size of the client jvm.dll has increased by 20% since 1.4.2
Duplicate :  
JDK-4905487 - Size of Solaris client libjvm.so increased by 1Mb in 1.5 b08
Relates :  
JDK-4639363 - Java Platform Profiling Architecture (JSR-163)
Relates :  
JDK-4950714 - JVMTI: tracing segfaults.
Description
The automatically generated classes jvmtiEnterTrace and jvmdiEnterTrace
are very large and noticeably increase the size of HotSpot.

These classes are designed to facilitate troubleshooting of JVMTI/JVMDI
applications and/or the VM implementations of these interfaces, including
in production VMs.
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger-beta2 FIXED IN: tiger-beta2 INTEGRATED IN: tiger-b35 tiger-beta2
14-06-2004
EVALUATION There are a variety of approaches which can be applied to reduce or eliminate the footprint of these classes. Some examples -- Instead of generating inline code, functions could be introduced which would eliminate some of the repeated code. These files could be compiled at a low level of optimization. They could be removed from production VMs (thus removing much of their value). An interface or hackery could allow much of what these classes do to be done with an external agent. ###@###.### 2003-08-13 ====================================================================== It is unclear if the increased executable size has any or a least need have any impact on run time foot print. We will explore these issues. ###@###.### 2003-12-02 ============================================= Per the decision at the performance meeting: tracing code is ifdef-ed out on C1-product builds. Code was shifted to allow this. ###@###.### 2003-12-17
17-12-2003