IssueTracker

Found suddenly that this process has run for 3 hours !!

Shouldn't AS tell me that another builds was going on ?

By the way, it has never run for 3 hours before...

RG

Thinking back for three hours, I may have tried to stop the build process by clicking on the gray x behind "Gradle bulding..." message on the AS status bar. All seemed OK then...

RG

FYI theese are the AS related applications running during theese hours...

Saving project and restarting AS solved the problem so far...

Breaktrhrough !!

If you try to stop the build process when app:transformDexWithInstantRunSlicesApkForDebug is executing, the build will "hang" in "Execute transform". The AS statusbar might show "Gradle build finished in xxs yyyms.

To remedy this situation and do a recompile, you need to restart AS.

See picture of situation.

RG

How to reproduce:

1. Start building your project ("F10" or "Play button on action bar" or "Run -> Run App")
2. "You discovered an error in your code, and want to stop the build process".
3. Open your Build window, and show the processes ( not the log ).
3. Let the build process reach at least ":app:transformDexWithInstantRunSlicesApkForDebug"
4. Stop the build process by clicking the gray "cancel" button on far right of the status bar (x) (showing the build progress). See picture "notstopped_01"
5. The status bar shows "Stopping - Gradle Build Running". See picture "notstopped_02"
6. After a while the status bar shows nothing in the status bar in the middle, to the right the progressbar is disappeared and to the left following message is shown "Gradle build finished". See picture "notstopped_03"
7. The "task list" still shows that the process is running ":app:transformDexWithInstantRunSlicesApkForDebug".
8. If you try to Run the app again with "Run -> Run App " it will not build or start.

Build log also attached.

RG

In AS 3.1 Canary 9:

Starting Build First time. Stopping Build First time, same result as above (except pt 8.).

Starting Build Second time. New process is made, launching a process window showing both the "running" process (which is really stopped) and the new one.

Let the Second Build run out, and seems that this one is launched, but the first is still "running".

See picture.

RG

Sorry typo above, it was AS 3.2 Canary 3, not AS 3.1 Canary 9...

RG

Checking further down the line:

It is not necessary to stop the process at pt 3. int the reproduce description above. You could try to stop the process in any step, and process window shows "running" process still.

If you start and stops subsequently, more "processes are made", and I cannot say they will influence each other.

Restarting AS still seems to remedy the situation though.

RG

May relate to issue https://issuetracker.google.com/37102122

Reproduced in

Android Studio 3.2 Canary 2
Build #AI-173.4591728, built on February 7, 2018
JRE: 1.8.0_152-release-1024-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.9.0-5-amd64

Reproducible steps from comment #7 reproduces this issue 5/5

Does this error also happen against any of the 3.1 Beta builds?

Can reproduce on 3.1 beta 4

Thanks for finding this issue! The problem is that the build view does not get a finish event when the build is cancelled, causing any running task to appear as it is still running, even if it is not.

The fix for this issue will show any pending task as skipped when the build is cancelled (see attached image).

This bug still exists on Build: 3.2 Canary 4, AI-173.4615518, 201802220212.

RG

Yes, the fix was not included on 3.2 Canary 4 nor 3.1 beta 4. Next release will include it.

Yes, the fix will be available in Studio 3.1 RC1.

I suppose (as mentioned above) that AS 3.2 Canary 5+ will get it, not only the AS 3.1 path ?

Error still occures in AS Build: 3.2 Canary 5.

Additional IDE error occured:

===

No message
com.intellij.openapi.externalSystem.model.ExternalSystemException:
        at org.jetbrains.plugins.gradle.service.execution.GradleExecutionHelper.execute(GradleExecutionHelper.java:217)
        at com.android.tools.idea.gradle.project.build.invoker.GradleTasksExecutorImpl.invokeGradleTasks(GradleTasksExecutorImpl.java:394)
        at com.android.tools.idea.gradle.project.build.invoker.GradleTasksExecutorImpl.run(GradleTasksExecutorImpl.java:163)
        at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:713)
        at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$1(CoreProgressManager.java:157)
        at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:543)
        at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:488)
        at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:94)
        at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:144)
        at com.intellij.openapi.progress.impl.ProgressManagerImpl$2.run(ProgressManagerImpl.java:165)
        at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:315)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
        at java.lang.Thread.run(Thread.java:745)

===

was automatic reported.

RG

Thanks RG for letting us know!

I just checked the builds and unfortunately 3.2 canary 5 (build 173.4630681) does not include this fix yet. 3.2 Canary 6 will include it.

Confirming that fix is in Build: 3.2 Canary 6, and seems to work well !!

Thank you ! :D

RG