Comment 3 for bug 1268524

I'm setting status back to "in progress". While the fix that was committed stops the 100% CPU usage, this doesn't fix the underlying problem: if the .so for the scope doesn't have a destroy function in the symbol table, we end up spinning somewhere. I'm looking into this at the moment.