You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a bug in _JKDictionaryHashTableEntryForKey which returns an incorrect result (returns an object when it should return NULL) if the key falls into the same bucket as another key, but the hash and value don't match.
This was reported by another user, but I never heard back if the fix I gave them worked. I've checked in that fix.
If you happen to have some JSON that tickles this bug, could you paste it in to the ticket? This condition never showed up during my testing, it requires just the right set of conditions that's almost impossible to create by hand.
Hi John,
There's a bug in _JKDictionaryHashTableEntryForKey which returns an incorrect result (returns an object when it should return NULL) if the key falls into the same bucket as another key, but the hash and value don't match.
The loop does:
But never clears atEntry if we get to the end of the loop and the key wasn't found.
Thanks!
Regards,
Omar
The text was updated successfully, but these errors were encountered: