This sounds a lot like the secondary bug I reported in this topic for the previous release (release 110).