$ 0 0 For you information, the previous version I was running was 2015.1.318, where this problem did not yet occur.