Netbeans 5.0 beta 2, Profiler Milestone 11, JDK 1.5.0_04/_06, Solaris (cannot 
reproduce on Windows & Linux):

Steps to reproduce:

1/ Create new sample project TomcatServletExample, run it normally using Run 
Main Project action, then stop the server from Runtime tab

2/ Click Attach Profiler, setup Tomcat 5.5 for local direct attach, installdir 
<nb_installdir>/enterprise2/catalina... and base dir <nb_userdir>catalina..., 
let the wizard start Tomcat automatically

3/ Choose CPU profiling, entire app, all classes, open Live results window 
during server startup, take snapshot after the server starts

4/ Detach Profiler and let the Tomcat stop when detaching. Then start Tomcat 
from AttachWizard using the last used settings

5/ Choose memory profiling, alloc only, stack traces. Click Attach, here the 
exception occurs.

The scenario reproduces the bug also vice versa - first profiling Memory, then 
CPU.


CPU -> Memory:

java.lang.NullPointerException
	at org.netbeans.modules.profiler.LiveResultsWindow.checkIfResultsExist
(LiveResultsWindow.java:428)
	at org.netbeans.modules.profiler.LiveResultsWindow.access$700
(LiveResultsWindow.java:57)
	at org.netbeans.modules.profiler.LiveResultsWindow$5.run
(LiveResultsWindow.java:352)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:471)
[catch] at org.openide.util.RequestProcessor$Processor.run
(RequestProcessor.java:904)


Memory -> CPU:

java.lang.NullPointerException
	at org.netbeans.modules.profiler.LiveResultsWindow.checkIfResultsExist
(LiveResultsWindow.java:432)
	at org.netbeans.modules.profiler.LiveResultsWindow.access$700
(LiveResultsWindow.java:57)
	at org.netbeans.modules.profiler.LiveResultsWindow$5.run
(LiveResultsWindow.java:352)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:471)
[catch] at org.openide.util.RequestProcessor$Processor.run
(RequestProcessor.java:904)