This does sound like a bug I (many of us) have ran into, however I thought with that bug that the issue was temporarily mitigated for a few months by
↧