Hey @Jason_Teo – my recommendation for the moment would probably be to disable analysis, and see if things pick up again when you re-enable it.
If that doesn’t work, I would sit tight. We are aware of some issues in the analysis code you’re using, but we’ve opted to re-write analysis from the ground up for our upcoming 1.3 release.
I don’t have a firm timeline on when it will be released, but it should be by the end of the year. Our new analysis code should yield much better results, but it will require your library to be re-analyzed, which is why I wouldn’t worry about this too much for now.