| Summary: | Widget is disposed error in the .log file | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Olivier Thomann <Olivier_Thomann> |
| Component: | Compare | Assignee: | Platform-Compare-Inbox <platform-compare-inbox> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Michael.Valenta, Mike_Wilson, tomasz.zarna |
| Version: | 3.5 | ||
| Target Milestone: | 3.5 M6 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Olivier Thomann
This looks the same as bug 221583 and bug 260512 Thanks Michael, they all look pretty much the same indeed. Especially bug 260512 and bug 221583 look almost identical. I'm wondering why patch from bug 176447 didn't help (the same impression got Olivier[1]). The stack looks similar to what we can see here, but the fix was in TextMergeViewer.ContributorInfo.elementDirtyStateChanged()[2] method. So, is the patch from bug 221583[3] any good or should I rethink it (i.e. find a better place to put the check in)? [1] bug 221583, comment 0 [2] org.eclipse.compare.contentmergeviewer.TextMergeViewer.ContributorInfo.elementDirtyStateChanged(Object, boolean) [3] attachment 91737 [details] The patch looks reasonable. Note that adding checks to validate that widgets are not disposed is a good idea whenever code is expected to run asynchronously, but separate from that, it would be good if we understood *why* it happens in each case. <= That let's you identify any other potentially similar issues in related code. *** This bug has been marked as a duplicate of bug 221583 *** |