It has been reported many times on the forum, but we do have a fix for this coming in the next update. See here:
Specifically: