Closed dascandy closed 3 years ago
Describe the bug During normal use (building, running as daemon) the .evoke.db file gets up to gigabytes in size, with huge sections of sparse bytes.
Expected behavior File should, on successful build, remain tiny (<1MB).
Screenshots Add screenshots or a command log to help explain your problem.
System (please complete the following information):
Additional context Noted by developer; not on main line.
Problem fixed; problem was using file.good() instead of file.eof() causing it to think one record existed past the end, which causes corrupt data & random things.
Describe the bug During normal use (building, running as daemon) the .evoke.db file gets up to gigabytes in size, with huge sections of sparse bytes.
Expected behavior File should, on successful build, remain tiny (<1MB).
Screenshots Add screenshots or a command log to help explain your problem.
System (please complete the following information):
Additional context Noted by developer; not on main line.