If you recently updated to version 49.22, you likely have the same issue described in this recent discussion: