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 185193 - OutOfMemoryError: Java heap space
Summary: OutOfMemoryError: Java heap space
Status: RESOLVED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-28 15:46 UTC by talofo
Modified: 2010-04-28 15:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 145916

Attachments
stacktrace (1.46 KB, text/plain)
2010-04-28 15:46 UTC, talofo 		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 talofo 2010-04-28 15:46:23 UTC 
Build: NetBeans IDE 6.8 (Build 200912041610)
VM: Java HotSpot(TM) 64-Bit Server VM, 16.2-b04-271, Java(TM) SE Runtime Environment, 1.6.0_19-b04-271-10M3050
OS: Mac OS X

User Comments:
GUEST: Stopping a C++ program

talofo: Scanning Projects

GUEST: It is not working, it is freezing and not functioing.

GUEST: i was doing a select to a database table




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at org.netbeans.lib.profiler.results.cpu.cct.nodes.BaseCPUCCTNode.<init>(BaseCPUCCTNode.java:105)
   at org.netbeans.lib.profiler.results.cpu.cct.nodes.TimedCPUCCTNode.<init>(TimedCPUCCTNode.java:186)
   at org.netbeans.lib.profiler.results.cpu.cct.nodes.MethodCPUCCTNode.<init>(MethodCPUCCTNode.java:95)
   at org.netbeans.lib.profiler.results.cpu.cct.CPUCCTNodeFactory.createMethodNode(CPUCCTNodeFactory.java:73)
   at org.netbeans.lib.profiler.results.cpu.CPUCallGraphBuilder.plainMethodEntry(CPUCallGraphBuilder.java:1095)
   at org.netbeans.lib.profiler.results.cpu.CPUCallGraphBuilder.plainMethodEntry(CPUCallGraphBuilder.java:1125)
Comment 1 talofo 2010-04-28 15:46:28 UTC 
Created attachment 98212 [details]
stacktrace
Comment 2 Tomas Hurka 2010-04-28 15:58:16 UTC 
The problem is not in profiler. In your case AWT was blocked for a long time and therefor sampling was running for a long. Accumulated data for slowness report run out of memory. 
Anyway, it should be fixed in NB 6.9.