This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 219372 - VirtualMachineError: out of space in CodeCache for adapters
Summary: VirtualMachineError: out of space in CodeCache for adapters
Status: RESOLVED WONTFIX
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 7.2
Hardware: All All
: P3 normal (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-02 11:53 UTC by Tomas Mysik
Modified: 2012-10-02 12:24 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 192944

Attachments
stacktrace (1.08 KB, text/plain)
2012-10-02 11:53 UTC, Tomas Mysik 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tomas Mysik 2012-10-02 11:53:52 UTC 
Build: NetBeans IDE 7.2 (Build 201207171143)
VM: Java HotSpot(TM) 64-Bit Server VM, 20.10-b01, Java(TM) SE Runtime Environment, 1.6.0_35-b10
OS: Linux

User Comments:
tmysik: just open profiler snapshot




Stacktrace: 
java.lang.VirtualMachineError: out of space in CodeCache for adapters
   at org.netbeans.modules.profiler.LoadedSnapshot$SamplesInputStream.readSample(LoadedSnapshot.java:590)
   at org.netbeans.modules.profiler.SampledCPUSnapshot.getSample(SampledCPUSnapshot.java:272)
   at org.netbeans.modules.profiler.SampledCPUSnapshot.getTimestamp(SampledCPUSnapshot.java:110)
   at org.netbeans.modules.profiler.snaptracer.impl.IdeSnapshot.getTimestamp(IdeSnapshot.java:93)
   at org.netbeans.modules.profiler.snaptracer.impl.TracerModel.getTimestamp(TracerModel.java:120)
   at org.netbeans.modules.profiler.snaptracer.impl.TracerModel.firstTimestamp(TracerModel.java:111)
Comment 1 Tomas Mysik 2012-10-02 11:53:56 UTC 
Created attachment 125220 [details]
stacktrace
Comment 2 Tomas Hurka 2012-10-02 12:24:50 UTC 
This is not a bug in profiler. This failure only occurs with a full CodeCache, so it can be worked around by using a large size with the "-XX:ReservedCodeCacheSize=" option.