Community
Participate
Working Groups
I installed eclipse-jee-2019-12-R-win32-x86_64 (build id below) as I did with previous versions, recreated my workspace and then Eclipse (almost) froze. One thread used 100% of a CPU core and everything was orders of magnitude slower than normal. A quick check revealed that it is a memory (over)usage problem. So please, either: - reduce memory usage to normal (as it was in older versions) - increase the default -Xmx option value in eclipse.ini to something like 2GB As the first option is utopic I suggest implementing the second solution. Eclipse IDE for Enterprise Java Developers. Version: 2019-12 (4.14.0) Build id: 20191212-1212
Additional note: after increasing the Xmx parameter and restarting Eclipse, the problem was gone (well, except the gargantuan RAM consumption, but I have many gigabytes...)
Upon more inspection, the problem does not seem to be memory related. Sorry for false alert. What happened is: - download and extract eclipse-jee-2019-12-R-win32-x86_64.zip - add to eclipse.ini: -vm C:/Program Files/Java/jdk-11.0.6/bin/server/jvm.dll - start Eclipse - install plugin: Subclipse 4.3.0 with JavaHL 1.11.1 - checkout 5 (related) projects from SVN - select all 5 and in context menu select: Configure / Convert to Maven project After a while the Progress view shows a lot of entries named "Processing Build Path changes (Waiting)" 17 pieces and 3 times "JPA Project Change Event Handler (Waiting)". There is 12% CPU load (I have 4 cores x 2 SMT, so that is one fully loaded thread)- CPU is Intel i7-6820HQ After waiting for roughly 30 minutes I closed Eclipse (took about a minute). Then I increased Xmx to 3072m and reopened Eclipse and continued work, with no issues. Later I checked out some more project from SVN (to same workspace) and after clicking Configure / Convert to Maven project, the same problem happened: 100% load in one thread and the same items in Progress. It is still running, so any debug ideas are welcome.
Can you create a stack trace when the problem occurs, so that it can be further investigated? https://wiki.eclipse.org/How_to_report_a_deadlock
Created attachment 282008 [details] two stack traces for high CPU load I uploaded 3 stack traces: - one earlier, during the build process - one later, when the build is finished (according to the maven console) - and one when closing Eclipse, when the GUI window is already gone, but the process is still running I used jstack, as I have JDK 11 that has no jvisualvm.
Seems to me that the JobManager is overloaded, reassigning to Platform Runtime, they might have a better clue.
I believe I've seen this some years ago, that was or is Subclipse bug where it creates gazillions of jobs for refreshing after SVN updates. It created so many jobs, that we had even OOM due the max threads limit hit on Linux (around 4000). I believe even to patched that somewhere, or at least posted the patch proposal. If that is not merged, it is probably still somewhere in bugzilla. But isn't Subclipse dead?
Bug 489143 was it, but that should have been fixed.
It might be that in this case M2Eclipse is creating the huge number of jobs. David, how many Maven modules does your checkout contain?
(In reply to Andrey Loskutov from comment #6) > But isn't Subclipse dead? Apparently not. What else should I use? I'm aware of Subversive and I used both, but they both have their set of bugs, so I settled with Subclipse, especially after they fixed some of the most annoying bugs. (In reply to Rolf Theunissen from comment #8) > David, how many Maven modules does your checkout contain? Four. The fifth project just "bundles" those four, the pom.xml is just a <modules> element with 4 <module> children.
To try to find where all the jobs come from, can you enable job tracing? To enable debugging: 1. Create a file .options in the Eclipse install directory with this contents: org.eclipse.core.jobs/jobs=true 2. Start Eclipse with the -debug parameter This will create a trace.log file in the .metadata directory, with tracing about the jobs created. This should help in identifying which jobs are scheduled and by with plugin.
Created attachment 282336 [details] screenshot of dialog I did that and suddenly I got this error dialog: Missing node.js (see screenshot) I never saw it before.
Kind of strange that you get the error now, but there have been other unexpected interactions when enabling the logging. Could you be suffering for Bug 386171 (which seems not to be fixed or re-appeared)?
Don't know. There are too many comments to read.
TLDR: see last paragraph I now tried eclipse-jee-2020-09-R-win32-x86_64 and got the same issue. Eclipse IDE for Enterprise Java Developers (includes Incubating components) Version: 2020-09 (4.17.0) Build id: 20200910-1200 java.version=11.0.8 Steps: - unzip Eclipse - start it, create new workspace - install Subclipse (version 4.3.0, with JavaHL 1.14.0) - when asked restart Eclipse - open "SVN Repository Exploring" perspective - add a SVN repo - browse and select 5 projects and check them out - in Java EE perspective, view Project Explorer, select all projects and in right click menu select Configure / Convert to Maven project The same high CPU load happened and Eclipse GUI was very slow. After exiting, the Eclipse window disappeared, but the process was still running for several minutes, then I killer it (from Task Manager / End Task). Then I rerun Eclipse with the .options file and -debug parameter and a new workspace, but there the problem did not happen (or was not so intense). So I renamed the install folder, extracted eclipse again (into same pathname), added the .options file and repeated the above steps. This time the seemed to not be as severe as at first, but now I have logs. After the maven build ended, the message "JPA Project Change Event Handler" kept appearing in the status bar (bottom of the Eclipse window). When I exited Eclipse, it took a while. Lastly, I extracted again eclipse to a new folder (different path as before), and run it with the .options file and -debug option. This time the problem occurred in "full size". As the logs contains some private info, I don't want to post them publicly. Is there some private way to share them with developers? Alternatively I can to "anonymize" them.
I just got the same issue again with eclipse-jee-2022-12-R-win32-x86_64.zip , about menu says: Eclipse IDE for Enterprise Java and Web Developers (includes Incubating components) Version: 2022-12 (4.26.0) Build id: 20221201-1913 Steps: Steps: - unzip Eclipse - start it, create new workspace - install Subclipse (version 4.3.3, with JavaHL 1.14.0) - when asked restart Eclipse - open "SVN Repository Exploring" perspective - add a SVN repo - browse and select 15 projects and check them out - in Java EE perspective, view Project Explorer, select all those projects and in right click menu select Configure / Convert to Maven project (In reply to Rolf Theunissen from comment #10) > To try to find where all the jobs come from, can you enable job tracing? Still interested in a job trace?
> Still interested in a job trace? This bug report doesn't make sense without *thread dump* which you can create via jstack <java process id>.
Created attachment 288999 [details] thread dump (In reply to Andrey Loskutov from comment #16) > > Still interested in a job trace? > > This bug report doesn't make sense without *thread dump* which you can > create via jstack <java process id>. Attached.
A day later thing returned to normal: the Progress view show "No operations to display at this time." Everything appears to be normal.
