capture memory snapshot when the app runs out of memory

[christophsturm]

add java -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=bisq-dump to the start script. then people experiencing out of memory errors automatically have a dump file that they can send to us.

optionally check for the dump file at startup and tell people to create an issue. inspired by #3128

[christophsturm]

cc @ripcurlx

[battleofwizards]

Memory dumps can potentially contain secrets like private keys, mnemonic seeds, PRNG state, etc.

But maybe that could still be useful if we only allow it for developers (who I assume are testing on regtest and know what they are doing)?

[christophsturm]

Good point. We should make some memory dumps and see what data they contain.

[christophsturm]

or people could just open up the snapshot in jvisualvm and send us a screenshot.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.