I had a similar problem on a nth program start, in seemingly the same conditions, was a disk cache memory hardware failure, some memory block return 1, whatever

I had a similar problem on a nth program start, in seemingly the same conditions, was a disk cache memory hardware failure, some memory block return 1, whatever was written into it. The bug trigger was highly erratic, because corrupt reads only was on cache read, and crashed my program as it was one of the single thing running on the system most of the time, and one of the single thing that was re-read enough to be kept in cache despite large disk traffic. The program had a large number of hour without incident, was thoroughly tested with unit test, and had 0 valgrind warning. I'd been intermittently tracking the problem for months, and the fact that it was an hardware issue was a huge relief, as I really started to loose footing on the necessary minimum of confidence in predictability you need to write software.