Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Maximum Call Stack Exceeded When Destroying a nested model #476
This seems to be an issue with the can.Observe attributes serialize method conflicting with can.Observe.List's serialize method. When attributes get serialized, they're checked against a stack of already serialized observes to prevent infinite loops, but can.Observe.List.prototype.serialize seems to bypass this.
referenced this pull request
Dec 2, 2013
I'm digging this one too, and in the meanwhile I found out something at least interesting. I'm not sure as to how this adds for the discussion, but anyway, If one deferred FOO is resolved after another BAR, FOO just gets serialized and BAR makes the exception to be thrown. See http://jsfiddle.net/scorphus/ARTQ5/ for a brief demo. Hope it helps.