Could be possible that this is just a side-effect of the scanner scheduler issue currently discussed in the following topic: