We also upgraded to 2.8 from 2.7 and are experiencing the same behaviour. We are looking forward to the fix this month.
