v1.55 has several defenses in place to prevent this. It is now very rare. It can still happen but the full resolution requires a change in the architecture of testdat.db location and access. I'm calling this fixed for now.