It is a known issue. I read the same post yesterday (dunno if it was you or someone else). It is a retroarch bug, might be corrected in a future version after a retroarch b*mp.