On 4/28/23 02:20, tim Rowledge wrote:
Even the reading I'm doing is as near atomic as we get for file operations; open the file, read the entire contents, parse into json. Mind you, for a MultiByteFileStream we do seem to do a lot of work to handle potential non-ascii UTF-8chars. Maybe that opens the door to some problems? Except we're still looking at sometihng that has happened maybe 5 times out of a thousand swings through the same file(s)
... bad RAM??
Tony