Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pmd plugin greatly slows down project import #31

Closed
farnetto opened this issue Dec 27, 2017 · 5 comments
Closed

pmd plugin greatly slows down project import #31

farnetto opened this issue Dec 27, 2017 · 5 comments

Comments

@farnetto
Copy link

The pmd-eclipse-plugin slows down the project import greatly, apparently because it is invoked many times and/or runs in parallel. This problem seems to have gotten worse and become severe with Eclipse Oxygen, so much so that this Eclipse release is unusable for us.
Attached is a logfile showing the problem. This shows the process when importing only one small (maven) project with only 87 files.
pmd-eclipse.log

@farnetto
Copy link
Author

m2e generated .project file attached
.project.txt

@farnetto
Copy link
Author

This doesn't seem to be a specific problem with the PMD plugin. The project import starts many full builds at once - eight in the screenshot attached - which lead to just as many full executions of checkstyle, PMD etc. Is this problem with m2e or with oxygen in general? Are there other open issues in those projects dealing with it? Any tips much appreciated.
grafik

@farnetto
Copy link
Author

Problem slightly improved by saving .pmdruleset.xml outside of project in another directory. That way PMD doesn't get called multiple times per project. Method EclipsePmdProjectConfigurator#createOrUpdateEclipsePmdConfiguration modified for this.

The bigger problem still exists, and that is a huge memory leak that eventually exhausts virtual memory on the machine. Issue described in more detail here: https://stackoverflow.com/questions/49852097/pmd-memory-leak

@farnetto
Copy link
Author

Upgrade to 4.0.16 doesn't solve the problem.

@adangel
Copy link
Member

adangel commented Jan 12, 2019

@farnetto The memory problem should be fixed with 4.0.17 via #52 . Can you update the plugin and try again? If you still see the problem, please reopen this issue. Thanks!

@adangel adangel closed this as completed Jan 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants