130

I observe "Remote System Explorer Operation" in Progress view of Eclipse after each save of Java file (so it might be related to compiling?). It makes the Eclipse unusable for 1 to 10 seconds. In some projects (of about the same size) it's quicker, in some it's slower.

I have no idea which plugin might be the cause for it. I have Build id: 20090920-1017. I have quite a few plugins installed.

I have tried turning all the remote systems to enabled=false under Preferences | Remote Systems (whatever it means). I didn't help.

Any idea how to solve it?

EDIT:

  1. It doesn't happen when Project | Build automatically is turned off. So it's some part of the building process.
Asclepius
  • 57,944
  • 17
  • 167
  • 143
Grzegorz Oledzki
  • 23,614
  • 16
  • 68
  • 106

13 Answers13

182

Here are the steps:

  1. Click on the Windows > Preferences menu
  2. Select General > Startup and Shutdown in the tree
  3. Uncheck RSE UI
  4. Select Remote Systems in the tree
  5. Uncheck Re-open Remote Systems view to previous state
  6. Restart Eclipse

Note: You must have Eclipse 4.3.1 (or newer) due to a bug on previous version

Nathan
  • 8,093
  • 8
  • 50
  • 76
Marckaraujo
  • 7,422
  • 11
  • 59
  • 97
  • Accepting this answer since it seems to be a solution to current generation of the problem. (I haven't observed the bug and the fix in particular) – Grzegorz Oledzki Apr 22 '14 at 07:53
  • tried all that, what finally worked for me was the last part - updating to luna (4.4.0) – theRiley Apr 13 '15 at 01:01
  • 11
    Every new version of the eclipse is worse than the previous one. More RAM, faster disks but the Eclipse is getting worse and worse – Igor Vuković Oct 11 '17 at 07:48
  • 1
    Now it's 2018. This issue is still not resolved! This didn't work for me. Try Q9703's: delete `RemoteSystemsTempFiles` from Windows -> Preferences -> -> General -> Workspace -> Build Order – AnthonyY Jul 10 '18 at 18:55
  • The combination between this answer and Q9703's one allows a really good improvement in Eclipse performance. RSE must be disabled and also the automatic builds of its own projects. – Alessandro C Nov 09 '18 at 08:49
  • I'm using Eclipse Kepler. I have followed the above solutions, but it didn't work for me – Satya P Jun 16 '20 at 12:50
  • It's 2021 and the problem is still in Neon. Happy anniversary – Jens Feb 23 '21 at 09:47
25

Here are the steps:

  1. Click on the Windows > Preferences menu
  2. Select General > Workspace > Build Order in the tree
  3. Uncheck Use default build order
  4. Select RemoteSystemsTempFiles
  5. Click Remove Project
  6. Click Apply and Close
Andrea
  • 6,032
  • 2
  • 28
  • 55
Q9703
  • 274
  • 3
  • 3
  • 1
    Brilliant -- as the year is now 2016, this should be the newly accepted answer. However, I do wonder what removing that from the build will break?! – Dave May 19 '16 at 15:18
  • 1
    What happens if you add new projects -- are they added automatically to that list? If not, this should not be the preferred way, since people will very probably forget to add the projects manually. What do you think? – Till Kolditz Aug 01 '17 at 15:09
9

This was driving me crazy too.

Thanks to this topic I got to understand it was the plugin RSE, but I could not uninstall the Remote System Explorer plugin tool either. I had to remove all the plugins whose name started by org.eclipse.rse in plugins/, it's working now.

Alexis Laporte
  • 515
  • 1
  • 4
  • 14
  • Thanks, I am on STS 3.9.3.RELEASE, this seems to solve my problem – pmverma Apr 01 '18 at 12:06
  • This seems to solve the issue, but in debug STS remains very slow, with continuing freezes. I think "Remote System Explorer Operation" is not the only fault. – Alessandro C May 24 '18 at 17:09
5

I'm having this issue also.

I have found that the operation is part of the Remote System Explorer plugin which comes packaged with SpringSource 3.3 (Kepler). Trying to figure out how to uninstall it now. Will post back here once I find it.

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 uninstall I'm still trying (the option to uninstall is greyed out for me in the installation details panel).

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

Solution
We've since moved to a Vanilla install of Eclipse Kepler and just added the plugins we require (excluding Remote System Explorer). This has fixed the issue.

diggersworld
  • 12,770
  • 24
  • 84
  • 119
5

Close the Git-Staging View !

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

user1484745
  • 59
  • 1
  • 3
3

I have experienced "Remote System Explorer Operation" tasks running on resource save.

Kepler + AspectJ + SpringSource In my case, it was caused by invalid aspectj pointcut definitions. I had 30 pointcuts and 4 of them referenced a deleted class. I have noticed blinking Spring AOP markers.

After I have fixed the pointcuts, the freezing stopped.

PJA
  • 61
  • 3
  • ya.. If there are any Aspect checks are blinking den, that will cause this issue. My issue( Same ) got resolved after fixing/delete that particular class. – Bandham Manikanta Apr 18 '18 at 17:05
3

I think I may have found a work-around for this issue...

  1. If the window pops up, close it then click the Stop button at the bottom
  2. Uncheck "Build Automatically" under Project
  3. Project | Build Project
  4. Check "Build Automatically"

Now, try what you were doing again.

user3418049
  • 131
  • 2
  • 2
1

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

This is with Eclipse 4.3 Kepler (2013/2014)

Find the all non-LOCAL items and Delete them. I could not see any DISABLE function.

For me this seems to stop the extra 1 to 3 second delay (on Intel i7 box) when saving with editor and an auto-build completes.

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.4M1+ might alleviate the problems, I have not yet tried this as I only run GA releases so will try when Kepler SR1 comes out in 7 days from now.

Darryl Miles
  • 4,576
  • 1
  • 21
  • 20
1

For me at this time for Spring Tool Suite 3.9.4. Release disabling remote system via preferences menu fixed the issue. Here is the reference that helped me. but after a while, the problem is there again!

mehdi mohammadi
  • 331
  • 3
  • 10
0

Switched to eclipse photon one week, didn't see the annoying "remote system...." any longer.

CQLI
  • 413
  • 4
  • 11
0

I was also experienced multiple remote system explorer operations while compiling a C++ project in eclipse (I'm using Nsight bu nvidia - eclipse based platform). After i did all the suggested solutions here, I still had the problem.

BUT- when i changed the -Wall option to -w option for the gcc compiler the problem disappeared.

GO TO - Project Properties -> Build-> Settings -> Tool settings tab-> gcc compiler -> warnings -> uncheck -Wall and check -w

The same goes for G++ Compiler.

CertainPerformance
  • 356,069
  • 52
  • 309
  • 320
Kobi M
  • 1
0

I also experienced "Remote System Explorer Operation" tasks running on resource save.

When using AspectJ Around method In my case, it was caused by Aspectj around method Spring AOP markers creation.

Delete the AspectJ Markers from the Eclipse Markers console system hang issue will be solved automatically.

Loga Nathan
  • 123
  • 1
  • 4
  • 14
-7

The issue disappeared after some update of the Eclipse libraries (still using the same build). So I guess the solution is to perform an update.

Grzegorz Oledzki
  • 23,614
  • 16
  • 68
  • 106
  • 1
    This "solution" does not help the rest of us! – Philippe Mar 26 '13 at 19:58
  • Same issue here. Solution don't really work. Shouldn't be marked as answer. – Sergey Karpushin Sep 07 '13 at 21:21
  • 1
    It did work for me three years ago. Now (2013) for some reason I see a lot of activity in the question, which probably might or might not be unrelated to the previous behavior. Anyway, I don't have a problem with selecting some other answer if it's proven to help people. – Grzegorz Oledzki Sep 21 '13 at 21:49