OOM killer, inconsistent db state, memory limit

[j1warren]

Hello,
Started blockbook after 2 days off and it was killed by oom killer and seems like now I have to redo the whole DB.
internalState: database is in inconsistent state and cannot be used

Is it syncing in bulk mode even after the initial sync is done and it starts just after a day of two off and 200-300 block behind?

Also, is it possible to implement either in blockbook itself or in blockbook + systemd (MemoryMax=20G) to make it gracefully restart after it consumes a specified memory limit?
Currently it uses from 10 GB slowly growing over time to 24 GB+ for bitcoin. I'd like it to automatically restart after it reaches 20 GB, for example.

[martinboehm]

I would recommend to disable the bulk mode using -workers=1 parameter, see for example #43