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
Compute memory leak with nested properties #1676
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.
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
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.