Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 396141

Summary:	visible paint of scrolled-in content while scrolling in editor w/ cursor
Product:	[Eclipse Project] Platform	Reporter:	Matthias Dahl <ua_eclipse>
Component:	SWT	Assignee:	Platform-SWT-Inbox <platform-swt-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	ericwill, nobody
Version:	4.3	Keywords:	triaged
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:

Description Matthias Dahl

2012-12-09 09:26:38 EST

I am seeing rather annoying/disturbing scrolling behavior: If you scroll within the editor sideways or up-/downwards w/ the cursor, the currently visible content is displaced accordingly w/o the new content already attached. The gap created is filed in after the old content has been displaced and that paint event is clearly visible for less than a second... enough to be annoying. You can easily see (when you scroll sideways) the painting of the scrolled-in content from right to left or the other way around.

All of the following make no difference, meaning the exhibit the same behavior:

w/ and w/o plugins, w/ classic, default and gtk:
Eclipse 3.8, latest maintenance release of 4.2, latest 4.3 nightly

This is on (Gentoo) Linux x86_64 w/ gtk+ 2.24.14, cairo 1.12.8 and nvidia blob 304.64 (w/ GTX 470). It does not matter if you use OpenJDK (icedtea7) or the "official" Oracle JDK (7). The WM/DE (w/ and w/o composition) make no difference (tested w/ KDE 4.9.4 and XFCE 4.10).

I also tested this w/ GTK3 on the latest Eclipse 4.3 nightly (w/ SWT_GTK3=true) but that makes no difference as well.

Last but not least: Just for comparision, I made a test with IntelliJ IDEA 12 as well as PyCharm (which is basically the same codebase). Since both use swing instead of SWT, they work very smoothly wrt scrolling and do not show the same behavior.

Comment 1 Matthias Dahl

2012-12-11 04:49:50 EST

Some more info I forgot to add:

- this is limited to linux/GTK (Win f.e. is fine but (un)fortunately not my OS :P)
- scrolling w/ scrollbars is almost free of this problem (= hard to spot)
- scrolling by page-up/page-down has said "tearing"/repaint issues as well

Comment 2 Matthias Dahl

2012-12-21 08:30:48 EST

Some more things I tried:

1)
To rule out the nvidia blob, I grabbed a Fedora 18 beta kde live image which comes with nouveau, installed the latest openjdk and tried the latest 4.2 maintenance build w/o any plugins whatsoever.

It made absolutely no difference. :( The overall KDE desktop was surprisingly responsive but the Eclipse text editor still showed the same issue(s).

2)
On my regular desktop, I traced with cairo-trace and made some tests with cairo-perf-trace which did not show anything out of the ordinary.

3)
I downgraded Cairo from 1.12.8 to 1.10.2 since a lot of changes that went in on the way to 1.12.8 caused performance trouble even for the open source drivers.

Again, no difference at all.

4)
I downgraded pixman from 0.28.2 to 0.24.4. Also no difference at all.

Comment 3 Matthias Dahl

2013-08-22 09:28:50 EDT

Unfortunately, this is still the case w/ 4.3 final. Meanwhile I've switched to Emacs because this issue was too much of an annoyance/distraction.

For what it's worth: No program whatsoever shows this behaviour on my desktop, including IntelliJ/PyCharm which I tested exactly for this purpose with the same jvm and system. So this is definitely an Eclipse issue, imho.

Comment 4 Matthias Dahl

2013-09-17 10:18:58 EDT

Since it is now over 9 months after the initial report and this bug hasn't seen any official activity, I'd kindly and humbly ask for at least a note what could be the cause of this and if there is any chance of fixing this in the near future?

Thanks a lot in advance.

Comment 5 Eric Williams

2018-04-13 16:36:20 EDT

I do not see this issue, is it still reproducible? We had some fixes for scrolling in Neon which might have resolved this.

Comment 6 Eric Williams

2018-04-23 10:21:10 EDT

Please file a new bug report if the issue happens on GTK3.22 and a 4.8 I-build.