JDK-6630863 : Profiled NetBeans crashes in allocation memory profiling if CMS GC enabled
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 6u5
- Priority: P2
- Status: Closed
- Resolution: Duplicate
- OS: windows_xp
- CPU: x86
- Submitted: 2007-11-16
- Updated: 2012-02-01
- Resolved: 2009-07-29
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.
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 7 |
|---|
7Resolved  |
Related Reports
|
Duplicate :
|
Description
http://www.netbeans.org/issues/show_bug.cgi?id=112853 Performed steps: - NetBeans 6.0 Profiler was used to profile another instance of NetBeans 6.0, the instance was started with the customized userdir and agentpath parameters for profiler direct attach - Memory Task (Record object creation only, each 50 object, record allocation stack traces) was chosen for profiling - Crash happened during profiled NetBeans 6.0 instance startup. # # An unexpected error has been detected by Java Runtime Environment: # # EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x6d9a42b3, pid=3868, tid=2124 # # Java VM: Java HotSpot(TM) Client VM (1.6.0_05-ea-b06 mixed mode windows-x86) # Problematic frame: # V [jvm.dll+0xf42b3] # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp #
Comments
|