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 45449 - fix all places where AWT calls blocking operation
Summary: fix all places where AWT calls blocking operation
Status: RESOLVED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: Refactoring (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: issues@java
URL:
Keywords: PERFORMANCE, UMBRELLA
Depends on: 44097 44605 44663 45975 46071 46408 46412 46730
Blocks: 44492
  Show dependency tree
 
Reported: 2004-06-23 13:13 UTC by Pavel Buzek
Modified: 2007-04-03 18:02 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel Buzek 2004-06-23 13:13:10 UTC 
Ability to check when a mutex is owned and be
notified when available. I've heard comments that
the UI can block on exclusive mutex for example
when one wants to display source structure of a
java file and meanwhile another thread updates a
database somewhere. Imho there should be a way how
to check without blocking whether the mutex is
available and if not display just "Please wait..."
and fill the structures later.

Submitter is going to fix all places where AWT
calls blocking operation (using RequestProcessor).
(TCR)
Comment 1 Pavel Buzek 2004-06-23 13:28:57 UTC 
to correct myself - all places need to be analyzed and in the case
where AWT is knowingly calling MDR should be listed with explanation
Comment 2 Martin Matula 2004-07-26 10:26:57 UTC 
Changing to TASK since this is an umbrella - individual occurences of
the issue are filed separately.
Comment 3 Tomas Hurka 2004-09-07 09:28:59 UTC 
Fixed.