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.
In my opinion jfluid and using of its features in profiler needs a review focused on stability and safety. From my point of view there is needed: 1. redesign handling of user events between ui and jfluid - AWT thread cannot be blocked by some model/jfluid activity (network connecting etc.) 2. review usage of monitors in jfluid - there are a few random deadlocks of profiled application 3. review or redesign dependences of ui on jfluid activities - ui of whole ide cannot be slowed-down by slow connection to profiled application 4. review work flow of user actions, redefine which activity should block which actions - e.g. modify profiling uses two progress bars,one modal and one non-modal and leaves users to invoke actions ending by deadlock - take snapshot 5. make profiling agent more controllable - agent should be finished automatically after connection or other errors - there can never stay profiling process running on background after succes or failed profiling 6. cleanup old parts of code - startup profiling, maybe code region etc.
I think implementation of issue 77639 - running profiler like a 'service' (asynchronous) - should solve some parts of this issue.