Comment 8 for bug 1218839

The stacktrace suggests memory corruption (image->common.transform is an invalid pointer, but if it exists it has to be a valid transform - therefore something far more wacky took place). Grabbing a profile of the high cpu loads is likely to give a clearer picture of what occurs after the corruption takes place.