Configuration.xml file not recreated after Deamon crash

(Stephan Petzchen) #1


Gradle seems to look for the old config file after a crash of the daemon and is not creating a new one. The old one is gone after the crash.
So a follow up issue to the already mentioned Daemon crash.

Win7, 64bit, 32GB RAM…my attachement in my last post holds all information about my configuration. C:\Users\Petzch.AndroidStudio1.2\system\compile-server\geoquiz_5cfcefef\gradle\configuration.xml (The system cannot find the path specified)
at Method)
at com.intellij.openapi.util.JDOMUtil.loadDocument(
at org.jetbrains.jps.gradle.model.impl.JpsGradleExtensionServiceImpl.getGradleProjectConfiguration(
at org.jetbrains.jps.gradle.model.impl.JpsGradleExtensionServiceImpl.getGradleProjectConfiguration(
at org.jetbrains.jps.gradle.model.impl.GradleResourcesTarget.computeRootDescriptors(
at org.jetbrains.jps.cmdline.BuildRunner.load(
at org.jetbrains.jps.cmdline.BuildSession.runBuild(
at org.jetbrains.jps.cmdline.BuildMain$MyMessageHandler$
at org.jetbrains.jps.service.impl.SharedThreadPoolImpl$
at java.util.concurrent.Executors$
at java.util.concurrent.ThreadPoolExecutor.runWorker(
at java.util.concurrent.ThreadPoolExecutor$

(Róbert Papp) #2

I support this, half of the AS/IDEA log is filled with this stack trace in: intellij\idea\log\build-log\build.log.*
Take “half” literally, each rolled log file is 20MB large, removing this exception and stacktrace makes it 10MB.
This is totally unnecessarily using the CPU and disk (which may be important for SSDs).

Is this a Gradle issue though, isn’t it IDEA?