[
https://issues.apache.org/jira/browse/LUCENE-9232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17039064#comment-17039064
]
Robert Muir commented on LUCENE-9232:
-------------------------------------
As far as abnormally long time (default is supposed to be 3 hours), I think it
might be related to closing/opening laptops lid and their Timer class that
governs when daemon will exit.
I actually didn't kill daemons until around 15:00. I tried to make sense of how
it was implemented there at a glance, but I was unsuccessful and have to get
moving today.
>From my experiments with the gradle integration of Eclipse IDE (they are
>short-lived because it thinks lucene projects have recursive dependencies?
>Maybe I am holding it wrong?), Eclipse spins up its own gradle daemon anyway
>for IDE purposes, with its own timeout. I have not looked into other IDEs or
>even where we are at with IDE integration in general. But it is something to
>consider here.
> 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
