The bug still happens (frequently) in 4.14. Resampling the terrain component size to the same resolution fixes it.