| Summary: | [quick assist] BadLocationException when applying proposal while preview is computed | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Markus Keller <markus.kell.r> | ||||
| Component: | UI | Assignee: | Markus Keller <markus.kell.r> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | daniel_megert, deepakazad | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | 3.6.2 | ||||||
| Hardware: | PC | ||||||
| OS: | Linux-GTK | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 293995 | ||||||
| Bug Blocks: | 195834 | ||||||
| Attachments: |
|
||||||
|
Description
Markus Keller
Created attachment 167632 [details]
Fix 1
Potential fix that implements the synchronization with a barrier and polling (to prevent the deadlock that occurs with a Java 'synchronized' monitor).
The patch is not trivial to understand and has not been tested intensively. We will probably live with the BadLocationException in 3.6 on GTK and only fix this in 3.7 (and 3.6.1, if successful). Committed the patch to HEAD. I've released the fix into R3_6_maintenance. Verified on Linux-GTK with M20101201-0800. (In reply to comment #5) > Verified on Linux-GTK with M20101201-0800. The fix got released on December 6. It looks like your verification steps are not too good. ;-) Verified in the code that the fix is in M20101215-0800. Deepak, please verify it again using M20101215-0800. |