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.

Bug 77900 - Review of jfluid
Summary: Review of jfluid
Status: NEW
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@profiler
Depends on:
Reported: 2006-06-14 13:37 UTC by ehucka
Modified: 2006-10-23 15:47 UTC (History)
0 users

See Also:
Issue Type: TASK
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description ehucka 2006-06-14 13:37:48 UTC
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.
Comment 1 ehucka 2006-06-15 08:06:37 UTC
I think implementation of issue 77639 - running profiler like a 'service'
(asynchronous) - should solve some parts of this issue.