Comment 38 for bug 330272

Upstream closed this bug, probably with good reason. Haven't heard of this happening in recent versions, and even if we did, it would need to be reproduced and a backtrace caught on a 0.24, and preferrably 0.25 system. If this reoccurs, please open a new ticket.