I know there was work done to fix this in v1.1.6, but I ran into this error today when destroying a model running against v1.1.7
I have created a fiddle, albeit not a pretty or simplistic one, but one that demonstrates the error.
Here's what I've noticed:
1. The models are nested creating circular references
2. The models need to be live binded to DOM
3. It is only after the second call to Policy.findAll that puts things in a state to throw the maximum call stack error
If you don't do numbers 2 or 3 above, then you don't get the maximum call stack error.
Here is the fiddle: http://jsfiddle.net/thecountofzero/8KX4N/
After it loads/runs, open the console (make sure you are in the result(fiddle.jshell.net) frame) and execute the following line:
- policies[0].destroy()
Thoughts?
