-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
core dump due to too much memory? #607
Comments
Is this the same issue as #445 ? Guessing you have updated since? |
And I think oasis crashing due to wanting more than 500MB of ram is probably to be expected sadly |
It is the same problem as the other ticket linked. How can we prevent this from happening? I wouldn't guess that we have individual messages that are 500mb (esp since this is configurable).
…On Thu, Feb 18, 2021, at 3:56 AM, Jacob Karlsson wrote:
And I think oasis crashing due to wanting more than 500MB of ram is probably to be expected sadly
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#607 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAA6DPEZIQOEJRLRP2BD5LS7T565ANCNFSM4XVYSVGQ>.
|
No not individual messages, the whole process. Do you just not have enough ram for this app maybe? Or do you mean that this error would only happen if trying to make one big allocation of 500MB+? |
What happens if you add a few GB of swap? |
@Powersource This was with 2gb of swap. |
Per I have 2gb of swap on that machine. |
Here's my full log for systemd. I have 1gb of ram, and oasis is consuming 30-50% of it.
The text was updated successfully, but these errors were encountered: