Revision deletion cron job can result in 'corrupt' nodes with no revisions

It says on the module's homepage, "This module will NEVER delete the current revision of a node, nor will it allow you to do so."

We have a situation where there are multiple nodes on the system with no revisions, no title, no content type - completely dud nodes. After a lot of debugging, we tracked the problem down to revision_deletion_cron(). This needs further investigation to understand exactly how or why this could happen, but for now we have simply disabled this module. I don't have the time now, but I would suggest that you make a through review of your implementation of hook_cron.