I attempted to load a snapshot utilizing the assumeutxo function supplied in Bitcoin Core v28.0. I ran loadtxoutset throughout IBD after the block headers have been synced.
However each time my login session will get killed after the next log:
..
2024-10-07T05:14:26Z FlushSnapshotToDisk: flushing cash cache (403 MB) began
...
2024-10-07T05:18:16Z FlushSnapshotToDisk: accomplished (230130.94ms)
...
2024-10-07T05:18:17Z FlushSnapshotToDisk: saving snapshot chainstate (45 MB) began
...
2024-10-07T05:22:01Z FlushSnapshotToDisk: accomplished (224537.77ms)
...
Checking the syslog, it seems that the method is being killed by oom.
2024-10-07T14:22:47.365074+09:00 FRONTIER systemd[3115]: [email protected]: systemd-oomd killed some course of(es) on this unit.
2024-10-07T14:22:47.366504+09:00 FRONTIER systemd[3115]: vte-spawn-4785ea6e-8c4a-44d0-80aa-72e36fb7107a.scope: systemd-oomd killed some course of(es) on this unit.
2024-10-07T14:22:47.366578+09:00 FRONTIER systemd[3115]: vte-spawn-4785ea6e-8c4a-44d0-80aa-72e36fb7107a.scope: Failed with end result 'oom-kill'.
2024-10-07T14:22:47.366672+09:00 FRONTIER systemd[3115]: vte-spawn-4785ea6e-8c4a-44d0-80aa-72e36fb7107a.scope: Consumed 2h 7min 57.285s CPU time, 46.4G reminiscence peak, 0B reminiscence swap peak.
Is that this a problem with Bitcoin Core? and is there a solution to work round this?
The snapshots are taken from the hyperlink under:
magnet:?xt=urn:btih:596c26cc709e213fdfec997183ff67067241440c&dn=utxo-840000.dat&tr=udppercent3Apercent2Fpercent2Ftracker.bitcoin.sprovoost.nlpercent3A6969
My surroundings is Ubuntu 24.04.1 LTS.