> Am 02.10.2017 um 19:53 schrieb William A Rowe Jr <[email protected]>: > > On Thu, Sep 28, 2017 at 7:44 AM, Stefan Eissing > <[email protected]> wrote: >> Update: disregard the man behind the curtain - for now. >> >> I have the strangest effects on my main machine under native macOS 10.12.6, >> which >> do not happen on my parallels ubuntu image and my laptop with macOS 10.13.0. >> I tested >> with hyperthreading disabled to exclude the Intel *lake bugs, but it made no >> difference. >> >> I will upgrade the machine over night to macOS 10.13.0 and check again >> tomorrow if >> that had any effect. > > Interesting. Any further word on this, or more comments that we might > help brainstorm?
With the fix that has also been accepted for backporting, I do not see these assertion failures any longer. There was a race with an unlock of a free mutex that triggered a pthread assertion. BUT: I still see one *one* machine, may recent iMac, that a signal for graceful restart triggers *something* in the process to spawn new threads endlessly until it exhausts system limits and dies. That is happening on this one machine on MacOS 10.12.6 and also 10.13.0. I suspect this is some 3rd party/os library linked. I checked that it is not a http2 related thread. Need to check for MPMs. I do not believe this to be hardware related since it did not happen at all for months before. I do not see it on my laptop for the same OS versions. I strongly suspect some mess-up of my machine now. Cheers, Stefan > >> Regardless of all this, I managed to find an edge case assertion fail and >> made a fix >> on trunk. If we go for 2.4.29, I'll propose that for inclusion. It is not a >> regression to >> 2.4.27, so no veto from me on 2.4.28. > > Thanks for that find and backport. I was wondering if this was related > to the report. > > Which machines / os do you observe the load test asserts on?
