Am experiencing this bug too. Can confirm the workarounds reported work as advertised, but obviously not valid for all situations.