This sounds very similar to a bug that we resolved in the 0.44.6 release, try updating to the 0.44.7 release and see if that fixes the problem.
