We could reproduce the problem internally and will forward the issue to our development.
With 2.2.0p21 this is also fixed.
Both fixed are required. p21 will be likely there tomorrow.