fixed by revision rev#80847
The correction will be available in next 6.5 release