Community
Participate
Working Groups
Created attachment 202697 [details] Screencast I20110830-1241 Cocoa 32bit on 10.7 When I open a Java editor, do Navigate > Show in Breadcrumb, and then click an arrow in the breadcrumb, I see a gray palette window with a mini-titlebar flashing up before the breadcrumb dropdown opens. This is a strange bug that I can consistently reproduce in various builds (including e.g. 3.7.1RC3 M20110831-1030-macosx-cocoa-x86_64) as long as I'm in the host workbench. But I've never seen it in a runtime Eclipse instance. To hunt it down, I started a second eclipse workbench from the Terminal like this: ./eclipse -vmargs -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 In my dev workspace, I created a Remote Java Application debug configuration with port 5005. After I've prepared everything in the second workbench, I set a breakpoint in org.eclipse.jface.viewers.AbstractTreeViewer#inputChanged(...) on line 1526 at "tree.setRedraw(true);". The palette window flashes up inside that call when I step over it. Precisely, it's inside "window.orderBack(null);" here: Thread [main] (Suspended) Tree(Control).internal_new_GC(GCData) line: 2099 GC.<init>(Drawable, int) line: 171 GC.<init>(Drawable) line: 134 Tree.setScrollWidth(boolean, TreeItem[], boolean) line: 2918 Tree.setScrollWidth() line: 2911 Tree.setRedraw(boolean) line: 2906 AbstractTreeViewer$5.run() line: 1526 ProblemTreeViewer(StructuredViewer).preservingSelection(Runnable, boolean) line: 1443 ProblemTreeViewer(TreeViewer).preservingSelection(Runnable, boolean) line: 403 ProblemTreeViewer(StructuredViewer).preservingSelection(Runnable) line: 1404 ProblemTreeViewer(AbstractTreeViewer).inputChanged(Object, Object) line: 1517 ProblemTreeViewer(ContentViewer).setInput(Object) line: 280 ProblemTreeViewer(StructuredViewer).setInput(Object) line: 1690 BreadcrumbItemDropDown.showMenu() line: 337
The palette window also flashes up when I select a Java identifier in the editor and then press F2.
This is the same as bug#369599. I could not reproduce bug#369599 while self hosting either. I do not know what is the difference. The problem does not happen with N20120131-2000. *** This bug has been marked as a duplicate of bug 369599 ***