[
https://issues.apache.org/jira/browse/LUCENE-9232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039013#comment-17039013
]
Robert Muir commented on LUCENE-9232:
-------------------------------------
I didn't experiment with anything. I used all the defaults on a machine where
i'd never run gradle before, clean checkout!
It created 2 daemons that leaked and did not go away. My problem was the bad
defaults (daemon=on).
If it was disabled I wouldn't have had multiple JVMs with gigabyte+ heaps
leaked.
Sorry, I cannot just sit by and "not do anything" when we can disable such
waste so easily.
The daemon feature is not ready for prime-time: it must not be the default.
> 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
