"Remote System Explorer Operation" causes a freeze within seconds

I observe the “Remote System Explorer Operation” in the Eclipse Progress view after each save of the Java file (so can this be related to compilation?). This makes Eclipse unusable for 1 to 10 seconds. In some projects (approximately the same size), this is faster, in some - slower.

I do not know which plugin might be causing this. I have a Build id: 20090920-1017 . I have quite a few plugins.

I tried to turn all remote systems into enabled=false in the "Settings" | Remote systems (whatever that means). I did not help.

Any idea how to solve it?

EDIT:

  • This does not happen when Project | Build automatically Project | Build automatically turned off. So this is part of the construction process.
+81
eclipse
Oct 27 '09 at 15:57
source share
9 answers

Go to MAC:

 Eclipse -> Preferences -> General -> Startup and Shutdown. 

-Uncheck RSE UI.

 Eclipse -> Preferences -> Remote Systems. 

-Uncheck Re-open the remote system system to the previous state.

Upgrade Eclipse to 4.3.1 (at least) due to a bug in the previous version.

Restart Eclipse and make it.

+118
Oct 11 '13 at 15:25
source share

Close Git -Staging View!

I had the same issue on my Eclipse 4.3 Kepler. After deleting (closing) the Git -Staging View problem was resolved!

+5
May 08 '14 at 5:57
source share

I have such a problem too.

I found that this operation is part of the Remote System Explorer plugin that ships with SpringSource 3.3 (Kepler) . Trying to figure out how to remove it now. I'll be back here when I find him.

Information on how to install can be found here (step 3): http://www.patrickjwaters.com/blog/2011-07-24/how-setup-eclipse-php-pdt-remote-system-explorer-theme -manager-and-drupal-plugins / 35

As for uninstalling, I'm still trying (the uninstall option will be highlighted for me in the installation details panel).

I tried Windows > Preferences > Remote Systems , setting everything to false, but the problem still occurred.

Decision
Since then, we switched to installing Vanilla Eclipse Kepler and simply added the plugins we need (except for Remote System Explorer). This fixed the problem.

+4
Jul 31 '13 at 10:26
source share

I experienced the "Remote System Explorer Operation" tasks that are performed while saving the resource.

Kepler + AspectJ + SpringSource In my case, this was caused by invalid pointcut aspectj definitions. I had 30 points, and 4 of them referred to the remote class. I noticed Spring AOP markers blinking.

After I fixed the points, the freeze stopped.

+2
Aug 14 '13 at 15:15
source share

I think I might have found a job for this problem ...

  • If a window pops up, close it, then click the Stop button at the bottom
  • Uncheck "Automatically create" in Project
  • Project | Assembly project
  • Check "Automatically create"

Now try to repeat what you did.

+2
Feb 18 '15 at 16:21
source share

Window -> Show View -> Other... -> Remote System Details (or maybe Remote Systems)

This is with Eclipse 4.3 Kepler (2013/2014)

Locate all items other than LOCAL and delete them. I have not seen any DISABLE function.

For me, this seems to stop the additional delay from 1 to 3 seconds (in the Intel i7 box) when saving using the editor, and the automatic build is completed.

http://forum.spring.io/forum/spring-projects/springsource-tool-suite/128402-sts-3-3-0-m2-and-remote-system-explorer-poor-performances hints that STS 3.4 M1 + can alleviate the problems, I have not tried it yet, since I am only launching the GA versions, so let's try it when Kepler SR1 comes out after 7 days.

+1
Sep 23 '13 at 21:10
source share

Go to the settings and delete the "RemoteSystemsTempFiles" project; Path: Windows → Preferences → Workspace → Build Order, uncheck "Use default build order", delete the project and apply it. Perhaps your question will be resolved.

+1
Mar 28 '16 at 9:14
source share

It drove me crazy.

Thanks to this topic, I realized that it was an RSE plugin, but I could not remove the Remote System Explorer plugin tool. I had to remove all plugins whose name was run by org.eclipse.rse in plugins/ , now it works.

0
Sep 13 '13 at 16:19
source share

The problem disappeared after some updating of the Eclipse libraries (the same assembly is still in use). Therefore, I assume that the solution should perform the upgrade.

-7
May 10 '10 at 8:32 a.m.
source share



All Articles