http://forums.donejs.com/t/bulk-actions-destroy-update-on-multiple-items/575
($click)=“handler()”
DefineMap, then you want `set: http://canjs.com/doc/can-define/map/map.prototype.set.html
can-validate / can-validate-validatejs should really help with validation
can-connect-signalr is notable (if you’re using ASP.net / SignalR)
you can now use can-event/lifecycle as a mixin
all the can-* packages have been updated to use Steal 1.0
{{#../teams.getById(homeTeamId)}} how does that work? besides the fact that I only thought possible to use {{#keyword}} with a reduced number of words there is also a parametric way of choosing that keyword? what about closing that tag, isn’t that necessary? thanks
Hi!
I don't know if I'm missing something or there is a memory leak in CanJs 3.
Following these steps anyone can reproduce the problem (I'm using Google Chrome):
- Open a new tab.
- Press F12 to show developer tools.
- Open http://www.place-my-order.com/
- Switch to Profiles tab on developer tools and take a heap snapshot.
- Click on the Restaurants link on the place-my-order page, then click on the Home link.
- Take another heap snapshot.
- Repeat step 5. and 6.
- On the Profiles tab select Snapshot 3 and list 'Objects allocated between Snapshot 1 and Snapshot 2'.
- Select for example the HTMLAnchorElement and view the details.
There are three detached HTMLAnchorElement DOM elements that are not garbage collected.
Does anyone know what alternative I have to the change event in canjs 3?
Say I have a list of foo's on my viewModel, and I want to listen to a change on any of the list "value" properties. I.e. how do I write this in canjs 3:
"{viewModel.foos} change" : function ( foos, event, prop ) {
if ( prop.indexOf( "value" !== -1 )) { ... }
}Hello!
I've further investigated the memory problem. It seems to me that can-util/dom/data/data causes the leak.
In data.js there is a variable 'data' that stores objects by id.
As I could understand the problem lies in not cleaning the 'data' variable.
To put everything in context: we have a quite large app (19 000 LOC) that is built with CanJS 2.x.
We are happy with it and started to migrate to 3.x.
We are at the final steps of migration and now we realized that with CanJS 3 we have a memory leaking problem.
I've created a small sample app that compares CanJS 2 and 3 regarding memory usage:
gist link
- Open index_canjs2.html and with dev tools Timeline record memory usage (start recording with a GC).
- Click on Insert/Remove for a few times.
- Before stopping Timeline recording call GC, then stop recording.
For example if I click on Insert/Remove for three times I can see on Timeline that there are exactly the same number of listeners (3) and nodes (70) in the begining as in the end.
Repeating these steps with index_canjs3.html show that the number of listeners grow gradually (with 3 Insert/Remove cycle the number of listeners grows from 4->10)!
If you put a breakpoint at the 753. row of can.all.js and analyze the content of variable 'data' (in Closure) after you click on Insert, you can see, that after a few "click on Insert/click on Remove" cycle 'data' keeps growing.
Initially - at the first click on Insert - there are 3 items in it.
Clicking Insert for the second time the 'data' variable contains 8 item.
When I click on Insert for the sixth time 'data' contains 28 objects!
No object gets removed from it.
This causes a memory leak: there are detached HTMLAnchorElements which cannot be GC-d because 'data' keeps reference for objects (canAttributesObserver, MutationObserver) which reference these HTML objects.
Shouldn't 'data' contain only objects that are somehow related to objects live in the DOM?
Is there something I'm doing wrong regarding the component insertion and removal?
Thank you in advance!
also, does this memory leak happen if you instead of
var frag = template(new TestVM());
document.body.appendChild(frag);you do
var myCompFrag = myCompRenderer();
document.body.appendChild(myCompFrag);