yup me too, i thought that i'm the only one that suffered this problem, the problem happened since i tried 10.12.1 beta 1 till 5 and then final 10.12.1 the problem still there, even i've tried clean install 10.12.1.
the app just get stucked with not responding status, and needed to be forced...