ValueThreshhold set to 0 or 1 results in badger abandoning crash resiliency

BadgerDB does not provide crash resiliency when value threshold is set to 0 or 1. For any values higher than 1, badger is able to handle crash i.e. the data which was written before the crash remains intact. One observation we see when value threshold is set to 0 or 1 is that data in vlog file is present but somehow while querying keys from badgerDB, badger is not able to find the keys written before crash.

Note: We crashed badgerDB by sending SIGKILL to the process to force ungraceful termination of the process where badgerDB close was not called.

Also, we would like to know the recommended value for value threshold setting in badgerDB for minimal memory usage?