[jira] [Commented] (OFBIZ-11954) Expiring Daemon because JVM heap space is exhausted

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-11954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17178466#comment-17178466 ]

Jacques Le Roux commented on OFBIZ-11954:
-----------------------------------------

Using --no-daemon fixes the issue/

Reading https://docs.gradle.org/6.5.1/userguide/gradle_daemon.html may also explain why we get an increasing space on demo server due to daemon though we are always using --no-daemon  when running any task! I'll digg that...

> Expiring Daemon because JVM heap space is exhausted
> ---------------------------------------------------
>
>                 Key: OFBIZ-11954
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-11954
>             Project: OFBiz
>          Issue Type: Bug
>          Components: Gradle
>    Affects Versions: Trunk
>            Reporter: Jacques Le Roux
>            Assignee: Jacques Le Roux
>            Priority: Major
>             Fix For: 18.12.01
>
>
> Today I got this in log out of the blue:
> {quote}
> Daemon will be stopped at the end of the build after running out of JVM memory
> Expiring Daemon because JVM heap space is exhausted
> {quote}
> I checked there was no OutOfMemoryError exception. And apart that in log the applications were running well
> The most relevant articles I found on the Net were:
> https://stackoverflow.com/questions/56075455/expiring-daemon-because-jvm-heap-space-is-exhausted
> https://medium.com/@tiwarishani/expiring-daemon-because-jvm-heap-space-is-exhausted-in-react-native-e17c2248c8af
> I'm not sure this issue will reproduce (why just now?). I'll discuss this on dev ML before increasing
> org.gradle.jvmargs

--
This message was sent by Atlassian Jira
(v8.3.4#803005)