@nielsdos This basically disables the timeout feature if hrtime is not available.
Wouldn't it be better to either disable it completely via ZEND_HRTIME_AVAILABLE or, and I think this would make more sense, to switch to using a real time timer instead?

This basically disables the timeout feature if hrtime is not available.

That's false, it only does on interrupt, which was the same (buggy) behaviour as before.

Wouldn't it be better to either disable it completely via ZEND_HRTIME_AVAILABLE

I don't understand this.

and I think this would make more sense, to switch to using a real time timer instead?

You mean a wall-clock timer? That's also wrong.
I don't particularly care about such theoretical platforms where high-res time is not available.

This basically disables the timeout feature if hrtime is not available.

That's false, it only does on interrupt, which was the same (buggy) behaviour as before.

👍 got it now

Wouldn't it be better to either disable it completely via ZEND_HRTIME_AVAILABLE

I don't understand this.

I mean removing the calls to zend_hrtime() via #if ZEND_HRTIME_AVAILABLE

and I think this would make more sense, to switch to using a real time timer instead?

You mean a wall-clock timer? That's also wrong. I don't particularly care about such theoretical platforms where high-res time is not available.

Yes, but I got the first part of the effected timeout feature wrong - so it's probably not worth the effort of a "better than nothing" workaround.

I mean removing the calls to zend_hrtime() via #if ZEND_HRTIME_AVAILABLE

I see. That would make the code a bit more complicated: it requires two #if blocks. So I'm not sure this is worth it.