Description Laurent Masse-Navette 2020-03-23 12:14:35 EDT

Our servers recently upgraded from CentOS6 to CentOS7, and I figured I would give the new versions of eclipse a try since CentOS6 meant we could not upgrade beyond Neon.
I used the last version of the installer (2020.03) and selected CDT, as I am using Eclipse IDE for C++ development.
Everything went smoothly, except that when I look at the output of top, I see the following output:
Tasks: 299 total,   1 running, 297 sleeping,   1 stopped,   0 zombie
%Cpu(s):  0.0 us,  0.0 sy,  0.0 ni, 99.9 id,  0.0 wa,  0.0 hi,  0.0 si,  0.0 st
KiB Mem : 13173472+total, 12140486+free,  3201972 used,  7127888 buff/cache
KiB Swap: 13421772+total, 13255630+free,  1661424 used. 12777955+avail Mem 

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                              
 2676 xxxxxxx   20   0   98.3g 102416  55172 S   0.3  0.1   0:01.55 WebKitWebProces                                      
32506 xxxxxxx   20   0  108.6g   1.7g  51732 S   0.3  1.4   2:57.28 java                                                 

With Neon, Eclipse CDT was not creating such big processes. It is a problem for me as I am sharing the CPU and memory resources on a CPU farm with many other users, and we cannot afford to reserve so large amounts of resources just for running an IDE. Is this behavior expected, and is there a way to control the amount of memory that is reserved by the processes generated when launching eclipse?

Regards,

Laurent