The issue has been resolved. The fix will be available in the next official release Q1 2015 as well in the internal builds.