Created attachment 72231 [details]
NetBeans log

Looking at message.log - there is OutOfMemoryError in NetBeans

WARNING [org.netbeans.lib.profiler.infolog]: OOME, resetting collectors!!!

Please try increase Xmx when running NetBeans. I also noticed that you are collection every allocation stack trace - you can lower the memory consumption 
by tracking  avery 10th or 50th allocation stack trace.

Created attachment 72328 [details]
NetBeans log with increased Xmx

I increase NetBeans memory allocation with -J-Xmx2048m and I get the same error in the GUI (no out of memory messages 
in the NetBeans log). I was watching NetBeans with jconsole.exe and memory use stayed around 1GB.

I get the same issue in 6.5 on OS X.  I'm trying to profile a J2EE app that uses Spring and Hibernate, and it takes a
while to load the Spring context.  So, every time I try to profile it I have to babysit on startup and click "No" a
bunch of times on that pop-up.

Any chance we could get a toggle (like a checkbox or something) somewhere in the profiler configuration screens/menus to
suppress this message?  I think it should be enabled by default but if it's getting in the way of your profiling (which
it is, in my case), I'd like to be able to turn it off.

addendum to my previous comment: 

This message also comes up periodically while my application is running, and if I'm not there to click "Yes" or "No"
(such as when I'm running it overnight), the VM Telemetry graph doesn't update properly.

What I'd really like to see is a "good faith" effort on the Profiler's part to update when it can, even if the
application periodically stops responding.  I can understand if it simply can't communicate with the application, but
having something less intrusive than a modal dialog would be nice... like a status bar or something.

reporter has given all requested info - removing INCOMPLETE

Unfortunately not for 6.7.

This issue seems related to https://visualvm.dev.java.net/issues/show_bug.cgi?id=346, however it is still present in NetBeans 6.9.

Is this dialog part of VisualVM and not NetBeans?  Should this issue be posted on their ticketing system, instead?

I'm also experiencing this problem in a different environment:

OS: Linux (2.6.32-24-generic)
Architecture: amd64 64bit
Java Home: /usr/lib/jvm/java-6-sun-1.6.0.20/jre
JVM: Java Hotspot(TM) 64-Bit Server VM (16.3-b01, mixed mode)

The problem persist even after increasing the amount of memory used from 512 to 1024, 1536 and 2048. It only happens when I try to use the Memory profiler, the CPU profiler works fine.

Any ideas?

(In reply to comment #10)
> I'm also experiencing this problem in a different environment:
> 
> OS: Linux (2.6.32-24-generic)
> Architecture: amd64 64bit
> Java Home: /usr/lib/jvm/java-6-sun-1.6.0.20/jre
> JVM: Java Hotspot(TM) 64-Bit Server VM (16.3-b01, mixed mode)
> 
> The problem persist even after increasing the amount of memory used from 512 to
> 1024, 1536 and 2048. It only happens when I try to use the Memory profiler, the
> CPU profiler works fine.
> 
> Any ideas?
Which version of NetBeans do you use? 
Which version of JDK is used for profiled application? I suggest to use 1.6.0_21 for profiled application. 16.0_21 fixed crash when taking memory snapshot. See <http://netbeans.org/bugzilla/show_bug.cgi?id=183107>. It would be great if you can provide reproducible test-case.

(In reply to comment #11)
> (In reply to comment #10)
> > I'm also experiencing this problem in a different environment:
> > 
> > OS: Linux (2.6.32-24-generic)
> > Architecture: amd64 64bit
> > Java Home: /usr/lib/jvm/java-6-sun-1.6.0.20/jre
> > JVM: Java Hotspot(TM) 64-Bit Server VM (16.3-b01, mixed mode)
> > 
> > The problem persist even after increasing the amount of memory used from 512 to
> > 1024, 1536 and 2048. It only happens when I try to use the Memory profiler, the
> > CPU profiler works fine.
> > 
> > Any ideas?
> Which version of NetBeans do you use? 
> Which version of JDK is used for profiled application? I suggest to use
> 1.6.0_21 for profiled application. 16.0_21 fixed crash when taking memory
> snapshot. See <http://netbeans.org/bugzilla/show_bug.cgi?id=183107>. It would
> be great if you can provide reproducible test-case.

I was using NetBeans 6.8. But now I started all over with NetBeans 6.9.1 and JDK 1.6.0_21, these are my specs showed by the About window:

   Product Version: NetBeans IDE 6.9.1 (Build 201007282301)
   Java: 1.6.0_21; Java HotSpot(TM) 64-Bit Server VM 17.0-b16
   System: Linux version 2.6.32-21-generic running on amd64; UTF-8; en_US (nb)

And these are the starting options in the etc/netbeans.conf:

netbeans_default_options="-J-client -J-Xmx1536m -J-XX:+UseConcMarkSweepGC -J-XX:+CMSClassUnloadingEnabled -J-XX:+CMSPermGenSweepingEnabled -J-Xss2m -J-Xms32m -J-XX:PermSize=32m -J-XX:MaxPermSize=200m -J-Dapple.laf.useScreenMenuBar=true -J-Dapple.awt.graphics.UseQuartz=true -J-Dsun.java2d.noddraw=true"


I started the memory profiler with these options selected: "Record both object creation and garbage collection", "Record stack trace for allocations" and "Track every object allocations" set to 50. And after some minutes of using my web application (project under test) it gets really slow and finally this message appeared on NetBeans:

"The profled application does not respond. Do you want to close the connection and stop profiling?"

I need to have it running for at least 30 minutes to take some snapshots and find out where the memory leak is...

Thanks in advance

It seems to be fixed. Please reopen if you are able to reproduce it with NetBeans 7.3 beta. Thanks.