Community
Participate
Working Groups
I got this in a Kepler 4.3.0 release: Release info: eclipse.buildId=4.3.0.I20130605-2000 java.version=1.7.0_17 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE Framework arguments: -product org.eclipse.epp.package.modeling.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.modeling.product Error message: Conflicting handlers for org.eclipse.jdt.ui.edit.text.java.refactor.quickMenu: {org.eclipse.jdt.internal.ui.actions.JDTQuickMenuCreator$1@43a61cbc} vs {org.eclipse.jdt.internal.ui.actions.JDTQuickMenuCreator$1@4ea89d56}
This still appears in Eclipse Luna 4.4.0 M2 Eclipse SDK Version: 4.4.0 Build id: I20130918-2000
(In reply to Udo Walker from comment #1) > This still appears in Eclipse Luna 4.4.0 M2 > > Eclipse SDK > > Version: 4.4.0 > Build id: I20130918-2000 Can you provide steps that reproduce this?
Can't reproduce using http://download.eclipse.org/eclipse/downloads/drops4/R-4.4-201406061215/
Probably it's fixed already. Since several months I did not get this message anymore.
I got this in a Luna 4.4.1 release: Conflicting handlers for org.eclipse.jdt.ui.edit.text.java.refactor.quickMenu: {org.eclipse.jdt.internal.ui.actions.JDTQuickMenuCreator$1@c334f3b} vs {org.eclipse.jdt.internal.ui.actions.JDTQuickMenuCreator$1@3aa02b54} eclipse.buildId=4.4.1.M20140925-0400 java.version=1.8.0_20 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=ja_JP Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product
*** Bug 445984 has been marked as a duplicate of this bug. ***
*** Bug 451455 has been marked as a duplicate of this bug. ***
The conflicts come from wrong activations and not from wrong contributions in JDT.
*** Bug 452012 has been marked as a duplicate of this bug. ***
*** Bug 452432 has been marked as a duplicate of this bug. ***
*** Bug 452433 has been marked as a duplicate of this bug. ***
*** Bug 452434 has been marked as a duplicate of this bug. ***
*** Bug 452435 has been marked as a duplicate of this bug. ***
*** Bug 452436 has been marked as a duplicate of this bug. ***
I was redirected to this bug as the error reports tool reported these handler conflicts: !ENTRY org.eclipse.ui 4 4 2014-12-23 17:58:26.018 !MESSAGE Conflicting handlers for org.eclipse.compare.selectNextChange: {ActionH andler(org.eclipse.compare.contentmergeviewer.TextMergeViewer$37@172811e)} vs {A ctionHandler(org.eclipse.compare.contentmergeviewer.TextMergeViewer$37@7af0e8)} !ENTRY org.eclipse.ui 4 4 2014-12-23 17:58:26.207 !MESSAGE Conflicting handlers for org.eclipse.compare.selectPreviousChange: {Act ionHandler(org.eclipse.compare.contentmergeviewer.TextMergeViewer$38@12ce364)} v s {ActionHandler(org.eclipse.compare.contentmergeviewer.TextMergeViewer$38@4debd )} !ENTRY org.eclipse.ui 4 4 2014-12-23 17:58:26.230 !MESSAGE Conflicting handlers for org.eclipse.compare.ignoreWhiteSpace: {ActionH andler(org.eclipse.compare.internal.ChangePropertyAction@14da5dc)} vs {ActionHandler(org.eclipse.compare.internal.ChangePropertyAction@c44172)} !ENTRY org.eclipse.ui 4 4 2014-12-23 17:58:26.253 !MESSAGE Conflicting handlers for org.eclipse.ui.edit.text.toggleShowWhitespaceCharacters: {ActionHandler(org.eclipse.compare.internal.ShowWhitespaceAction@1152863)} vs {ActionHandler(org.eclipse.compare.internal.ShowWhitespaceAction@ea217)} !ENTRY org.eclipse.ui 4 4 2014-12-23 17:58:26.276 !MESSAGE Conflicting handlers for org.eclipse.ui.editors.lineNumberToggle: {ActionHandler(org.eclipse.compare.internal.TextEditorPropertyAction@f11e13)} vs {ActionHandler(org.eclipse.compare.internal.TextEditorPropertyAction@1ed9bef)} In my case this sequence was the typical signal that the workbench needs a restart due to a closed but leaked compare editor. Not sure if there's a real connection to this bug.
> Not sure if there's a real connection to this bug. If you think your stacktrace did not relate to this error please let me know (send me the report by email please). In case the *message* was (quite) different, this version of the error reporter merges errors with similar stacktraces and ignores different messages iff the trace is similar. I'm working on a version that allows to configure this on a per-report basis.
(In reply to Marcel Bruch from comment #16) > > Not sure if there's a real connection to this bug. > > If you think your stacktrace did not relate to this error please let me know > (send me the report by email please). In case the *message* was (quite) > different, this version of the error reporter merges errors with similar > stacktraces and ignores different messages iff the trace is similar. I'm > working on a version that allows to configure this on a per-report basis. Comment 15 contains all the additional info I could find in my .log. Anything particular missing from it?
(In reply to Stephan Herrmann from comment #17) > Comment 15 contains all the additional info I could find in my .log. > Anything particular missing from it? A stacktrace would be the ultimate information I'd need to say whether the reporter made failure or works as intended. But AFAICT it works as intended: Markus merged Bug 445984 (created by the error reporter) with this one. The reporter respects this information and sends users to the "root" bug report instead to send him to the the closest automated(!) report. The messages you provide look similar to those in bug 445984 and the other duplicates. Thus I think it's correct that the reporter send you here. HTH.
