Community
Participate
Working Groups
Sometimes the compare editor for Java Elements (compare with other element) starts with correct regions but wrong connecting lines. (cf. bug 297316 comment 5 for the original observation). Inspecting this in the debugger revealed the following non-deterministic behaviour: When running without breakpoints the problem can be reproduced. When setting a few breakpoints the behaviour was correct. The breakpoint that seemed to make the difference was actually a watch point (Modification) on StyledText.verticalScrollOffset. This leads me to the conclusion that some widgets may get painted before the vertical scroll offset is correctly initialized. More specifically, I could observe: Method TextMergeViewer.handleResizeLeftRight(..) triggers method StyledText.scrollVertical(int,boolean) thus initializing the vertical scroll offset. However, before the method updates field StyledText.verticalScrollOffset, a call to scroll(..) may trigger update() which calls into the UI mainloop (gdk_window_process_updates()). Depending on event ordering (I assume -- this happens in native code) this may call back into doPaint() which invokes paintCenter() and paintSides() in an inconsistent state, since the verticalScrollOffset is used before assigned.
Created attachment 266296 [details] Screenshot of problem (wrong range) I see this with: Eclipse Java EE IDE for Web Developers. Version: Neon.2 Release (4.6.2) Build id: 20161208-0600 and AnyEditTools 2.6.1.201602151951 AnyEditTools.feature.group Andrey Loskutov I compare a selection in a Java file with the Clipboard content. Then I click the toolbar button to ignore white space. As seen on the screenshot, the marking on the left is wrong, the diff is after the last line, not before as indicated. It happens even if I close Eclipse and restart it and do the diff on the same data. Never noticed it elsewhere tho.
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.
