OK, then it's likely the negative value (-1) that caused the issue, as expected. I'm going to submit the fix patch to upstream.