JDK-6680665 : bytecode Escape Analyzer produces incorrect escape information for methods without oop arguments
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: hs12
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_10
  • CPU: x86
  • Submitted: 2008-03-26
  • Updated: 2011-03-08
  • Resolved: 2011-03-08
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.
JDK 6 Other
6u14Fixed hs12Fixed
Description
Bytecode Escape Analyzer produces incorrect escape information for methods 
without oop arguments since it do not analyse such methods. 

For such methods which return an object bcEscapeAnalyzer
always says that it return a new non-escaping allocated object since
it is default escape information for a method before bytecode analysis.

In the failed test cases the methods are accessors for static fields oop
(which global escape). And the caller method synchronizing on this field.
But locks were removed since EA says it is not escaping.

Failed nsk methods:

 nsk/monitoring/ThreadInfo/getLockName/getlockname001
 nsk/monitoring/stress/thread/cmon001

 nsk/jdwp/StackFrame/GetValues/getvalues001
 nsk/jdwp/StackFrame/SetValues/setvalues001
 nsk/jdwp/StackFrame/ThisObject/thisobject001
 nsk/jdwp/ThreadReference/CurrentContendedMonitor/curcontmonitor001
 nsk/jdwp/ThreadReference/Interrupt/interrupt001
 nsk/jdwp/ThreadReference/Name/name001
 nsk/jdwp/ThreadReference/OwnedMonitors/ownmonitors001
 nsk/jdwp/ThreadReference/Resume/resume001
 nsk/jdwp/ThreadReference/Status/status001
 nsk/jdwp/ThreadReference/Stop/stop001
 nsk/jdwp/ThreadReference/Suspend/suspend001
 nsk/jdwp/ThreadReference/SuspendCount/suspendcnt001

Comments
EVALUATION See Description.
27-03-2008