tchdboptimize() should not be necessary to avoid corruption...

... now that we have proper signal handling.

I put this here because the performance impact does not seem negligible as thought when tchdboptimize() was committed. I have not managed to reproduce any corruption in intense kill-respawn tests, I'll test even more today together with @awsiv and post the results.