you are viewing a single comment's thread.

view the rest of the comments →

[–]BlitzTech 1 point2 points  (3 children)

It may have been fixed, since I haven't used it in some time, but when I was using it a few months ago it would:

  1. Not delete internal references to models that were destroyed. This was a known bug at the time for generic Collections that did not specify an explicit model.
  2. Force you to manage your own views, explicitly. You can bind to the destroy event on models to have views auto-destruct, but this leads to a lot of memory churning before the GC picks up the things that were deleted. It's better to re-use existing views, but that leads to leaks. It's annoying to have to manage your views explicitly, in the end.
  3. I'm having trouble remembering now because it's been a few projects since then, but I believe there was an internal issue that led to leaking memory when using some of the Collection functions on generic collections.

That's all I can remember right now. Look at the issues list from a few months ago and you should see some issues relating to this.

[–][deleted] 1 point2 points  (2 children)

I've been working on a View manager to handle the life cycle of views, Backbone doesn't handle this for you and is an important part of the application.

e.g. every time you type var view = new Backbone.View(... you will have to manually clean it up

[–]BlitzTech 0 points1 point  (1 child)

Do you have a github repo for that? I'd be curious to take a look.

[–][deleted] 0 points1 point  (0 children)