"RangeError: Maximum call stack size exceeded" when destroying twice the same model
Opened this issue · 2 comments
ncortines commented
Hi,
The issue is easy to reproduce. Simply invoke "destroy" twice in the same model.
I'm not saying it is correct invoking "destroy" twice on the same model, but in my opinion this should be better handled.
Thanks
jeromegn commented
You're right. This command should be a noop after the first successful run or it should return a proper error.
killtheliterate commented
I just ran into this problem as well, though I cannot track down where multiple calls to destroy
are happening. I have a remove
listener set up on a collection which calls the destroy
method on the removed model, and then everything goes crazy and I have a stack overflow.