IntelliJ IDEA 2019.2.4 Ultimate is running a lot of process

Answered

I have IntelliJ IDEA 2019.2.4 Ultimate installed on mac running macOS Mojave 10.14.6, the IntelliJ build is #IU-192.7142.36, built on October 29, 2019.

I always have several windows open. For one of them, that has a big maven project, IntelliJ is spawning a lot of process for re-compiling it. Every now and then I see more than 100, and even more than 200 hundred, process running.

Is there anything I can do to avoid this? I've been working with IDEA for several years with this kind of maven projects and it's the first time I face this issue.

1
7 comments

I see the message within IntelliJ, in the bottom of the IDE. Regarding the issue IDEA-223667, how can I verify that I'm suffering the same issue?

Unfortunately, I can't use EAP versions for my job, I'd rather to use the ultimate license that my company provides us.

 

Thank you very much for your prompt response.

0

Please show what do you see exactly, what messages.

EAP does not require a license - you can install it temporarily and run at the same time with 2019.2 version.

0

Find attached a screenshot with the message "X process running"

If I click in this message, a "Background Tasks" screen appears:

 

And here it is an extract of the idea.log

2019-11-26 12:51:14,307 [18152714] INFO - ij.compiler.impl.CompileDriver - COMPILATION STARTED (BUILD PROCESS)
2019-11-26 12:51:14,324 [18152731] INFO - .ScalaCompilerReferenceService - [compiler indices] startIndexing. clean build: false
2019-11-26 12:51:14,336 [18152743] INFO - j.compiler.server.BuildManager - Using preloaded build process to compile /Users/.../Projects/.../[OFUSCATED] 
2019-11-26 12:51:14,350 [18152757] INFO - .ScalaCompilerReferenceService - [compiler indices] onCompilationFinish. success: true, active indexing phases: 0
2019-11-26 12:51:14,722 [18153129] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stdout]: Build process started. Classpath: /Applications/IntelliJ IDEA.app/Contents/plugins/java/lib/jps-launcher.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_231.jdk/Contents/Home/lib/tools.jar
2019-11-26 12:51:14,785 [18153192] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
2019-11-26 12:51:14,785 [18153192] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: SLF4J: Defaulting to no-operation (NOP) logger implementation
2019-11-26 12:51:14,785 [18153192] INFO - j.compiler.server.BuildManager - BUILDER_PROCESS [stderr]: SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
2019-11-26 12:51:16,307 [18154714] INFO - .ScalaCompilerReferenceService - [compiler indices] onCompilationStart. active indexing phases: 1
2019-11-26 12:51:16,746 [18155153] INFO - .ScalaCompilerReferenceService - [compiler indices] startIndexing. clean build: false
2019-11-26 12:51:17,899 [18156306] INFO - .ScalaCompilerReferenceService - [compiler indices] finishIndexing.
2019-11-26 12:51:17,979 [18156386] INFO - lij.compiler.impl.CompilerUtil - COMPILATION FINISHED (BUILD PROCESS); Errors: 0;  

0

It's getting worse as time passes:

 

601 processes running...!

0

Do you use any 3rd plugins? Try disabling if you do.

If problem remains it would be great if you try 2019.3 version as there were a lot of changes and this issue could be fixed.

If problem remains please file an issue at https://youtrack.jetbrains.com/issues/IDEA with IDE logs zipped. It would be also useful to have several jstack thread dumps of IDE process.

0

Thanks for the response, and for the tip for finding the solution.

 

The last plugin I installed is "Save Actions" (https://plugins.jetbrains.com/plugin/7642-save-actions/) it's a great plugin that I usually use to automatically format code, optimize imports and so on.


But I'm afraid I misconfigure it and MAYBE it's continuously changing the files and therefore, IntelliJ is trying to re-compile over and over and over.

 

After disabling the plugin, the IDE seems to work correctly.

 

I will double-check the plugin configuration in order to find out what is creating the issue.

 

But the problem is apparently solved, so you can close the ticket.

 

Thank you very much and best regards.

0

Please sign in to leave a comment.