[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=17181752#comment-17181752 ]

ASF subversion and git services commented on OFBIZ-11954:
---------------------------------------------------------

Commit d014dfa4ed3fe8fe252b97c168fbfa19520fb484 in ofbiz-framework's branch refs/heads/trunk from Jacques Le Roux
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=d014dfa ]

Fixed: wrong maxheapsize (OFBIZ-11967)

Reverts: Expiring Daemon because JVM heap space is exhausted (OFBIZ-11954)

Most likely a local error on my machine because nobody else complained and my
machine did not reboot for weeks

Or an issue with Gradle 6.5.1, but I doubt.

Anyway I still got the
"Expiring Daemon because JVM heap space is exhausted"
error with "org.gradle.jvmargs=-Xmx2g -XX\:MaxHeapSize\=4g"

> 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)