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 93140 - Unsynchronize NativeExecutor.run
Summary: Unsynchronize NativeExecutor.run
Status: RESOLVED INVALID
Alias: None
Product: cnd
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Thomas Preisler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-24 21:47 UTC by _ gordonp
Modified: 2008-02-25 00:18 UTC (History)
0 users

See Also:
Issue Type: DEFECT
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 _ gordonp 2007-01-24 21:47:44 UTC 
Minor performance issue. Since NativeExecutor is used once, the run method
shouldn't need to be synchronized. However, I'd rather defer this until
after the Sun Studio IDE EA build.
Comment 1 _ gordonp 2008-02-20 00:20:09 UTC 
I think its safe to unsynchronize, but I'll defer to Thomas (he's got another NativeExecutor
bug).
Comment 2 Thomas Preisler 2008-02-25 00:18:46 UTC 
Well, we (CND) use NativeExecutor once but it is a public method and is used by other components like advanced tools, dbxgui, and d-light so it is safest to 
keep it synchronized. If the same instance of NativeExecutor is called multiple times, there is a risk of them clobbering each other if not synchronized.

Once we get around to finalize a public and stable API, we could un-synchronize it and document it usage.

Anyway, I don't think this is p2.