They're looking into the issue and trying to reproduce it. The only hint so far appears to be (possibly) this comment made by the dev team:

This bug is actually coming from one of the modules launched by db_autopwn, not autopwn itself. Do you have any local modules installed that are not part of the tree?
I have no really tweaked the system other than updating. Does anyone have a suggestion to further test to see if somehow an update or something else installed an excess, duplicate, or corrupt module?