Community
Participate
Working Groups
Version: 2018-09 (4.9.0) Build id: 20180917-1800 While scrolling through code the whole text freezes. It only catches on once I let go of the touchpad. Many other users have reported this issue on other sites, some even date back a year or more. Still this issue persists. I am on Windows 10 using a precision trackpad.
Please try to capture some thread dumps, see https://wiki.eclipse.org/How_to_report_a_deadlock if you need to keep the finger on the touchpad for this issue, consider running jstack in a loop with a short delay in between.
!SESSION 2018-11-01 13:08:33.157 ----------------------------------------------- eclipse.buildId=4.9.0.I20180906-0745 java.version=11.0.1 java.vendor=Oracle Corporation BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE Framework arguments: -product org.eclipse.epp.package.java.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product -consolelog !ENTRY org.eclipse.mylyn.bugzilla.core 4 0 2018-11-01 13:08:33.907 !MESSAGE FrameworkEvent ERROR !STACK 0 org.osgi.framework.BundleException: Could not resolve module: org.eclipse.mylyn.bugzilla.core [282] Unresolved requirement: Require-Bundle: org.apache.xmlrpc -> Bundle-SymbolicName: org.apache.xmlrpc; bundle-version="3.0.0.v20100427-1100" org.apache.xmlrpc [71] Unresolved requirement: Import-Package: javax.xml.bind Unresolved requirement: Require-Bundle: org.eclipse.mylyn.commons.xmlrpc; bundle-version="[3.8.0,4.0.0)" -> Bundle-SymbolicName: org.eclipse.mylyn.commons.xmlrpc; bundle-version="3.24.2.v20180904-2231"; singleton:="true" org.eclipse.mylyn.commons.xmlrpc [299] Unresolved requirement: Require-Bundle: org.apache.xmlrpc; bundle-version="[3.0.0,4.0.0)" -> Bundle-SymbolicName: org.apache.xmlrpc; bundle-version="3.0.0.v20100427-1100" at org.eclipse.osgi.container.Module.start(Module.java:447) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1685) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1664) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1627) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1558) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343) !ENTRY org.eclipse.mylyn.bugzilla.ui 4 0 2018-11-01 13:08:33.918 !MESSAGE FrameworkEvent ERROR !STACK 0 org.osgi.framework.BundleException: Could not resolve module: org.eclipse.mylyn.bugzilla.ui [284] Unresolved requirement: Require-Bundle: org.eclipse.mylyn.bugzilla.core; bundle-version="[3.8.0,4.0.0)" -> Bundle-SymbolicName: org.eclipse.mylyn.bugzilla.core; bundle-version="3.24.2.v20180905-0003"; singleton:="true" org.eclipse.mylyn.bugzilla.core [282] Unresolved requirement: Require-Bundle: org.apache.xmlrpc -> Bundle-SymbolicName: org.apache.xmlrpc; bundle-version="3.0.0.v20100427-1100" org.apache.xmlrpc [71] Unresolved requirement: Import-Package: javax.xml.bind Unresolved requirement: Require-Bundle: org.eclipse.mylyn.commons.xmlrpc; bundle-version="[3.8.0,4.0.0)" -> Bundle-SymbolicName: org.eclipse.mylyn.commons.xmlrpc; bundle-version="3.24.2.v20180904-2231"; singleton:="true" org.eclipse.mylyn.commons.xmlrpc [299] Unresolved requirement: Require-Bundle: org.apache.xmlrpc; bundle-version="[3.0.0,4.0.0)" -> Bundle-SymbolicName: org.apache.xmlrpc; bundle-version="3.0.0.v20100427-1100" at org.eclipse.osgi.container.Module.start(Module.java:447) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1685) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1664) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1627) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1558) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343) !ENTRY org.eclipse.mylyn.commons.xmlrpc 4 0 2018-11-01 13:08:33.930 !MESSAGE FrameworkEvent ERROR !STACK 0 org.osgi.framework.BundleException: Could not resolve module: org.eclipse.mylyn.commons.xmlrpc [299] Unresolved requirement: Require-Bundle: org.apache.xmlrpc; bundle-version="[3.0.0,4.0.0)" -> Bundle-SymbolicName: org.apache.xmlrpc; bundle-version="3.0.0.v20100427-1100" org.apache.xmlrpc [71] Unresolved requirement: Import-Package: javax.xml.bind at org.eclipse.osgi.container.Module.start(Module.java:447) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1685) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1664) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1627) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1558) at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1) at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:233) at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:343) org.eclipse.m2e.logback.configuration: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized. org.eclipse.m2e.logback.configuration: Logback config file: C:\Users\Alessandro\eclipse-workspace\.metadata\.plugins\org.eclipse.m2e.logback.configuration\logback.1.9.1.20180912-1601.xml SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [bundleresource://517.fwk372898106:1/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [bundleresource://517.fwk372898106:2/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder] org.eclipse.m2e.logback.configuration: Initializing logback !ENTRY org.eclipse.mylyn.tasks.core 4 0 2018-11-01 13:08:46.651 !MESSAGE Unexpected error while loading repository template extensions !SUBENTRY 1 org.eclipse.mylyn.tasks.core 4 0 2018-11-01 13:08:46.654 !MESSAGE Could not load repository template extension contributed by 'org.eclipse.mylyn.bugzilla.ide' with connectorKind 'bugzilla' !ENTRY org.eclipse.egit.ui 2 0 2018-11-01 13:08:50.053 !MESSAGE Warning: The environment variable HOME is not set. The following directory will be used to store the Git user global configuration and to define the default location to store repositories: 'C:\Users\Alessandro'. If this is not correct please set the HOME environment variable and restart Eclipse. Otherwise Git for Windows and EGit might behave differently since they see different configuration options. This warning can be switched off on the Team > Git > Confirmations and Warnings preference page.
java version "11.0.1" 2018-10-16 LTS Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS) Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode)
Yes this issue happens only if I scroll with to fingers and keep my fingers on the touchpad. If I just "flick" one time, it scrolls more smoothly.
The logged errors should be reported to mylyn. Those just exemplify that "Import-Package: javax.xml.bind" is not sufficient when running on JDK 11, because that package has been removed and a separate library must be included. Still I have no idea what keeps your cpu busy during scrolling. Please see comment 1.
Maybe it is a misunderstanding: My CPU is not busy while scrolling, if I put up the task manager right next to Eclipse and start scrolling, it stays at around 5% CPU load. Still, the scrolling animation is extremeley choppy and often times non existent: when i start scrolling with two fingers nothing happens, once i let go of the touchpad the window where I see my code changes and it now shows the part where I have scrolled to. This is extremely annoying since I can't see how far I have scrolled and it makes it very difficult to scroll up and down quickly if I need to check something that's at the beginning of the page. From what I have found out IntelliJ seems to have (or used to have I read a one year old bug report) the same problem. It cannot handle the way scrolling works on precision touchpads and just freezes the whole image. This seems to be the same reported issue: https://superuser.com/questions/1329226/trackpad-lag-when-scrolling-through-eclipse-code
(In reply to Alessandro Escher from comment #6) > Maybe it is a misunderstanding: > My CPU is not busy while scrolling, if I put up the task manager > right next to Eclipse and start scrolling, it stays at around 5% CPU load. OK, so cpu is not doing much, understood. But still we have no idea what is happening unless you provide some thread dumps. Even if the system is not busy it would tell us where exactly it hangs. I will leave the bug an "info needed" until we have those thread dumps :) Regarding the IntelliJ bug report: can you see if it has been fixed? Is it s.t. that the tool *can* fix or is it perhaps hanging in the driver of your touchpad?
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. If you have further information on the current state of the bug, please add it. 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.
Please reopen with more details if it's still an issue.
