[
https://issues.apache.org/jira/browse/OFBIZ-11954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181755#comment-17181755
]
ASF subversion and git services commented on OFBIZ-11954:
---------------------------------------------------------
Commit a8821c7a7887f872271d47cf8f6961d9beaf88db in ofbiz-framework's branch
refs/heads/release18.12 from Jacques Le Roux
[ https://gitbox.apache.org/repos/asf?p=ofbiz-framework.git;h=a8821c7 ]
Revert "Fixed: Expiring Daemon because JVM heap space is exhausted
(OFBIZ-11954)"
This reverts commit 547abb70d6be1fd717639be6c7a9913d8a61d93f.
> 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)
