JDK-4546426 : JVM_Clone clears newly allocated object
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • OS: generic
  • CPU: generic
  • Submitted: 2001-12-04
  • Updated: 2019-02-11
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
tbdUnresolved
Related Reports
Relates :  
JDK-4653558 - Java Application startup time is SLOW in JDK 1.4 compared to JDK 1.3.1_02
Description
JVM_Clone allocates an object from the heap, then performs a shallow
copy of the object being cloned into it.

In Merlin, we initialize the newly created object to zeros before
returning it to JVM_Clone. In Ladybird, we handed back an uninitialized
object.

###@###.### 2005-06-09 05:08:10 GMT
Comments
EVALUATION ###@###.### 2002-08-02 Suggested fix right on and easy to implement given current functions in collectedHeap.inline.hpp (e.g., common_mem_allocate_noinit()). At first glance, it looks like the post_allocation_setup* steps can also be skipped by the noinit routines, except for the jvmpi allocation notification.
11-06-2004
SUGGESTED FIX We have methods in collectedHeap to do allocations: obj_allocate, array_allocate, large_typearray_allocate We could add new methods which return an uninitialized object.
11-06-2004