Search Issue Tracker

Fixed in 2018.1.X

Fixed in 2017.4.X, 2018.2.X

Votes

0

Found in

2017.3.1p2

Issue ID

1041385

Regression

No

Do Not Kill other gradle daemons when build completes

Mobile

-

Do not kill other instances of gradle when a gradle build completes.

We build mutiple android projects on the same build machine. When we build two or more Android builds, the first Android build will send out a command to shutdown all other gradle builds running. We see the following from the closed builds:

Gradle build daemon has been stopped: stop command received

Log in to vote on this issue

Comments (7)

  1. LostBoyRadPaisley

    Jan 07, 2020 22:44

    How can I toggle this setting via a build script? Or make sure this setting is saved for all my projects?

  2. daniel-hagstrom

    Nov 08, 2019 12:49

    Hey. I'm seeing this issue in several versions where as far as I can read the "Fixed in 20xx.x" says it should be fixed. I've gone over a couple of our projects in-house, and these are my results. The detection method I used was naive; I've looked for the "Stop Gradle daemons on exit" in Preferences->External Tools. If that option didn't exist, I treated that version as "not fixed" for this "table".

    Version, Fixed according to this ticket, Toggle exists in Preferences
    2017.3.1f1, No, No
    2017.4.18f1, Yes, No
    2017.4.26f1, Yes, No
    2018.3.7f1, Yes, No
    2018.3.8f1, Yes, No
    2018.4.0f1, Yes, Yes
    2018.4.11f1, Yes, Yes
    2018.4.8f1, Yes, Yes
    2019.2.2f1, Yes, Yes

  3. Petr777

    Sep 10, 2019 08:39

    Looks like unchecking "Stop Gradle daemons on exit" in "Preferences/External Tools" fixes this issue

  4. Petr777

    Sep 10, 2019 08:23

    Exists in 2018.4.4f1

  5. zach_peoplefun

    Aug 29, 2019 14:41

    Issue still exists in 2019.1.5f1

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues