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

Jacques Le Roux edited comment on OFBIZ-11954 at 8/17/20, 2:22 PM:
-------------------------------------------------------------------

Thanks James,

I doubt because  [~danwatford] reported in dev ML:
bq. I ran into this a while back and needed to increase heap in my WIP branch.
And I upgraded only few days ago. Also I did not find anything related to a 
Gradle version on the Net. If it's the case they will fix it, otherwise we are 
covered by reserving more memory :)



was (Author: jacques.le.roux):
Thanks James,

I doubt because  [~danwatford] reported in dev ML:
bq. I ran into this a while back and needed to increase heap in my WIP branch.
And I upgraded only few days agao. Also I did not find anything related to a 
Gradle version. If it's the case they will fix it, otherwise we are covered by 
reserving more memory :)


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

Reply via email to