Compute memory leak with nested properties

[dylanrtt]

Apparently if you manually add a compute to a Map, and the compute depends on a deep property of that same Map, it can leak bindings if used in conjunction with other event bindings in a certain order.

http://jsbin.com/nadelesulu/1/edit?html,js,console

[justinbmeyer]

This is likely due to can.Map thinking that compute represents a define.get.

[justinbmeyer]

Looked into this. First, I don't think you should be writing your code like this. There's no reason to bind to "change" events on can.Map anymore and you could use the define plugin to describe petInfo.

I'm not sure why you would set a compute as a property value of an attribute either.

All that being said, it would still be nice to make this work. The problem is that this code creates a "cycle" of binding that isn't being detected while unbinding.

[justinbmeyer]

#1231 is probably related

[justinbmeyer]

Closed by #1696.