[
https://issues.apache.org/jira/browse/LUCENE-9232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039019#comment-17039019
]
Robert Muir commented on LUCENE-9232:
-------------------------------------
I think {{generate-defaults.gradle}} may have caused the leaked daemon here.
The first time you run the build, there's no gradle.properties, it forks a
daemon. it creates a new gradle.properties since that is what our build does.
The second time you run the build, there's now the gradle.properties so jvm
options have changed. daemon is "incompatible" so it forks another one.
now you have 2 daemons. and for me after many many hours they never go away
This isn't me doing anything at all: its simply the out of box experience.
> disable gradle daemon by default
> --------------------------------
>
> Key: LUCENE-9232
> URL: https://issues.apache.org/jira/browse/LUCENE-9232
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Robert Muir
> Priority: Major
>
> We should disable the gradle daemon by default: the user can opt-in by
> changing the properties file.
> If you forget to do this, you end out with leaked JVMs everywhere. It won't
> just leak one daemon, it will leak multiple ones.
> I ran {{ps}} on my laptop, surprised at 13:00 to find 2 leaked gradle jvms
> when I hadn't used the thing since 07:00.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
