Bug 559135 - [content assist] Execution exception in async mode
Summary: [content assist] Execution exception in async mode
Status: CLOSED DUPLICATE of bug 558921
Alias: None
Product: JDT
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.15   Edit
Hardware: PC Windows 10
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 531061
Blocks:
  Show dependency tree
 
Reported: 2020-01-13 18:28 EST by Wim Jongman CLA
Modified: 2020-01-14 01:50 EST (History)
1 user (show)

See Also:

Attachments
video (3.10 MB, video/mp4)
2020-01-13 18:28 EST, Wim Jongman CLA 		no flags Details
Video (3.07 MB, video/mp4)
2020-01-13 18:31 EST, Wim Jongman CLA 		no flags Details
prefs 1 (23.08 KB, image/png)
2020-01-13 18:31 EST, Wim Jongman CLA 		no flags Details
Prefs 2 (39.02 KB, image/png)
2020-01-13 18:32 EST, Wim Jongman CLA 		no flags Details
Logs (19.01 KB, application/octet-stream)
2020-01-13 18:32 EST, Wim Jongman CLA 		no flags Details
Show Obsolete (1) View All 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 Wim Jongman CLA 2020-01-13 18:28:31 EST 
Created attachment 281478 [details]
video

I found and execution exception in the log while using non blocking completion. See attached documents/
Comment 1 Wim Jongman CLA 2020-01-13 18:31:05 EST 
Created attachment 281479 [details]
Video

The first time nothing happens except the execution exception. The second time it gives an unhandled event loop exception.
Comment 2 Wim Jongman CLA 2020-01-13 18:31:42 EST 
Created attachment 281480 [details]
prefs 1
Comment 3 Wim Jongman CLA 2020-01-13 18:32:05 EST 
Created attachment 281481 [details]
Prefs 2
Comment 4 Wim Jongman CLA 2020-01-13 18:32:34 EST 
Created attachment 281482 [details]
Logs
Comment 5 Mickael Istria CLA 2020-01-14 01:50:17 EST 
Which version of org.eclipse.jdt.ui are you using?
Comment 6 Mickael Istria CLA 2020-01-14 01:50:50 EST 

*** This bug has been marked as a duplicate of bug 558921 ***