Bug 515899 - JavaStackTracePageParticipant causes "Conflicting handlers" errors
Summary: JavaStackTracePageParticipant causes "Conflicting handlers" errors
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.7   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-27 08:29 EDT by Andrey Loskutov CLA
Modified: 2022-10-21 19:28 EDT (History)
1 user (show)

See Also:

Attachments
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 Andrey Loskutov CLA 2017-04-27 08:29:03 EDT 
Open Console view, click on the "+" drop-down and select "Java Stack Trace Console" to open new pane.

Now in JUnit view which has a failure click on the "Show Stack Trace in Console View" button. This opens a second "Java stack trace" console pane inside the Console view, and it seem that those two consoles (previous one and new one) don't play well together, I see error below every time I make the Console view visible:

Conflicting handlers for org.eclipse.jdt.ui.edit.text.java.format: {org.eclipse.jdt.internal.debug.ui.console.JavaStackTracePageParticipant$1@10ab14a2} vs {org.eclipse.jdt.internal.debug.ui.console.JavaStackTracePageParticipant$1@2e1a9116}
Comment 1 Dani Megert CLA 2017-04-27 09:57:41 EDT 
Do you have Code Recommenders installed? If so, bug 449454.
Comment 2 Andrey Loskutov CLA 2017-04-27 10:02:12 EDT 
(In reply to Dani Megert from comment #1)
> Do you have Code Recommenders installed? If so, bug 449454.

No, just SDK and very few hand selected plugins :-).
Comment 3 Eclipse Genie CLA 2020-07-12 18:30:25 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.

If you have further information on the current state of the bug, please add it. 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.
Comment 4 Eclipse Genie CLA 2022-10-21 19:28:02 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.

If you have further information on the current state of the bug, please add it. 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.