Angular Issue about ama HOT 3 CLOSED

Here are a few things you might try:

• use ng-stats to see digest times
• Try it in an incognito tab (so it doesn't have your extensions). It looks like you have Batarang installed and enabled. Could be that...
• Open up the devtools and click the "Pause" button to see where execution is.

Pause button:

Let me know what you come up with :-)

from ama.

I had already been using ng-stats to try and track down the problem with no luck (although it did help me improve other things about the app by reducing watchers via one-way binding. In the end I resorted to process of elimination: removing things from my controller and routing until the problem went away.

In the end it turned out the culprit was angular.copy(). I found this thread where one of the Angular collaborators even said that the team regrets exposing angular.copy to the public, and that led me to removing it from my controller to test – I had about 6-7 of them in the offending controller. Voila, page load time went back to normal (~1s).

I can't remember exactly why I was using angular.copy in that situation, as everything still worked the same after I removed it, but I think it had something to do with sorting/manipulating lists off of an API by making a copy of them first. Anyway, issue resolved!

from ama.

I can't remember exactly why I was using angular.copy in that situation

I remember we talked about why you were using it many months ago, I just can't remember the reason.

from ama.