Memory leak in 0.7.1

[jccazeaux]

Hi

I've done the upgrade from 0.6.9 to 0.7.1. Since i noticed some memory leak. The objects seem to be retained after unbind.
I made a jsfiddle with a very basic bind/unbind. In the model i put a very big String (~5MB) so we can clearly see the allocations and deallocations.

example with 0.6.9 : http://jsfiddle.net/jccazeaux/v6x47k6k/

In the chrome profiler we can see that the objects are correctly freed:

Same code with 0.7.1 : http://jsfiddle.net/jccazeaux/v6x47k6k/2/

In the chrome profile we see that the objects are retained. The memory is growing.

To test it, just start the "Record heap allocation" profiling type and click alternatively on "bind" and "unbind".

[jhnns]

Yep, that looks like a memory leak...

[bharatpatil]

Should I downgrade?

[JakeHP]

Yikes..

[mikeric]

Looks like this issue was opened after #421 had already been merged in.

@jccazeaux Can you please verify that this is in fact an issue on master? I was already aware of the memory leak in the current release (0.7.1), which has been addressed in #421.

[mikeric]

Closing this. I've released 0.7.2 which includes #421.

[jccazeaux]

I was unavailable until today. I verified the 0.7.2 and it doesn't seem to solve the problem. Here is the jsfiddle with 0.7.2 : http://jsfiddle.net/4tprm3ny/2/

[docluv]

I verified the leak in jccazeaux's JSFiddle using IE's memory profiling. You can see the memory building up from the base of 3.5MB (JSFiddle baseline) to 13+MB after the bind. The bound data is not released and only compounds as you bind and unbind.

[jccazeaux]

This issue should be reopened

[mikeric]

@jccazeaux, @docluv Thanks for reproducing the leak on 0.7.2. Reopening this, will take a look next chance I get.

[JakeHP]

Thanks @mikeric

[jhnns]

👍

[jccazeaux]

Thanks

[AMTourky]

Still occurs at 0.8.0
my object is pretty big, and leaking tons of memory

[JakeHP]

Good catch @AMTourky

[AMTourky]

Thanks @JakeHP

[jccazeaux]

Found the solution in sightglass : mikeric/sightglass#10

[JakeHP]

Good job @jccazeaux!

[jhnns]

👍

[nopnop]

Nice catch @jccazeaux,
@mikeric : any plan to fix this issue soon ?
Thanks