<p></p>
<p>I have seen that too but only once for my always-on bisq. Seems like a legitimate Out-of-Heap error since Bisq is resource hungry beyond compare. Restart Bisq and everything is fine again.</p>
<p>There are multiple efforts and fixes in the pipeline, though, as <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/ghubstan/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/ghubstan">@ghubstan</a> already said, java10 is very old and outdated, yet, we refuse to upgrade, and that would fix a whole lot of issues (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="614036656" data-permission-text="Title is private" data-url="https://github.com/bisq-network/bisq/issues/4242" data-hovercard-type="pull_request" data-hovercard-url="/bisq-network/bisq/pull/4242/hovercard" href="https://github.com/bisq-network/bisq/pull/4242">#4242</a>). Plus, there are projects in line to help reduce RAM requirements (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="595721729" data-permission-text="Title is private" data-url="https://github.com/bisq-network/projects/issues/29" data-hovercard-type="issue" data-hovercard-url="/bisq-network/projects/issues/29/hovercard" href="https://github.com/bisq-network/projects/issues/29">bisq-network/projects#29</a>, <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="576403913" data-permission-text="Title is private" data-url="https://github.com/bisq-network/projects/issues/25" data-hovercard-type="issue" data-hovercard-url="/bisq-network/projects/issues/25/hovercard" href="https://github.com/bisq-network/projects/issues/25">bisq-network/projects#25</a>) which are either waiting to be reviewed and merged or waiting to start (with a clear <g-emoji class="g-emoji" alias="+1" fallback-src="https://github.githubassets.com/images/icons/emoji/unicode/1f44d.png">👍</g-emoji> from the community but no budget for over a month now).</p>
<p><a class="user-mention" data-hovercard-type="user" data-hovercard-url="/users/cd2357/hovercard" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/cd2357">@cd2357</a> we played around with the -XX:+UseG1GC flag way back and it did not change anything. Only when I hunted down and found the faulty line of code that produced the resource leak, thing changed. Bisq still holds the whole data stores in RAM (not at first, but just click the "trades" tab and there you go) and it will do so until we change things.</p>
<p>As long as we do not fix the underlying issues, we will only treat single failures and waste time and resources over and over again.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/bisq-network/bisq/pull/4048#issuecomment-629136414">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AJFFTNUPA7ZKRO4VQ6VV7M3RRUEEBANCNFSM4LFWJPGQ">unsubscribe</a>.<img src="https://github.com/notifications/beacon/AJFFTNUDYG22NGYDUWWF7X3RRUEEBA5CNFSM4LFWJPG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEV75YHQ.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/bisq-network/bisq/pull/4048#issuecomment-629136414",
"url": "https://github.com/bisq-network/bisq/pull/4048#issuecomment-629136414",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>