16 Jun
2014
16 Jun
'14
9:08 a.m.
On 16/06/14 13:08, Arran Cudbard-Bell wrote:
Maybe a bad parent, which is weird... valgrind?
It takes a long time to happen as the test server only receives a small amount of traffic; would running it under valgrind for extended period produce useful info here?
Could you also try reverting 6075844989ca8301a2743aed06ddd95382a6e78b
I could, though I might work on triggering it reliably first.
Which i'd say is the most likely candidate for introducing this bug, if it's only started appearing relatively recently.
TBH it's only very recently that I've had time to look into 3.0.x in production, so I'm not sure I have enough history to know it was recent for sure.