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
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
Comments (7)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
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?
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
Petr777
Sep 10, 2019 08:39
Looks like unchecking "Stop Gradle daemons on exit" in "Preferences/External Tools" fixes this issue
Petr777
Sep 10, 2019 08:23
Exists in 2018.4.4f1
zach_peoplefun
Aug 29, 2019 14:41
Issue still exists in 2019.1.5f1