Bug 517730 - Undiagnosed CCE
Summary: Undiagnosed CCE
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.7   Edit
Hardware: PC Windows NT
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2017-06-02 11:12 EDT by Ed Willink CLA
Modified: 2020-04-05 15:33 EDT (History)
1 user (show)

See Also:


Attachments
Console log (786.10 KB, text/plain)
2017-06-02 11:40 EDT, Ed Willink CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ed Willink CLA 2017-06-02 11:12:04 EDT
RC2: I am getting many (20 in the same minute) CCE error log entries for org.eclipse.ui, but the detail only identifies 
Unhandled event loop exception

java.lang.ClassCastException

without a stack trace.

Diagnosis is therefore rather hard.
Comment 1 Andrey Loskutov CLA 2017-06-02 11:15:43 EDT
Can you provide steps to reproduce & the error log file please?
Comment 2 Ed Willink CLA 2017-06-02 11:40:49 EDT
Created attachment 268726 [details]
Console log
Comment 3 Ed Willink CLA 2017-06-02 11:41:28 EDT
No, but it should be possible to search the code for "Unhandled event loop exception" and find the code path on which the stack trace is discarded.

(This bug is for the CCE diagnosis failure, not the CCE origin.)

The relevant entries are:

!ENTRY org.eclipse.ui 4 0 2017-06-02 12:10:43.169
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.ClassCastException

!ENTRY org.eclipse.ui 4 0 2017-06-02 12:10:43.200
!MESSAGE Unhandled event loop exception
!STACK 0
java.lang.ClassCastException

Full log attached:
Comment 4 Eclipse Genie CLA 2020-04-05 15:33:39 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.