I think this is fixed with rev 17813.