| Summary: | Conflict Commands | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Paul Webster <pwebster> |
| Component: | UI | Assignee: | Paul Webster <pwebster> |
| Status: | VERIFIED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | browe, john.arthorne, nsand.dev, pelder.eclipse, polomm, pwebster, shr31223, sptaszkiewicz, thatnitind |
| Version: | 3.6.2 | ||
| Target Milestone: | 4.3.1 | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 395642 | ||
| Bug Blocks: | |||
|
Description
Paul Webster
Resolution: It seems there's a problem in some JVMs that can cause org.eclipse.ui.internal.util.Util.compareIdentity(Object, Object) to fail (System.identityHashCode(left) - System.identityHashCode(right)). That means that sometimes the Set of active handlers (which uses this method in its comparator) can fail to find an existing activation (so it doesn't get removed from the set) and the next time a new one is added, you get this conflict. Ported as https://git.eclipse.org/r/15029 Paul, could you please review this? PW Released on 4.3 as https://git.eclipse.org/c/platform/eclipse.platform.ui.git/commit/?h=R4_3_maintenance&id=5552aec82a0ffc1e0abaa7918377c2dd46c9e5b1 Verified in build 4.3.0.M20130821-0800 |