Reply to thread

Message

<blockquote data-quote="Mike" data-source="post: 1464533" data-attributes="member: 3">Honestly, I'm very confused by this error. The line in question doesn't pass a charset argument (we rarely do), so it should be using the default_charset. You appear to have headed me off by mentioning that, so I don't see how this would happen. There have been a couple places where certain functions weren't truly thread safe, but the case I'm thinking of was libxml related, and thus PHP being beholden to an underlying library. That isn't the case here. Looking at the C in the PHP source, it really should be coming from the argument or falling back to the php.ini setting.There isn't anything in the default XF code or libraries that actually tries to change default_charset either.We have seen some situations in the past where opcode caching bugs/corruption have led to impossible execution stats, so I do wonder if that's the case here. You mention PHP 5.6 so that could be relevant -- 2.2 has just been released (and is now our preferred version) and we've just dropped support for 5.6.So as it stands, my only idea is some bizarre server issue.</blockquote>

[QUOTE="Mike, post: 1464533, member: 3"] Honestly, I'm very confused by this error. The line in question doesn't pass a charset argument (we rarely do), so it should be using the default_charset. You appear to have headed me off by mentioning that, so I don't see how this would happen. There have been a couple places where certain functions weren't truly thread safe, but the case I'm thinking of was libxml related, and thus PHP being beholden to an underlying library. That isn't the case here. Looking at the C in the PHP source, it really should be coming from the argument or falling back to the php.ini setting. There isn't anything in the default XF code or libraries that actually tries to change default_charset either. We have seen some situations in the past where opcode caching bugs/corruption have led to impossible execution stats, so I do wonder if that's the case here. You mention PHP 5.6 so that could be relevant -- 2.2 has just been released (and is now our preferred version) and we've just dropped support for 5.6. So as it stands, my only idea is some bizarre server issue. [/QUOTE]

Verification