Given that the only plausible explanation was memory corruption caused by capture of a DNG with inadequate free space, and given that I haven't been able to brick my camera after many deliberate attempts, I think that the risk of this bug is now minimal.
It's not clear what the mechanism would have been if running out of space were the cause, by itself you wouldn't expect running out of space to cause memory corruption. It's also not correct to say this is the only plausible explanation. There are an essentially unlimited number of possible porting errors that could cause memory corruption, which would at least in theory end in hardware damage if they happened to hit the right location.
An alternative possibility was capturing DNG in a mode where valid raw was not available would cause memory corruption because it reverses the bytes of a large chunk of memory that is expected to be the raw buffer, but is actually something else.
This could be tested by commenting out the corresponding CAM_DISABLE_RAW_IN_* defines and shooting DNG in those modes.
That said, I agree that it is reasonable to post builds publicly now, with a warning referencing this thread. Note that this camera was not previously enabled in the autobuild, and it's not clear to me whether or not it is ready, independent of the hardware damage issue.
Edit:
Thanks a lot for risking your camera to test this.
