-
Notifications
You must be signed in to change notification settings - Fork 338
Elements -> $scope shows "Maximum call stack size exceeded" #301
Comments
What version of Batarang are you running? |
I've the same problem, the versión is 0.12.7 and chrome 52. For more details, we have an Angular App 1.5.0 |
After a lot of searching, I discovered that the method of provider compiler Enable again and It works! |
Yeah, you need to enable debug in order to use debug tools. |
@bytelovers I'm afraid that I'm still on What do you mean by
exactly? Thanks! |
@SomeKittens Alright, this
is valid, regardless of versions (Angular, Batarang)? |
Yes, regardless of what version of software you're using, you can't use features if you disable them. |
debug enabled:
but still get this error:
jquery: 2.2.4/3.3.1 could anyone help? |
As is has been mentioned in this SO comment, the Baterang tool in the debugger tab Elements -> $scope sometimes shows not that useful informations like these:
It is quite hard to reproduce and I guess, that a JSFiddle or Plunker won't help much, because the environment (for the debugger and the Batarang plugin) is very different.
We have a normal Web Application and are using Angular 1.4.7. We also use the Angular ui-router 0.2.14.
These lines are shown for the element only (AFAIK) and in apparently random circumstances.
The Maximum call stack size exceeded error do not appear in the console, though. I have no idea, where it could have been thrown, but I guess not in our scripts or the framework/libraries.
I know, that this might not be very telling, if you need any information, please ask.
Edit When you click on another element in the tree under , then back to , the correct informations regarding the $scope will be shown.
The text was updated successfully, but these errors were encountered: