This looks weird that you need to utilise both recursion protection and stack protection. Are you sure that you need both?

Agree with @ndossche

I added stack protection in order to have some fast path at the beginning of functions to immediately return if we can detect an error, instead of going through the whole code waiting for a recursion error to be raised

I added stack protection in order to have some fast path at the beginning of functions to immediately return if we can detect an error, instead of going through the whole code waiting for a recursion error to be raised

You're optimizing the sad flow here instead of the happy flow. We generally don't do that. While here it doesn't really degrade the performance of the happy flow noticeably, it's still adding complexity. I'd prefer to stick with the recursion protection alone.

both recursion protection and stack protection

It can be useful to differentiate between the two cases, as one of them is not supported by mb_convert_variables(), while the other is supported as long as the stack is large enough. So a "Cannot handle recursive references" tells you that you can not use mb_convert_variables() like that, while "Maximum call stack size reached" tells you that you may be able to fix the problem by increasing the stack size.

But changing the stack limit message emitted by mb_convert_variables() so that it mentions potential recursive references would work too, I think: "Maximum call stack size reached. Deeply nested structure or recursive references?".

So I pushed a new version adding a check before emitting the warning. This way, the error is displayed if the stack is overflowed and the warning is kept in case of deep/infinite recursion. Because of how the code is articulated, that's what I could achieve.

Windows test is failed. Diff is below:

001- Fatal error: Uncaught Error: Maximum call stack size of %d bytes (zend.max_allowed_stack_size - zend.reserved_stack_size) reached. Infinite recursion? in %s:%d
002- Stack trace:
003- #0 %s(%d): mb_convert_variables('utf-8', 'utf-8', Array)
004- #1 {main}
005- thrown in %s on line %d
001+ Done

Fixed by decreasing the stack size and increasing the nesting depth so it also crashes on Windows