If we're not going to fix this bug for 1.10.0, I would strongly suggest disabling the metadata update feature entirely. I got memory corruption fairly regularly on my machine, so I wouldn't call it "rare". This might be the type of thing that doesn't really pop up on some machines at all, but on mine it was an issue.
If we're not going to fix this bug for 1.10.0, I would strongly suggest disabling the metadata update feature entirely. I got memory corruption fairly regularly on my machine, so I wouldn't call it "rare". This might be the type of thing that doesn't really pop up on some machines at all, but on mine it was an issue.