As Alexander explained to me verbally, implementing a test case that reproduces this issue is extremely difficult (there has to be a specific integer value in the stack for this problem to happen). So we agreed to push this one without a test - it's a 'one-liner' anyway. Pushed to 1.9