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.
It seems that if I invoke performance profiling of an applet with default settings - entire application, all classes it profiles only init thread of the applet (a thread calling AppletPanel.run()). So the profiler doesn't measure any ui action invoked from running applet. I think there should be measured at least eventdispatch thread too.
There is no reason, why other threads are not profiled. Please provide more information, attach applet, etc.
It is 100% reproducible in profiler dev builds. I cannot reproduce it in profiler 5.5. Steps to reproduce: 1. start profiling of attached applet 2. press increase, decrease buttons 3. take snapshot Result: snapshot does not contain method make called from events dispatching thread
Created attachment 32142 [details] applet
I suppose you are using "Entire Application" preset. This preset turns off the option to profile spawned threads and relies on root methods solely. As you don't have your event handling methods defined as root methods they are not instrumented and therefore not reported in snapshots. We are planning to introduce a more advanced system allowing different project types to use different profiling defaults (eg. it makes sense to profile spawned threads for applets, even for entire application as the application is typically pretty small).
ok, but the issue should stay opened until it is not fixed :). You can make it depends on some enhancement or task.
Fixed. From now for Profile File & CPU Entire Application all methods from the class & its inner classes and anonymous classes are used as root methods.
verified