2

From the Rivets.js documentation

Every call to rivets.bind returns a fully data-bound view that you should hold on to for later. You'll need it in order to unbind its listeners using view.unbind().

But what if it is not convenient to hang on to this reference? Must unbind always be called?

If the view's elements have been removed from the document using a method like jQuery'sremove(), will there still be guaranteed memory leaks because Rivets itself will continue to hold a reference to the element or the view?

  • I'm in the exact same situation now, still leaking memory, but jQuery remove and such things still causing memory leakage. did you find a solution? – AMTourky Feb 09 '15 at 11:24
  • 1
    @AMTourky, for me the question was more of a hypothetical that I wanted to be assured wouldn't happen rather than a problem I was experiencing. As no assurances were forthcoming and everything else indicated I probably shouldn't, I didn't go forward. I could imagine that reporting your issue or making a feature request to the maintainer of rivets could help clarify things (or upvoting the question)... – toomanydaves Apr 23 '15 at 20:00
  • I think there still no solution available for this? – chiragchavda.ks Oct 28 '16 at 06:49

0 Answers0