Your issue could be related to a very recently introduced and fixed bug:
Do you run the latest patch-level release?