There are other threads reporting the same issue which became prevalent after the upgrade to 4.2.0.19. Here
and here