>>> 3. On a developer a machine the daemon could eat up a lot of memory and
>>> there seems to be no limit how many daemons can spawn. I have tried to
>>> decrease the problem by writing the plugin so, that it does not execute
>>> tasks concurrently (including loading of projects) unless for certain kind
>>> of tasks (run, debug). However, if the user starts two tasks with
>>> incompatible JVM arguments, there will be two daemons running and the
>>> processes will remain even after they are going idle. Do this a few times
>>> and you can effectively kill any pc. So my proposal is that at most only one
>>> idle daemon might run concurrently. If there are more, one must commit
>>> suicide.
>>
>>
>> You are talking about tasks from different Gradle builds?
>
>
> This is the reply from Attila:
>
> To clarify the 3rd point: It might be due to using multiple versions of
> Gradle but more likely it is because you started two gradle builds with
> incompatible jvm arguments; or simply, executed two builds in parallel (I
> expect one of the daemon to die when both builds complete). Executing two
> builds in parallel is something that is likely to happen when executing a
> "run" task (i.e.: you need to execute multiple apps in parallel).
I'm pretty sure we want to offer some ways to manage the daemon
processes. I'm not a fan of arbitrary synchronization rules (like one
daemon per project). Such rules can be implemented by the clients
themselves.
Cheers!
--
Szczepan Faber
Principal engineer@gradleware
Lead@mockito
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
