Comment 9 for bug 53581

I know the comments are getting long at this point, but just to confirm this is specific to the *4.5 bits, I hammered on the *4.4 bits for a few hours (and I'm going to leave them on for the next few days, at least until hearing what other steps I can do to help debug this). It usually takes around 10-15 seconds to start getting the sigsegv's from the *4.5 bits, so at this point I'm extremely confident that this is a regression introduced in the 4.5 bits resulting from advisory USN-320-1. Unfortunately, there was a large amount of changes in the 4.5 bits which makes it more difficult to track down which change is causing this (and incidentally is a good reason for security updates to not bundle so many changes :)