Community
Participate
Working Groups
as per bug 398509 comment 73 ... I still see this occasionally in Eclipse 4.3.1. I select a variable name in Java source and it and its occurrences are highlighted. Then I click on another variable, but still the previous one is highlighted. alt-tab to another window and back "fixes" it: the new variable is highlighted. Eclipse Java EE IDE for Web Developers. Version: Kepler Service Release 1 Build id: 20130919-0819 Windows 7 Pro SP1 64 bit java version "1.7.0_25" Java(TM) SE Runtime Environment (build 1.7.0_25-b17) Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
Reproducible steps would be helpful.
Sorry, I have no clue what causes it. Just no I clicked an identifier and it was highlighted. Then I clicked another one in the same function and it was not highlighted. I clicked a third one and it was highlighted. Then I clicked the second one again, and now it finally worked. I notice this every day or two.
It still happens in Luna too: Eclipse IDE for Java Developers Version: Luna Service Release 2 (4.4.2) Build id: 20150219-0600 Windows 7 Pro SP1 64 bit java.vendor=Oracle Corporation java.vendor.url=http://java.oracle.com/ java.vendor.url.bug=http://bugreport.sun.com/bugreport/ java.version=1.8.0_45 java.vm.info=mixed mode java.vm.name=Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name=Java Virtual Machine Specification java.vm.specification.vendor=Oracle Corporation java.vm.specification.version=1.8 java.vm.vendor=Oracle Corporation java.vm.version=25.45-b02 Latest occurrence description: Suddenly it "stopped working". Placing the text cursor into a variable name (either by mouse click or navigation using the cursor keys) does not trigger its highlighting. Switching to another already opened file does not help, but alt-tab does. This is a fresh installation of Luna SR2, with subversive plugin (it is shipped with it, AFAIK), a new workspace with a single java project, saved to SVN.
Still happening in: Eclipse Java EE IDE for Web Developers. Version: Neon.2 Release (4.6.2) Build id: 20161208-0600 Windows 7 Enterprise SP1 64 bit java.vendor=Oracle Corporation java.vendor.url=http://java.oracle.com/ java.vendor.url.bug=http://bugreport.sun.com/bugreport/ java.version=1.8.0_121 java.vm.info=mixed mode java.vm.name=Java HotSpot(TM) 64-Bit Server VM java.vm.specification.name=Java Virtual Machine Specification java.vm.specification.vendor=Oracle Corporation java.vm.specification.version=1.8 java.vm.vendor=Oracle Corporation java.vm.version=25.121-b13
(In reply to David Balažic from comment #4) > Still happening in: > Version: Neon.2 Release (4.6.2) > Build id: 20161208-0600 Thanks for feedback, but in the future please don't increase "Version" field which is used to mark the *first* version where the problem appears.
I think this bug is related to bug 481815. For me this problem happens because there are a lot of "File Transport Cancel Handler" entries in the Progress view. You can only see them if you enable "Show sleeping and system operations" in the view preferences. They show up many times in the stack trace like this: ``` "Worker-90: File Transport Cancel Handler" #849 prio=5 os_prio=0 tid=0x00007fe1ec00b000 nid=0x5ff3 sleeping[0x00007fe17dbfe000] java.lang.Thread.State: TIMED_WAITING (sleeping) at java.lang.Thread.sleep(Native Method) at org.eclipse.equinox.internal.p2.transport.ecf.FileReader$CancelHandler.run(FileReader.java:157) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) ``` These entries seem to be the result of failed network activity: ``` !ENTRY org.eclipse.equinox.p2.transport.ecf 2 0 2018-12-24 09:00:50.096 !MESSAGE Connection to https://spring.io/blog.atom failed on spring.io: Temporärer Fehler bei der Namensauflösung. Retry attempt 0 started !STACK 0 java.net.UnknownHostException: spring.io: Temporärer Fehler bei der Namensauflösung at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method) at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:929) at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1324) at java.net.InetAddress.getAllByName0(InetAddress.java:1277) at java.net.InetAddress.getAllByName(InetAddress.java:1193) at java.net.InetAddress.getAllByName(InetAddress.java:1127) at org.apache.http.impl.conn.SystemDefaultDnsResolver.resolve(SystemDefaultDnsResolver.java:45) at org.apache.http.impl.conn.DefaultClientConnectionOperator.resolveHostname(DefaultClientConnectionOperator.java:263) at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:162) at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144) at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:134) at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:610) at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:445) at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:835) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.performConnect(HttpClientRetrieveFileTransfer.java:1084) at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer.access$0(HttpClientRetrieveFileTransfer.java:1075) at org.eclipse.ecf.provider.filetransfer.httpclient4.HttpClientRetrieveFileTransfer$1.performFileTransfer(HttpClientRetrieveFileTransfer.java:1071) at org.eclipse.ecf.filetransfer.FileTransferJob.run(FileTransferJob.java:74) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63) ``` The Mark Occurrences feature works again if I manually cancel all those entries in the Progress view.
No work will happen on this bug. If someone has steps, please reopen.
Steps to reproduce: 1. Disconnect your network connection or otherwise prevent DNS lookups 2. Do "Help->Check for updates" multiple times. It should display an error message because of the missing network connection. 3. Continue #2 until Mark occurrences first slows down to several seconds delay. 4. Continue #2 until Mark occurrences stops working at all. For me after 14 invocations of #2 the feature stops working completely. In my setup every check for updates produces four "File Transport Cancel Handler" entries in the Progress view. The check for updates is just a way to create ECF network activity. I guess any other way would work well. Maybe other hanging background tasks would block it as well.
Reopening based on comment 8. Kalyan, please have a look.
(In reply to Dani Megert from comment #9) > Reopening based on comment 8. > > > Kalyan, please have a look. I have not been able to reproduce this issue. @Jan: Can you please check on the latest 4.10 release and update your findings?
Yes, I can reproduce this problem on the latest build: Version: 2018-12 (4.10.0) Build id: 20181214-0600 on Ubuntu 18.10
Do you use lombok? IIRC this was one of the features that lombok breaks
I don't use lombok and I see this issue in: Eclipse IDE for Enterprise Java Developers. Version: 2019-03 (4.11.0) Build id: 20190314-1200
Detailed steps to reproduce on build I20191114-1800 (vanilla install, Ubuntu 19.04, jdk-13.0.1+9 OpenJ9, no extra plugins): 1. Open Progress View and in the View Menu enable Preferences -> Show sleeping and system operations 2. Disconnect your network connection or otherwise prevent DNS lookups 3. Enter Window -> Preferences -> Available Software Sites and select the entry "2019-12" 4. Do "Reload" multiple times. It should display an error message because of the missing network connection 5. Notice: Every failed network attempt leaves multiple "File Transport Cancel Handler" entries in the Progress view 6. Continue #4 until Mark occurrences first slows down to several seconds delay. 7. Continue #4 until Mark occurrences stops working at all. For me after about 20 invocations of #4 the feature stops working completely
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.
I can still reproduce this on the current build: Version: 2021-06 (4.20.0) Build id: 20210612-2011 on Ubuntu 20.04
