@miha-x64 can you show us the overview page, so we could see daemon's JVM args? What OS do you use?

That looks like macOS.

Yes, it’s Mac. Arguments will not fit into a screenshot.

Arguments: --daemon-runFilesPath /Users/mike/Library/Application Support/kotlin/daemon --daemon-autoshutdownIdleSeconds=7200 --daemon-compilerClasspath /Users/mike/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-compiler-embeddable/1.1.0/782efe747ea43b08fa3d2c3184e83173934a7acb/kotlin-compiler-embeddable-1.1.0.jar:/Library/Java/JavaVirtualMachines/jdk1.8.0_112.jdk/Contents/Home/lib/tools.jar

@User uploaded a file:

And system props, please

(it has another pid because I’ve killed previous daemon and rebooted)

@miha-x64 This does not look like 1.1.1. Could you shutdown the daemon, and restart it with 1.1.1-eap-26?

and copy jvm args again 🙂

@User uploaded a file: System properties

@alexey.tsvetkov it’s 1.1, I’ve downgraded. I will upgrade, reboot, and copy this data then.

@miha-x64 yeah, please copy jvm args and system properties

Um, kinda stupid question. Build failed, "Compilation error. See log for more details”, where I can find them if I started Gradle wrapper via embedded command line?

If you mean Intellij terminal, then it should be in log above

@User uploaded a file: Looks not very informative...

@miha-x64 very strange, can you try from normal terminal?

@User uploaded a file:

Same in plain terminal.

@miha-x64 could you try to stop/kill all gradle daemons before starting the build?

jvisualvm shows no processes. Gradle outputs

Starting a Gradle Daemon, 3 stopped Daemons could not be reused, use --status for details

It will take five minutes more to crash again 🙂

May be you can find some more info in the logs. Usually

~/.gradle/daemon/<ver>/

Log contains some compilation (syntax etc) errors, which were not shown in IDE, and the same stack trace. I can post it to DM.

Yes, please

Quite some errors. It could be some conflicts with incremental compilation. Could you try to remove

build/

and/or run rebuild?

Same stack trace.

Are the errors from the log make any sense?

If not - I can think of only two sources of “stale” stuff - daemons (gradle and kotlin ones) and incremental compilation caches.

Yes, the errors are real, but IDE don’t shows them (I’m reinstalling it now), it just hangs; the project consists of five small classes, but daemon tries to compile it for five minutes...

Ok, let’s come back to the hanging problem. Could you, please, run compilation again on 1.1.1 and post here the jvm params and props of the compiler daemon process.

After that, could you, please, tell us a bit more about your network config. Are you using VPN now? Do you have many active network i-faces? Does localhost resolving works fast enough (e.g. via

nslookup

)?