This bug was originally marked as duplicate of bug 236118, that is already resolved. This bug is still valid, so this seems to be another bug, but it might be related.

Build: NetBeans IDE 8.1 (Build 201510222201)
VM: Java HotSpot(TM) 64-Bit Server VM, 25.65-b01, Java(TM) SE Runtime Environment, 1.8.0_65-b17
OS: Mac OS X

User Comments:
GUEST: Porfiling

GUEST: Profiling the memory of a project

GUEST: The profiler didn't shut down when it was supposed to, it still ran some processes in the background.

GUEST: ran out of memory while profiling

GUEST: OOM while trying to profile a web application deployed to Tomcat 8 via the IDE.

GUEST: was trying to profile my application

GUEST: I was trying to profile a project

GUEST: Profiling an application that constantly re-loads generated bytecode.

Profiler showed steady / constant heap usage but total heapsize would grow.

Profiler telemetry showed GC generation set increase but all no classes showed high generation survival count.

GUEST: Profile

GUEST: ? ???????? ?????????????? ?? ??????, ?? ??? ? ?? ????????. ????? ???? ? ??????? 2 ????? ??????????????, ?? ? ?????????????? ?? ??? ??? ???????? ?????????. ????? ?????? ??? ????? ???????? ?????????????? ?? ?????? ?????? "???????? ?? ???????" ???? ??????????? ?????????. ? ?????? ?? ????????? ???????????????, ? ?? ?????? ?????? ??? ??? ?????? ????.

GUEST: Memory profiling of a large application. After a few minutes NB just runs our of memory. Would help if I could just filter the classes to profile.

xuelianggao: ?????????????




Stacktrace: 
java.lang.OutOfMemoryError: Java heap space
   at org.netbeans.lib.profiler.results.EventBufferProcessor.readDataAndPrepareForProcessing(EventBufferProcessor.java:133)
   at org.netbeans.lib.profiler.ProfilerClient$SeparateCmdExecutionThread.run(ProfilerClient.java:132)