Comment 36 for bug 1307473

We haven't been able to reproduce the issues under lab conditions, and I'm not willing to use our production setup as a guinypig anymore. These issues have cost me too much credibility already.

We believe #1326367 is causing this, as we've bisected this issue to be between 3.13.0-27.50 and 3.13.0-29.53 (see our results earlier). #1326367 is the only change which felt relevant, but admittedly, this is just a hunch.