Bugzilla – Full Text Bug Listing
| Summary: | Possible Deadlock at IForm#waitFor | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Claudio Guglielmo <claudio.guglielmo> | ||||
| Component: | Scout | Assignee: | Andreas Hoegger <Andreas.Hoegger> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | Andreas.Hoegger, zimmermann | ||||
| Version: | unspecified | Flags: | zimmermann:
indigo+
zimmermann: juno+ |
||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 199911 [details]
Patch to resolve the bug.
Patch applied on trunk and Indigo RC1. Thank you Claudio. shipped with scout 3.7.1 Comment on attachment 199911 [details]
Patch to resolve the bug.
moved iplog flag from bug to patch
|
Build Identifier: 3.7.0 The following code leads to a deadlock: ClientSyncJob closeJob = new ClientSyncJob("Close", ClientSyncJob.getCurrentSession()) { @Override protected void runVoid(IProgressMonitor monitor) throws Throwable { form.doClose(); } }; closeJob.schedule(); form.start(new FormHandler()); form.waitFor(); Expected result: Closing the form releases the lock. Instead waitFor blocks forever. I know it is not a real life example. Nevertheless it should be fixed. Reproducible: Always